New Feature Screenshots

Change Log

Story

4594 Adjust the alignment of the table header of version browsing. 
4595 Fullscreen browse code files and the Back button is not working. 
4598 SVN package can be used to get the directory and files of a directory. 
4243 Integrate WeChat Enterprise notification with notification in ZenTao. 
4593 Export files can be read and downloaded at the same time. 
4586 The width of the Notification window is too much. 
4585 Align the table header of the backup list. 
4485 Check Build History.
4488 Jenkins server configuration.

4590 Use the Cron feature in ZenTao to synchronize repositories.
6795 Add menus and breadcrumbs of CI module in ZenTao.
6794 Display the task status of last execution in a Build list.
6793 Remove the old feature of repo management.
6787 Jenkins task run results, get log and analysis.
6786 Add tags to builds in Jenkins.
6785 Polling to get the task execution status in Jenkins.
6784 Use Cron to create builds.
6782 Manually create builds.
6778 Enable extension configuration when committing comments for a repo.
6777 Use comments to create a git build.
6773 Configure cron task, tags and comments to create a build.
6897 Package the request for CRUL desktop in  Jenkins.
6895 If GIT and SVN are triggered by a Tag, use a parameter to pass the tag name and url to Jenkins for creating a build.
6893 Use comment commands as the system configuration.
6892 CI module in ZenTao. When editing a job, ajax can dynamically get the type of the selected repo (svn/git) and the sub directory of svn.
6889 CI module. Adjust its build plan.
6888 CI module. Page JS event, and bind it with Jquery after the loading is complete.
6859 Move the blame feature from Pro to open source version.
6856 When editing a build,  use Jenkins to get tasks for users to choose.
6854 Move the browse  feature from Pro to open source version.

Bug
2893 Optimized the integration with Dingding. 
2965 Uninstallation file of an extension cannot be deleted. 
2968 Admin data is not displayed.

Download

Source Code Package

     Official Website    SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website    SourceForge

• Windows 32 bit one-click installation

     Official Website    SourceForge

• Windows one-click installation (No security Settings)

     Official Website    SourceForge

One-Click Installation  Packages for Linux (unzip to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website    SourceForge

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

PHP package

• DEB package:     Official Website    SourceForge

• RPM package:    Official Website    SourceForge 

Help

  Installation Manual

  Update Manual

If you have any questions or would like to get a free trial for more than three users, contact renee @easycorp.ltd for help.

Do you really want to unsubscribe?

  Comments:

About ZenTao Enterprise

On the basis of ZenTao Pro fessional, ZenTao Enterprise adds features such as operation and maintenance management(OPS), OA office management, feedback management, document version management and document online preview, which can provide more comprehensive support for enterprise project management.

For ZenTao Enterprise features, click  HERE .

Changelog

2228 Error in the page of Product Overview.

2224 Save a default value for a field, but it cannot trigger the condition for the added action.
2223 Set the control type as date, but it shows the current date on the interface.
2212 Modules that is not in the category of a feedback is displayed.
2173 Add fields to a workflow and it affects the search feature.
2171 AssignTo and Mailto users are not notified in the newly added workflow.
2169 Modules in a custom workflow are incorrect.
2166 Copy a workflow. The navigation it is on cannot be copied.
2159 Add a field for the newly added workflow, but it is not displayed.
2155 Actions in the dropdown is not consistent with that of the Chinese version.
2153 Extended Action fields are overlapped and dysfunctioned.
2150 Datasource of a newly added field has default data.
2149 Invalid setting of the default value for a workflow.

2148 Set a newly added field as a required field, but it didn't work.
2132 Set  a newly added field as a Read-Only , but it didn't work.
2131 Only the key of a custom field is exported.
2122 Added fields in a workflow can't be exported.
2119 Error prompts when the length of a newly added field of a workflow is empty.
2117 Set a new field as a required field, the it goes blank.
2114 Newly added fields cannot be exported.
2113 Newly added field shows no name.
2108 Add a File field to Product and Project of a workflow, but no file can be uploaded.
2100 Edit an action for a project in a workflow, but the interface is not right.
2095 Extended Action in a workflow cannot be set.
2091 Add a rich text type of fields, then it is not right.
2090 Set cross-flow privileges, then the corresponding lang is missing.
2089 Action buttons on the list of newly added flows need to be optimized.
2085 New flow. First-level navigation of its location is not right.
2082 Set the interface of a page, then the position of the fields need optimization.
1988 Extra "-" in the name of a field on the detail page of a workflow.

1987 Set the navigation for a flow but it didn't work.
1936 Add breadcrumb to the bottom of the Flow page.
1849 Fields are not displayed in the added Action page.

Installation and Upgrade

• For the first-time Installation, refer to  H ERE.
• For upgrade (from Open Source Version), refer to HERE.

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website

• Windows 32 bit one-click installation

     Official Website

• Windows one-click installation (No security Settings)

     Official Website

One-Click Package  ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website

PHP package

• PHP 5.3-5.6 package:     Official Website

• PHP 7.0 package:           Official Website

• PHP 7.1 package:           Official Website

• PHP 7.2 package:          Official Website

ZenTao Desktop

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by  Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click  HERE to know more about it.

ZenTao Desktop

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit  MacOS

ZenTao Desktop Server

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit   MacOS

If you have any questions or would like to get a free trial for more than three users, contact Renee @easycorp.ltd for help.

ZenTao Pro is an enhanced version of ZenTao Open Source. The intention of developing the professional version is to provide IT companies and teams with more comprehensive solutions. The professional version enhanced features are more fit for managing the internal process of any enterprise.

About ZenTao Pro

For ZenTao Pro features, click  HERE .

Installation and Upgrade

• For the first-time Installation, refer to  http://www.zentao.pm/book/zentaopromanual/133.html
• For upgrade (from Open Source Version), refer to  http://www.zentao.pm/book/zentaopromanual/131.html
• For update (from Lower Version), refer to   http://www.zentao.pm/book/zentaopromanual/136.html

ZenTao Pro Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website    SourceForge

• Windows 32 bit one-click installation

     Official Website    SourceForge

• Windows one-click installation (No security Settings)

     Official Website    SourceForge

One-Click Package  ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website    SourceForge

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

PHP package

• PHP 5.3-5.6 package:     Official Website    SourceForge

• PHP 7.0 package:           Official Website    SourceForge 

• PHP 7.1 package:           Official Website    SourceForge

• PHP 7.2 package:           Official Website    SourceForge 

ZenTao Desktop

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by  Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click  HERE to know more about it.

ZenTao Desktop

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit  MacOS

ZenTao Desktop Server

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit   MacOS

If you have any questions or would like to get a free trial for more than three users, contact  Troy@easycorp.ltd for help.

Change Log

Bug

2954  Windows one-click installation package. xxd server version is not the same as shown in ZenTao Desktop.
2951 Create Task page. Choose linked stories and error prompts.
2947 Report in Doc includes the sizes of deleted files.
2946 Project-Bug. Search feature error.
2943 Project-Overview. Cost hours are not accurate.
2942 Repeat password has no reminder when the passwords are not the same.
2941 Batch create users are not recorded in zt_action.
2937 Product-Plan. Create a plan and select the dates, and save. The dates are 2030-01-01.
2935 Upload relative URL of an image to the Editor, then it is not displayed in the email.
2933 Initalizing scripts have no scripts to update efforts.
2932 Reoport on Dashboard is not displayed right.
2931 The clickable area of a checkbox on the Create page is too large.

2930 Error prompts on Doc pages (not reproduced on the local machine)
2929 If Markdown contains << , what is after the sign is not displayed.
2927 Create several child tasks in a short period and no prompts of it.
2926 Bug to Story. Unparsed code is displayed in the history.
2924 Edit Block feature should be optimized.
2922 Effort report on Project-Report is not accurate.
2919 Create a project via a plan. Save it and it goes blank.
2918 Incorrect data in Project-Report.
2917 Tree view. No real names are displayed for stories.
2914 Untranslated terms in Translate module.
2913 Optimized the display for contact groups with long titles.
2910 Todo cannot be closed in bulk.
2907 No error page for incorrect search conditions.
2904 View and Privilege under the Privilege module are not redirected to the same page after being saved.
2897 My Dashboard. Task status is not right.
2896 Test--Bug page. Incorrect search results.
2894 Activate Project error in the Manage Privileges page.

Download

Source Code Package

     Official Website    SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website    SourceForge

• Windows 32 bit one-click installation

     Official Website    SourceForge

• Windows one-click installation (No security Settings)

     Official Website    SourceForge

One-Click Installation  Packages for Linux (unzip to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website    SourceForge

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

PHP package

• DEB package:     Official Website    SourceForge

• RPM package:    Official Website    SourceForge 

Help

  Installation Manual

  Update Manual

If you have any questions or would like to get a free trial for more than three users, contact Philip @easycorp.ltd for help.

This name change will allow us to present ourselves as truly an innovative and comprehensive company to the IT industries worldwide.

Our commitment to our customers and partners remains our highest priority. By rebranding ourselves as EasyCorp and becoming a comprehensive company with three product category, namely management software, IoT solutions, and cloud storage, we believe that we are providing our customers with the best selection of management tools and services available to the market today.

Further, as part of this exciting worldwide company rebranding effort, EasyCorp will all be adopting new logos that better express our family of products and services. 

Please note that our rebranding and name change will not impact our PayPal account, and additional invoicing information, which all remain the same:

PayPal account: paypal@cnezsoft.com

Company Name: QingDao Nature Easy Soft Network Technology Co., LTD.

Billing Address: 167 Wuyishan Road,Qingdao, Shandong, China

Thank you for your continued support and patronage, and we look forward to sharing our new look with you!

IT Industry in Vietnam

Multinational companies like Intel, IBM, Samsung Display, Nokia and Microsoft chose Vietnam to outsource their software projects. Vietnam exported $3.5 billion worth of software 2018, according to the Ministry of Information and Communications of Vietnam.

IT is a growing industry in Vietnam. A report by recruitment firm ManpowerGroup, a Vietnam human resource solution provider , released in January 2019 said that IT will be the industry with the highest recruitment demand this year with 14 percent increase compared to last year.

As IT industry is booming in Vietnam, so does the demand to manage IT projects. ZenTao as a project management tool for IT, especially software, is recognized in Vietnam.

ZenTao Presents in Vietnam

Nguyễn Quốc Nho, is a professional and experienced project manager and actively involves in project management training. He is also the Director of Fsofts Co., Ltd which offers an onsite, nearshore & offshore technology support and IT outsourcing services.

I found that in Vietnamese market ZenTao is greatly needed, especially in project management.

                                                                                                                                    -Nguyễn Quốc Nho,  Fsofts Co., Ltd  

ZenTao is a Scrum tool covering the application project management from planning to releasing. 

ZenTao

Reference

1. https://e.vnexpress.net/news/business/industries/vietnam-it-industry-is-more-than-just-outsourcing-3912280.html#targetText=Vietnam's%20fintech%20market%20reached%20%244.4,SAAS)%20and%20e%2Dcommerce.

2.

About ZenTao Enterprise

For ZenTao Enterprise features, click  HERE .

Installation and Upgrade

• For the first-time Installation, refer to  H ERE.
• For upgrade (from Open Source Version), refer to HERE.

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website

• Windows 32 bit one-click installation

     Official Website

• Windows one-click installation (No security Settings)

     Official Website

One-Click Package  ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website

PHP package

• PHP 5.3-5.6 package:     Official Website

• PHP 7.0 package:           Official Website

• PHP 7.1 package:           Official Website

• PHP 7.2 package:           Official Website

ZenTao Desktop

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by  EasyCorp. It is self-hosted and cross-platform with various plug-ins and rich features. Click  HERE to know more about it.

ZenTao Desktop

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit  MacOS

ZenTao Desktop Server

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit   MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy @easysoft.ltd for help.

The annual summary feature is added to Report view of this release. This feature is designed to help users better report the annual work. In the annual work summary, users can generate relevant working hours, the number of requirements, tasks and bugs created by the current user annually, the project list, the involved project, the involved product, and basic information according to a user role. You can view the complete data of the entire project intuitively, which is convenient for users to summarize and report their annual work. The interface is graphic and textual, and supports one-click export as an image.

About ZenTao Pro

For ZenTao Pro features, click  HERE .

Installation and Upgrade

• For the first-time Installation, refer to  http://www.zentao.pm/book/zentaopromanual/133.html
• For upgrade (from Open Source Version), refer to  http://www.zentao.pm/book/zentaopromanual/131.html
• For update (from Lower Version), refer to   http://www.zentao.pm/book/zentaopromanual/136.html

ZenTao Pro Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website    SourceForge

• Windows 32 bit one-click installation

     Official Website    SourceForge

• Windows one-click installation (No security Settings)

     Official Website    SourceForge

One-Click Package  ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website    SourceForge

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

PHP package

• PHP 5.3-5.6 package:     Official Website    SourceForge

• PHP 7.0 package:           Official Website    SourceForge 

• PHP 7.1 package:           Official Website    SourceForge

• PHP 7.2 package:           Official Website    SourceForge 

ZenTao Desktop

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by  EasyCorp. It is self-hosted and cross-platform with various plug-ins and rich features. Click  HERE to know more about it.

ZenTao Desktop

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit  MacOS

ZenTao Desktop Server

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit   MacOS

If you have any questions or would like to get a free trial for more than three users, contact  Troy@easysoft.ltd for help.

Screenshot: Annual Work Summary

Change Log

Story

4438 Edit a build and change the Linked Project. 
4437 Display the number of Test Request linked Cases. 
4428 Search tab is not highlighted on all pages of Sprint. 
4425 ID of duplicated bugs should be required. 
4507 View codes in Repo is moved from Pro version to open source version. 
4529 Display the data of each block for testers. 
4528 Display the data of each block for PO users. 
4527 Display the data of Effort for Developer users. 
4526 Display the data of Bugs and Tasks for Developer users.   
4525 Display the data of Project for Developer users. 
4524 Display the data of Project Involved for Developer users. 
4523 Display the data of Profile for Developer users. 
4522 Design the visual style and layout of the five major blocks. 
4521 Design the global style for big screens. 
3363 Change the returned page after creating an object. 
4520 Integrate the latest Xuan IM. 

Bug

1276 It is very slow to batch edit tasks.
1334 Login address error of the integration between ZenTao and the third-party application.
2014 Code remains even the test request is deleted.
2029 Invalid editing story stages on the page of a story list.
2066 Company-Department. Loading time is too long.
2075 Create Bug in Tutorial of ZenTao international version.
2078 Batch Create Todos. No prompts if no information is entered.
2084 Manage modules in a Doc Lib. The order of the modules is not the same as before.
2089 Hide Batch actions if no batch action related privileges.
2114 Histograms on bugs error. If a project name is long, it is not displayed as a whole.
2184 A module of a product can be changed to the branch of another product.
2185 Incomplete display of date generated in Report.
2208 Abnormal display of story phases when batch editing them.
2219 QA-bug list page. The scrollbar at the footer of a table blocks the data.
2225 PPT icons in file libraries are not displayed.
2231 If there are many tasks, the page is displayed in a mess.
2237 Report a bug. Data in tab bars is not updated.
2239 Timeout when uploading a file to a doc library.
2244 ID of a duplicated story is not recorded when creating it.
2250 Closed Project. Set it off to display doc libraries but error prompts.
2252 Collapse is disabled after executing the search under several conditions.
2253 Story ReviewedBy is not separated in a new line.
2254 Batch Run Cases. The results are not linked.
2264 IE11. The cursor is in a new line when entering repro steps for a bug.
2277 Linked Branch in a product module can't be edited.
2281 Roadmap is reversed in product details page.
2289 The spaces between action controls are not the same on different pages.
2303 One-click installation. Options on the interface are not on the same line.
2306 Icons displayed on the homepage of the QA.
2308 Assignees on a bug list. Usernames are displayed.
2309 Batch edit modules linked to stories on a list page. The page will scroll down when using the search feature.
2310 Titles in a roadmap is overlapped on Product Overview.
2312 Choose a group for repro steps of a test case, the steps are not fully displayed.
2315 Special characters in repro steps of test cases affect the display of the page.
2321 Required mark is missing when entering Close Reason.
2326 Project-Doc. Access document categories but prompts as no privilege.
2327 IE11. Image uploaded is not compatible.
2329 Edit a product line. Module name should actually be the name of a product line.
2330 Rich text editor in Product-Plan is not displayed right.
2335 Search rules of assignedto on a Link Case page.
2338 Accessing a page without the required privilege via a link, you will be directed the last page you were on.
2342 Project-Report.The interface should be optimized.
2343 Story information should be displayed nicely.
2349 Create and Edit a case, and its group info is not compatible with the repro steps.
2364 No story is linked to a product for a project, but the product module will show when managing modules for the project.
2405 Batch Edit Plans. The input box is abnormal.
2422 “+” icon title is missing on the page of Task details.
2423 Ongoing tasks cannot be batch cancelled.
2428 Access child tasks but prompted as no privileges.
2430 Create a child task but no module of parent tasks can be linked.
2431 Actions on the pop-out of case details are not right.
2434 Choose a group for cases. Then the steps of recorded cases are turned into child cases.
2436 Reset the password and login. User will be directed to the page to reset the password.
2437 Incomplete data in the dropdown of product/project.
2441 Refresh the page of Product and error.
2442 Edit a bug, and the scrollbar needs to be optimized.
2444 Optimize the pop-out window of Create Build.

2445 Click Link Product when a Create Build pop-out displayed. The style of that pop-out requires optimization.
2446 Image delete button on doc detail page is invalid.
2448 The number of block listed should be set.
2449 Resolved Build of a bug will contain the releases that is terminated and deleted.

2450 Duplicated dropdowns on the page of Project.
2451 Add Child Task buttons on My Dashboard and Task List are not in the same style.
2453 Delete the custom contact, and edit the user. Error.
2477 Fix the summary of Plans.
2612 Markdown will filter html tags.
2631 Activation Counts and Time of bug details are separated.
2632 Create Doc. Translation error of document names.
2633 Incomplete display of Cost and Left man-hour.
2634 Date on the page of Review Case Lib.
2684 Hide child categories of documents, but it is invalid.
2736 The width of bearychat webhook is not enough.
2759 Set tags as required field for bugs. Enter 0 and prompts as it cannot be black.
2777 If there is http info in the Markdown editor, error prompts.
2816 Batch add users. Save it and prompted as the password does not meet the requirements.
2825 Installation. SQL can check and delete zt_im_client.
2835 Markdown. Image link is not right.
2836 Privilege set for Test Request is not as it should be.
2837 SVN integration. Missing lines when diff.
2839 Types of recurred todos are not right.
2841 Save a comment. The loading icon is not right.
2843 ZenTao Tutorial. Prompts show that users have no privileges.
2851 Paste images and tables to a comment, but the data is not fully recorded in MySQL.
2852 Set customized required fields, then cases can't be imported to a case lib.
2856 Timeout during the installation is not taken care of.
2860 Issues in managing teams.
2861 Case title that are edited can't be updated to the case lib.
2862 Company-User. Check the finished todos of a user but it is not selected as green.
2863 Same titles are not the same in different interfaces.
2864 The style of plan list is not right.
2865 My Dashboard-QA-AssignedToMe is not displayed.
2866 Limited User privilege issues.
2867 Add the width of Project Alias on Product-Project.
2868 Interface of Bug Report is shown as interface.
2869 Jumpto address error when doing a Change Story.
2870 Left hours can be overridden if entering hours in reversed chronological order.
2871 The style of the Actions column need to be optimized once a new field is added.
2874 After recurred todo is deleted, it will still be created automatically. 
2875 Search table is not consistent with the one as required.
2876 Async sending. Assign bugs again that will cause the image not displayed.
2877 A bug that you have no privileges can be found and viewed through search.
2878 Resolved Time on a bug detail page is inaccurate.
2879 Click Next on the detail page, and the display is abnormal.
2880 Batch Close parent tasks, but the History is not accurate.
2881 Linked Case of a Test Request is Waiting.
2882 Todo reminders that belong to other users are sent to you.
2883 Toggle cases by clicking arrow buttons, then the steps are gone.
2884 When creating a project, choose a linked product. Error prompts.
2885 Admin account set a global custom field but it is invalid.
2886 Case Library. Click a case but it is not directed the detailed page.
2887 Name in Privilege list and that in a Menu is not the same.
2889 Personal notification via Dingding can only be @ phone number.

2890 No tips for Create Story.
2891 Parent-Child task list page. The name is not displayed totally.
2898 Click Same as Story when clicking Decompose Task, then the input boxes are overlapped.
2899 Add project linked products and plans and page error.
2900 Man-hour as a required field is invalid when creating a task.
2901 Project-Kanban. Customized Kanban and the page is not right.
2902 Upgraded to 11.7 and the custom bug types are gone.
2903 Manage a view and it does not apply to the product.
2905 File version number is not right.
2906 Title error.
2908 View cases by clicking pagers. It can't jump to the last build of the next case automatically.
2911 Toggle builds on the page of case, and the build number is wrong.

Download

Source Code Package

     Official Website    SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website    SourceForge

• Windows 32 bit one-click installation

     Official Website    SourceForge

• Windows one-click installation (No security Settings)

     Official Website    SourceForge

One-Click Installation  Packages for Linux (unzip to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website    SourceForge

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

PHP package

• DEB package:     Official Website    SourceForge

• RPM package:    Official Website    SourceForge 

Help

  Installation Manual

  Update Manual

If you have any questions or would like to get a free trial for more than three users, contact  Troy@easysoft.ltd for help.

About ZenTao Enterprise

For ZenTao Enterprise features, click  HERE .

Installation and Upgrade

• For the first-time Installation, refer to  H ERE.
• For upgrade (from Open Source Version), refer to HERE.

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website

• Windows 32 bit one-click installation

     Official Website

• Windows one-click installation (No security Settings)

     Official Website

One-Click Package  ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website

PHP package

• PHP 5.3-5.6 package:     Official Website

• PHP 7.0 package:           Official Website

• PHP 7.1 package:           Official Website

• PHP 7.2 package:           Official Website

ZenTao Desktop

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by  EasyCorp. It is self-hosted and cross-platform with various plug-ins and rich features. Click  HERE to know more about it.

ZenTao Desktop

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit  MacOS

ZenTao Desktop Server

Windows 64-bit    Windows 32-bit    Linux 64-bit    Linux 32-bit   MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy @easysoft.ltd for help.

About ZenTao Pro

For ZenTao Pro features, click HERE .

Installation and Upgrade

• For the first-time Installation, refer to http://www.zentao.pm/book/zentaopromanual/133.html
• For upgrade (from Open Source Version), refer to http://www.zentao.pm/book/zentaopromanual/131.html
• For update (from Lower Version), refer to http://www.zentao.pm/book/zentaopromanual/136.html

ZenTao Pro Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• PHP 5.3-5.6 package: Official Website SourceForge

• PHP 7.0 package: Official Website SourceForge

• PHP 7.1 package: Official Website SourceForge

• PHP 7.2 package: Official Website SourceForge

ZenTao Desktop

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by EasyCorp. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about it.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

image source: marketexpert24.com

Overview

Security undoubtedly has always been the topmost concern since the beginning of time and technology is not any exception. With the evolution of technology, it has become omnipresent but unfortunately, this evolution has also opened the gates for the ‘evolved uninvited’ - Hackers.

Active organizations in the digital ecosystem have continuously been adding upgraded security functionalities to their existing applications and implementing new strategies to provide better and safer services to their customers. This action has majorly found its usability in world wide web because it is generally said that presence on the web is the most effective way to increase brand awareness and establish your product into the user’s mind. However, it is also important to understand that security vulnerabilities are not only limited to the web, in fact, can also be induced (intentionally or unintentionally) into the physical systems which have a prolonged exposure.

The S cope of Penetration Testing

Also known as pen-testing, Penetration Testing Services are a set of an authorized and scheduled process that thoroughly analyzes the network for any potential vulnerabilities and tries to exploit them at the network level or at the code level. Pen-testing is a complex manual security testing process in which the authorized tester does the job of an unauthorized hacker to break into the company’s network security. An effective pen-testing process should:

• Confirm the existence of vulnerabilities

• Demonstrate the impact of the vulnerability exploit on the system

• A demonstration of how the solution can be linked to the loophole

• Demonstrate the use of effective technologies to acquire improved control over the system

External Penetration Testing

External pen-testing tests the company assets from an external environment, such as the hacker. In the course of an external pen-test, the ethical hacker or tester tries to gain access into the network architecture by leveraging the loopholes or vulnerabilities detected externally. The thoroughfare can also be attempted by gaining access to secure and privileged data such as payment info, email and other secured documents.

The tester tries to gather every piece of information from the targeted assets such as vulnerabilities, code flaws, open ports and general access related information. The moment, tester successfully exploits the loophole and creates a breach the objective of the pen-test is achieved. The tester then proceeds towards the next step of the test - internal penetration testing.

Internal Penetration Testing

This is the next step after external pen-testing, in which the tester checks the efficiency of the security network internally. In this testing technique, the ethical intruder gets to leverage the exploited vulnerability discovered during the external pen-test. From this initial breach point internal attacks are triggered, which bypasses a poorly secured domain network and may give complete control to the attacker. Various attacks are launched from multiple points to make sure that no loophole goes undetected/unattacked.

The information found on these attacked networks is then leveraged to exploit the deeper network. With a successful internal pen-test, the attacker may gain access to the entire mainframe and once this objective is achieved the test is concluded.

Advantages of Penetration Testing

• Detect Security Threats - A first-hand penetration test evaluates the defending strength of the security system for its users, applications, data and networks from internal and external intrusions. Pen-tests easily detect and dodges the unapproved intruders for making unauthorized attempts to protected assets. With regular and updated penetration testing , organizations can keep themselves safe from security breaches.

• Effectively prevent the rate of network downtime - The network downtime arising due to a security breach could be really hazardous and expensive for the organization. The recuperation, in this case, maybe quite steep and may include retention programs, legal issues, user protection, ROI issues and IT remediation efforts. If an organization needs to evade these aforementioned practices then penetration testing is surely the proactive saver here.

• Tests your cyber defense capability - A strategized penetration test helps both ways. It measures the organization’s cyber defense capability and also evaluates the responsiveness of the internal security team in times of breach. In the case of an intrusion, it shows how swift the security teams are and how efficiently they are able to block the tools used for the attack, loopholes and the penetration tester. Pen-test also keeps a check on the automatic threat detection system, if executed in place by the organization, whether or not it is sending immediate alerts to concerned departments in case of an intrusion.

• Ensure business continuity and maintain trust - Nobody believes someone who is not able to protect themselves. A security intrusion leaves a very negative impact and affects the loyalty of the customers, suppliers, investors and stakeholders. A pen-test ensures that your business runs smoothly with round the clock safety and negative disruption impact. The tests keep a stringent check on the network downtime, data breach and any potential losses in accessibility.

Footnote

Effective Penetration tests helps in managing risks properly. Thus the necessity of any such tests, conducted internally or externally, cannot be understated. The tests may take time in identifying the potential flaws, but would definitely pay in long-term towards safeguarding the security infrastructure of the organization. Ignoring the same is NOT recommended because at this very moment someone somewhere unauthorized, maybe trying to create a breach into your system.

About the author

Change Log

Story

3701 Free trial version. Batch add users and no upper limit of users added.        ..
4244 Implement Dingding personal message notification.
4377 Delete Ueditor code.
4391 Optimize the password submitted when login.
4409 Add WeChat Enterprise to webhook.
4426 Reduce the space of FinishedBy ad AssignedTo on the task list.
4427 Highlighted block in a project report should be the same style of  that in Level 1.5 navigation.
4430 Add the concept for users to choose from agile
4431 Product module is completely displayed in Project.
4432 Slow scrollbar of task list page on IE 11.

Bug

2516 Batch cancel is not working on the list page.
2759 When the tag of a bug is required, enter 0 and prompted it as empty,
2775 Vulnerable libraries of JavaScript.
2779 Wrong wording of point rules.
2780 ZenTao 11.6.3 release. Click the version info and prompted as no access.
2782 Click any task on Project-Task-Kanban, and click edit, then the page is partially displayed.
2783 Edit document categories, then the title of the popout window shows "Edit Module".
2787 Loophole in jQuery.
2788 Group view. Hours of a task can not be edited in AssignedTo.
2790 Linked Case is abnormal in Report.
2791 Add more than 15 users to a team and the page is displayed abnormally.
2792 No search for stages of stories in stories linked to a project.
2793 The width of Priority on Linked Case of Suite should be optimized.
2794 Parameters of a test request is lost when clicking the Sync button of a test case and the page was redirected.
2795 The name of a story is not displayed when opening a story.
2796 Batch Run test cases will update automatically with the changes of the original cases.
2797 Dashboard->Effort. Add Effort and wrong wording displays.
2798 Linked Module is not displayed in a parent task on a task List.
2799 Run button is missing on the page of a test request.
2800 Widths of all fields related to projects should be adjusted.
2801 Click Confirm button of a bug, and a new type of bug is displayed.
2804 Project->Story->Kanban. The columns of colors are not aligned.
2805 Edit a block and the length of its name is added.
2806 Choose a build for a bug, and other projects can be selected too.
2807 Document-Basic info. The length of updateddate is overflown.
2808 Use a proxy of Nginx and it can't login.
2809 Case status in a test request is not right.
2810 The style of Report Bug page on ZenTao Desktop is not right.

2812 Optimize the logic of updating a privilege list.
2813 Roadmap in a block is not the same as itself.
2814 Document-Basic info. Collapse logic is not the same as others.
2815 Tasks can be Batch Assigned to deleted users.
2816 Batch Add users. Click Save and prompted not right password.
2818 Password strength check is not right.
2819 Project team member is removed, then the man-hour is not updated.
2820 Capitalized letters in front of bug types are checked.
2823 Privileges set are not working.
2826 Save pasted images and edit it. The uploading image will be prompted as saved as one image.
2828 Incomplete title of cases displayed on a Story page.
2830 Installation stopped at the last step.
2832 Prerequisite of a case is not doing line break.
2833 Check the deletion of zt_workflow when upgrading to Enterprise and running SQL.
2834 Data in Test Request and Report is not consistent.
2838 Resolve the build creating issue.
2840 Man-hour is not calculated right in project-group by.
2842 Edit a comment and enter 0. Then prompted as empty.
2844 Dingding. Click Link ZenTao and erroneous redirection.
2845 Department. The field of order affects ordering.
2846 ID of Todos will break line if it is too long.
2847 Batch Activate bugs and not activated time.
2849 Task modules display IDs but not titles in the exported report.
2850 Click Update button on Case page and not valid.
2853 Change the stage on Edit Story page and nothing is changed.
2854 Dashboard-Profile. Click and error prompts.

Download

Source Code Package

Official Website SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Installation Packages for Linux (unzip to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• DEB package: Official Website SourceForge

• RPM package: Official Website SourceForge

Help

Installation Manual

Update Manual

If you have any questions or would like to get a free trial for more than three users, contact Renee @easysoft.ltd for help.

About ZenTao Enterprise

For ZenTao Enterprise features, click HERE .

Change Log

Bugs

9288 Logout time in Attendance is not right.
9287 Trip and Egress is in OA reports.
9286 Set privileges in Feedback. Neither Developer nor Non-Developer users can see public feedback in ALL list.
9285 Click Workflow to check and error page showed.
9284 Click Leave and save. No response.
9283 Force to change password after login the mobile app.
9282 Department attendance is not displayed.
9281 Create Task and error prompts.
9280 User login and jump to the Change Password page.
9279 Attendance. Department cannot be selected on the detail page.
9278 Attendance. Date is not displayed completely.
9277 Attendance. Log error.
9276 Plan of 2020 cannot be displayed.
9275 Item count is not accurate.
9249 Workflow->Add Field->Dropdown. Product branch is not displayed.
9248 Workflow->Add Field. Field is not displayed.
9247 Delete a subflow. ZenTao MySQL is affected.
9246 Added fields cannot be exported.
9244 Prompt which is displayed after a field is added should be consistent with that in the system.
9243 Actions added cannot be seen by users.
9242 Actions added to a bug. The datasource of the affected version is wrong.
9241 Actions added in built-in workflow are not displayed by triggers.
9240 A sub status is added to a task, but the task is not displayed in the lane.
9239 Verification set to the added actions. Its field is not saved.
9237 Sub status of a task is not displayed in the dropdown.
9236 Add a new workflow to the second navigation, but it is not displayed.
9235 Display added workflow and child flow separate;y in Company->Privilege.

9234 Set a subflow but it is not displayed in the parent flow.
9233 Submit a form in the parent flow. Its field is the key of a child flow, and it is not displayed.
9232 Data verification of actions failed.
9231 Export in built-in flow is invalid.
9230 Add Field. The style of the required field need to be optimized.
9229 Add fields to a child flow. Click all but it is not displayed.
9228 Set fields of a child flow checked, but uniqueness is not checked.
9227 Save and Return buttons and positions should be the same.
9225 Entry to set privileges for the added actions of a workflow is not found.
9224 Set the added field as required, but it is not working.
9223 Delete a newly added field in the custom list but an error prompt.
9222 Parameters of a function called are missing.
9221 Built-in form has to be confirmed whether it can be deleted.
9220 Data of the added workflow cannot be exported.2

Installation and Upgrade

• For the first-time Installation, refer to H ERE.
• For upgrade (from Open Source Version), refer to HERE.

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website

• Windows 32 bit one-click installation

Official Website

• Windows one-click installation (No security Settings)

Official Website

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website

PHP package

• PHP 5.3-5.6 package: Official Website

• PHP 7.0 package: Official Website

• PHP 7.1 package: Official Website

• PHP 7.2 package: Official Website

If you have any questions or would like to get a free trial for more than three users, contact Philip @easysoft.ltd for help.

About ZenTao Pro

For ZenTao Pro features, click  HERE .

Installation and Upgrade

• For the first-time Installation, refer to  http://www.zentao.pm/book/zentaopromanual/133.html
• For upgrade (from Open Source Version), refer to  http://www.zentao.pm/book/zentaopromanual/131.html
• For update (from Lower Version), refer to   http://www.zentao.pm/book/zentaopromanual/136.html

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

     Official Website    SourceForge

• Windows 32 bit one-click installation

     Official Website    SourceForge

• Windows one-click installation (No security Settings)

     Official Website    SourceForge

One-Click Package  ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu17+ and Centos7.4+ )

     Official Website    SourceForge

• Linux 64 bit one-click installation   ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

• Linux 32 bit one-click installation  ( Ubuntu16- and Centos7.3- )

     Official Website    SourceForge

PHP package

• PHP 5.3-5.6 package:     Official Website    SourceForge

• PHP 7.0 package:           Official Website    SourceForge 

• PHP 7.1 package:           Official Website    SourceForge

• PHP 7.2 package:           Official Website    SourceForge 

If you have any questions or would like to get a free trial for more than three users, contact  Troy@easysoft.ltd for help.

Change Log

Story

4411 Optimize the display of child plans in Product Summary report.

Bug

2821 QA. Click the title of  a case and an error prompts.

2822 Click Case Library and error prompts.

2824 Segment fault in /module/task/view/create.html.php. Line 199行 and Line 151 cause error page.

2831 Privilege name is not the same as that in the menu.

2833 Fix WebHook to support Dingding.

Download

Source Code Package

Official Website SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Installation Packages for Linux (unzip to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• DEB package: Official Website SourceForge

• RPM package: Official Website SourceForge

Help

Installation Manual

Update Manual

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

For the last two months, our team completely restructured ZenTaoATF with a lot of discussions, quarrels, and development. This refactoring focused on the development language, the organization of use case scripts, and the integration of ZenTao. We refactored the ATF using the GO language, which truly enables a an executable file that is platform-free and deployment-free dependencies. The syntax of the test script is also restructured, which can support multiple use cases in one script and greatly simplifies the maintenance cost of automated test scripts. It is also deeply integrated with ZenTao ALM, which can bind the use cases in ZenTao with the automated test scripts and submit the execution results of execution to ZenTao as test results. Failed scripts can also be reported as bugs in ZenTao.

Compared with other automated test frameworks based on recorded return visits, ZenTaoATF is a solution that is independent of the development language and implementation mode. Users can also implement automated test scripts using the methods they have been using, and the organization, execution, comparison of results, and docking of the test management system are all done by ZenTaoATF.  

ZenTaoATF Official Website

https://ztesting.net/

Changelog

1. Use Go Lang to reconstruct the framework and support cross-platform;
2. Integrate with ZenTao ALM;
3. Redefine the syntax and suppport multiple cases and groups in one script;
4. Support more languages.

Download

• ztf-linux-2.0.zip
• ztf-mac-2.0.zip
• ztf-win-2.0.zip
• Source Code  (zip)
• GitHub

Help

  https://ztesting.net/book/ztf-doc/ztf-about-26.html

Screenshots

print test results

Report a bug

Nowadays, the movie has indeed entered thousands of households, but do you know how the film works behind it? The complexity of a film and television project is no different from software development projects. In an film and television project, the producer is crucial. Producers are people who initiate, coordinate, supervise and manage the production of film and television. They also participate in all stages of the project from production to completion, which is similar to what project managers do in the software development projects. 

In the past, producers often use common office software to  manage the projects, but there were too many parties to work with, and the information gathered from each party is messy and too much and difficult to sort out. Take making our short film project  The Legend of ZenTao  as an example to see how producers use project management software to manage film and television projects.

Create Project

Go to Project view and add a project. Enter project related information, such as project name and project time frame.

Set Team

There are a large number of teams involved in the film and television production. According to the actual situation, a Camera team, a Lighting team, a Cast team, a Post-Production team, a Costume and Prop team, and a Promotion team are set for The Legend of ZenTao production. Then enter the available man-hour for each team.

Task Breakdown

Once all teams are set, the next step is to create tasks. Enter the task name, its description, etc. Assign it to the relevant person, and set the time required to finish it.

The whole process is defined and clear, so each team member will be very clear about what have to be do done. Then update the task progress and status in time.

Manage Task

On the page of the task list, you can see all the tasks, which is convenient for the producers to understand the current progress of each team, and to find and deal with the problems in the project.

Besides, the work of the producer is often messy, but it can be managed in the ZenTao.

Personal Todo Management

Go to Dashboard, and select the Schedule -> add Todo -> record recent work as todos, so that no work is missed; todos can be prioritized according to the importance of work.

If a todo conflicts with other tasks, assign it to other team members to do it.

Conclusion

Professional project management software help the project avoid detours in the production. If you also have a team facing the same cumbersome management problems, you should try ZenTao or search for project management software to help you solve the problem.

ZenTao is a complete professional Application Lifecycle Management tool.

Then I realize immediately that ZenTao is appropriate for webmasters, bloggers and publishers who maintain a website. ZenTao is not necessary only for development. In this case  that the QA module is not used, neither are plan, builds,  releases, etc... But stories, tasks, projects and products are quite usable. And the Doc module too.

ZenTao VS other management tools

In my work in mainframe industry, developing in COBOL, we are trying to do Scrum and we have worked with:

Jira Software is expensive and very complex and the roles are not clearly identified. You can set parameters for everything and then it becomes very complex. Sometimes, people prefer Trello because it is simple and you don't have to set "a million" parameters. However, Trello has cons, because it is too simple and you can not use it for project management. ZenTao is quite right. It has just the right number of parameters necessary to do a specific work. So you understand it immediately if it's your work. If you know a little of AGILE method you understand product, project, sprint, story, task and you understand immediately the help ZenTao can bring to you.

If you work in the construction of houses, you have no need to use a hammer that can be transformed in multiple forms. You just need to use a hammer. Period.

Quality Center is complex and it takes a lot of time to use it properly. Teams have no time to use it properly so Quality Center is often used to transmit testing documents from one team to another and is not really used for test requests. It become a giant tool to do very simple things. Some company use it like a DMS Tool.

More than a tool just for development projects

And now I realize ZenTao can be adapted for every kind of projects with just minimum changes.

If you imagine a V-Model Project a Scrum Project with only 1 iteration and a sprint duration of 1 or 2 years, you can use ZenTao to manage it. There is just a lack in the analyze phase. But to be scrum, it must be simple and reactive, short and quick.

For all projects, you have requirements and constraints. But sometime you have new requirements and constraints that appear during the implementation of the project. Then, you have just to analyze and give new rules to integrate in new stories, link to a sprint, and made new single tasks to respect these new requirements and new constraints, which is not a problem, really.

For webmasters and publishers, there are not such need. You can use ZenTao without the QA module. But when you get a new customer to develop a new website, you have to take notes of what your customer tells you, his needs, his requirements, etc. After that you can analyze the data and comment them. You finally write a document with all the requirements and mock-up of the project (like screen shot, etc...). The document must be validated by the customer and you can put it in the ZenTao Doc module. You can start creating stories, tasks, sprints... The before-project stage is a part of the job.

Manage projects using ZenTao

With some simple changes, you can easily transform ZenTao.

You have a parameter like this when choosing the concept:

It can be a parameter like this for:

Note: a V Cycle Project can be waterfall or not.

Maintain a project

Conclusion

With little adaptations, ZenTao can be used to manage all these kind of projects because I think ZenTao now is mature to do it. A few years ago I think it can't unless a lot of evolution. Now I think ZenTao is ready to be extended to all kind of projects.

AUTHOR

I researched few tools to get solution for problem related to test management in agile. In my research i have found very promising tool ZENTAO ( Zen-t-o) which can handle both agile project management as well as Test Management activities complete delivery cycles. I am presenting video series based on my personal research and usage of Zentao both in Agile Project Management and Test Management. Most amazing part of this tool is we can configure this tool for any of following mode.

• Agile Project Management
• Product Management
• Test Management (only)
• Agile Project Management with Test Management
• Product Management with Test Management

This tool is available in both Open-source and Licensed versions. Based on organizational / project needs one can opt for any of its versions.

Please see my video post on Test management using Zentao.

2) To be continued...

I researched few tools to get solution for problem related to test management in agile. In my research i have found very promising tool ZENTAO ( Zen-t-o) which can handle both agile project management as well as Test Management activities complete delivery cycles. I am presenting video series based on my personal research and usage of Zentao both in Agile Project Management and Test Management. Most amazing part of this tool is we can configure this tool for any of following mode.

• Agile Project Management
• Product Management
• Test Management (only)
• Agile Project Management with Test Management
• Product Management with Test Management

This tool is available in both Open-source and Licensed versions. Based on organizational / project needs one can opt for any of its versions.

Please see my video post on Test management using Zentao.

2) To be continued...

Change Log

Story

4349 Username include ‘.’

4390 Add translator info to About.

4392 Switch DocLibs when managing document categories, move documents to the new DocLib.

Bug

2438 Test Request. Display Case RunBy as Real Name.
2567 Batch Delete is not set as in Privilege.
2587 Fake CSRF reported by users.
2596 Case batch run data is not included in QA report.
2599 Delete a child task but it is not recorded in the history of the parent.
2614 Repro Steps template in Report Bug page can only be deleted by the CreatedBy.
2616 Image uploaded as Custom Doc and the hyperlink is replaced by an image.
2621 ZenTao Desktop error.
2622 Delete a child task, the the effort of the parent cannot be maintained.
2626 Admin->Develop. Click Database and error prompts.
2627 Project->Team. A deleted team can be copied.
2628 Parent tasks cannot be activated.
2629 A parent with a deleted task cannot be viewed in Task Kanban.
2630 Delete a child task, then the man-hour is miscalculated.
2641 Optimize the position of bug types.
2648 Inaccurate privileges prompts in Bug.
2652 Remove cases linked to a test request, then the pager column looks abnormal.
2657 Add a story. Module dropdown cannot display the right value.
2661 Case Lib error prompts.
2662 Click Save after Create Story but no response.
2663 Project-Document. Dropdown content displayed in the wrong position.
2666 Click Done to Fixed for a story. Then the linked plan is missing.
2681 Report bugs for a multi-branch product, and the page is abnormal.
2684 Document. Child category is invalid.
2686 Style of My Doc overflows.
2689 Batch Edit bugs failed.
2690 Create Case. Linked story list contains Closed stories.
2691 Dropdown is overlapped in Product.
2692 Tips for Save buttons are not the same.
2714 Test Request. Search case status but the results are inaccurate.
2716 Activate a test request and error prompts.
2717 Email list status is not consistent.
2718 Link a bug and it cannot be cancelled.
2719 Link test suites to cases. Go to the detailed page of a test suite, and an error prompts.
2720 Test Request. Detail page. Run button styles are not the same.
2721 Space is added to the code editor automatically.
2724 Link a project to multiple projects. Stories linked to the project plan is not reminded.
2725 Optimize the introduction of Y-Disk and MeshIoT on Installation interface.
2727 Paste an image and cancelled it. Paste it again but the image is reversed.
2728 Import bugs from  a project. Resolved bugs will be listed.
2729 Log in ZenTao Desktop and it will be recorded login twice.
2730 Edit a todo but it is not updated in Calendar.
2731 Change search conditions and choose Last Week, but nothing happened.
2733 php7.2 compatibility.
2735 Edit a module, and click Close. Background color and copy template buttons are missing.
2737 Create a task in Project but cannot be linked to stories.
2738 Test Request list. Click Run and it is not working.
2739 QA-Bug-Batch Report. A story can be linked to more than one module.
2740 No sign for bug types on Required setting page.
2741 Product dropdown is not consistent with other product layout.
2743 Task estimates can be negative.
2744 Add User page and Change Password page contain cleartext submission.
2747 Project story list. Names of stories in draft is not localized names.
2748 Translate. If the translated item is the same as the original item, it cannot be saved.
2749 Status is missing after editing a case.
2750 Comment and Edit buttons are overlapped.
2751 XSS loophole.
2752 Optimize the Change button of story on project task list page.
2753 Test Request. Clicking Run and error prompts.
2754 Tutorial. Create a user/project/product, and the translation is not working.
2756 Test Request. Link new cases but they cannot be run.
2757 Create a project. Link a plan and stories not linked to the plan will be linked to the project.
2758 Start and finish a task. Add a comment but not displayed in the history.
2760 Password is not working when batch creating users.
2761 Optimize names of roadmaps.
2762 Admin-Develop-Database. Xuanxuan is abnormal.
2763 Close test request page and error prompts.
2764 Batch create tasks and Edit. Start and Finish date is not validated.
2765 Add links to documents and error prompts.
2767 Invalid restriction on Translation.
2768 Todo status on Dashboard and Company-User is not consistent.
2769 Product-Story. Phase of a story can't be changed.
2771 No password login is not validated by timestamp.
2772 Active product. Current list error.
2773 Manager of a module cannot be set.
2774 No password login is not listed in Dynamics.
2776 Case links on QA report are invalid.
2778 11.6.3. Upload .csv and no data error.
2781 Backup size in Admin error.

Download

Source Code Package

Official Website SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Installation Packages for Linux (unzip to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• DEB package: Official Website SourceForge

• RPM package: Official Website SourceForge

Help

Installation Manual

Update Manual

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

What is a typical To-Business(2B) product in your mind?

Complex and difficult to use, complicated operation, old-fashioned interface...

How would you optimize a 2B product?

What a designer would do is nothing more than changing the interface, choosing a set of matching theme colors, and adding some guidance for actions ... More radical designers might say "Let's refactor the layout!"

2B products have undergone so many adjustments and iterations, and the underlying logical structure has long been perfect. Reconstructing the layout will not only subvert the user's past operating habits, but may even lose a batch of users.

What would a UX Designer do to optimize the user experience to a powerful and a To-Business product?

Designing for a 2B enterprise management software is not only the designing about a process but also about management. CEO Mental Model, a thinking model refined by AIUX, is prepared to optimize the design of 2B products.

Control

Why does the sense of control have to be involved in a 2B product?

Suppose the user is at the starting point, and the task that he tries to do is to get to the endpoint. What would you do to get to the endpoint from the starting point?

A common practice is to ask for directions.

Standing at a strange crossing and asking for directions, you will usually be told by an enthusiastic passer-by to turn left at a crossing and then turn right at the next one. In the end, you end up asking another enthusiastic passer-by.

Why is this happening? 

Your view is limited by, and so is your cognition.

You might reach the end point, but it might take you a while. 

Let's see it from an aerial view

An aerial view brings you completely different information. The directions of the road, every building and even every plant are in your sight as a panoramic view. This is also what the users of a 2B product want, a sense of control, which can show you each phase of a task, as well as what is done and what to do, so you can easily plan for tasks.

Below is another example.

Can you find the delayed tasks in the lists?

A list is often used in the modules of a 2B product. Usually, designers would only arrange the information in the order of states or chronological order. When the users landed on this page, they will see all the information.

Users will miss the target of the page and lose the overall control of the page, because the extremely high similarity among the modules, which makes it difficult for the users to get the most important information in a short time. 

What would a UX designer do?

Based on creating a sense of purpose and control, a module of statistics as shown below has been added, which is not just an overview of data.

First of all, a UX Designer would analyze the important data that flow in the product, such as my task, my bug, my story, etc.

Secondly, conduct an in-depth discussion of the data. Take the data of a bug as an example. Besides the total number of bugs, what do users care about? It can be categorized briefly as,

1. Whether the bug to be fixed is delayed; 2. How many bugs have been added; 3. How many bugs have been resolved？

Finally, the data overview of the added module is generally completed. It creates an atmosphere that the users understand the whole situation of bugs once they land on the page through the overview of key factors and tags. (What bugs I am going to deal with? What are they? Is any bug delayed?...)

Efficiency

Before talking about efficiency, let's talk about the process of making coffee. Some love the mellow taste of handmade coffee, and some prefer instant coffee.

It takes about 10 steps to make a cup of handmade coffee, but for a cup of instant coffee， it only takes one. For different purposes, consumers choose different coffee. In a sunny Sunday afternoon, enjoy the handmade coffee and its mellow taste; on a busy working day, instant coffee can quickly refresh you.

It is also true in UX design. Users' current scenario is analyzed and a suitable "coffee" is then selected for them. It is the purpose of 2B product design to improve efficiency.

The efficiency of a 2B product is more reflected in quickly obtaining valid information and completing tasks. Features such as editing are added in 2B products, but users' ability to quickly and directly land to the feature is overlooked.

My team optimizes the UX of a 2B product which is for enterprise management.

This product has a lot of batch actions for different stages and modules of each workflow. However, the hierarchical design of batch actions is relatively deep (as shown in the original path below), for users who have just started to use it, so it is difficult for them to find the right actions quickly and accurately.

Based on the research and interviews with users, we learned that in the actual use scenario, the user first completes the entire requirements document online, and after confirmation, the relevant person in charge is uniformly entered into the system.

Based on the research and interviews with its users, my team learned that users first completes the entire PRD (product requirements document) offline and then the manager will enter the requirements into the system after getting confirmation within the team.

Based on the analysis of various aspects and scenarios, the conclusion is that “batch action” is an important action with a relatively high-frequency. The solution is to enhance the presentation of batch actions, display the batch action in a more conspicuous position and shorten the path for users. Therefore, the efficiency of the users' action is improved.

Operability

In 1956, George A. Miller discovered "The Magic number 7 (plus or minus two)' which provides evidence for the capacity of short term memory. It proves that most adults can store between 5 and 9 items in their short-term memory. If there are more than 9 items of information to remember, the human mind is prone to error. Therefore, the magic number 7±2 rule is often applied to the interaction design of mobile applications, e.g. design no more than 5 tabs for an application.

Based on this finding, my team believed that the error rate increases when the users select  the same target for too many times, and it becomes relatively weak to accurately perform  the corresponding action and control it. Let's call it a weak operable action.

For 2B products, the operability is closely related to scenarios, which also affects the psychological state of the user. A useful and practical 2b product enables an easy schedule for users and handles them conveniently. Therefore, it is essential to design the operability of 2B products.

The above image is a "list" module of a 2B product, which contains a lot of actions. My team has processed the information. The gray bars represent the name of the object in different states; blue bars represent the "assignee"; the blue action represents the "action". It is obvious the actions corresponding to the object in different states are slightly different, which is mainly reflected in whether "the action can be executed in the current state".

What issue do you see in the list module above?

1. The object has too many actions. For new users, it is easy but also can be discouraging. It is possible that they feel it very troublesome and give up. For long-term users, too many actions mean high memory costs and not so operable;

2. Considering the workflow that users use and listing all those often-used actions, it seems to be convenient and direct, but might be not so.

How to optimize this list?

1. Analyze what is the substance behind “actions” and classify them according to the analysis. Actions can be categorized into the following three categories,

2. Considering the workflow used by users and positioning the classified actions.

• “Assign” action is highly relevant to “Assignee”. C reate a stronger sense of the scene by integrating “Assign” action with “Assignee”;

• Integrate three actions regrading state changing, according to the state of the object, the priority of display, and the "hover state of the mouse". Hide other actions regarding state changing;

• For common and relatively independent actions, keep them on the list.

3. Design according to the analysis above. The revised version is more concise. Considering users' actual workflow, three important actions are remained, which improves the overall operability and lower the challenging to remember for users.

Conclusion

The essence of UX design in 2B products according to the "CEO" model is reflected in two aspects.

1. Abstraction of standard workflows

Abstracted standardized workflows enable employees in the company to work more professionally at a lower cost, and more efficient flow between tasks and workflows.

2. Production of management thinking

Management philosophy is demonstrate in a product/system, and work is done with basic controls, such as forms, buttons, labels, etc.

"CEO Mental Model" is not the only design method, but a product design thinking for the 2B product. Designing for 2B enterprise management software is not only about a process, but also about a management method. I hope that "CEO thinking" can be enlightenment.

What is a typical To-Business(2B) product in your mind?

Complex and difficult to use, complicated operation, old-fashioned interface...

How would you optimize a 2B product?

What a designer would do is nothing more than changing the interface, choosing a set of matching theme colors, and adding some guidance for actions ... More radical designers might say "Let's refactor the layout!"

2B products have undergone so many adjustments and iterations, and the underlying logical structure has long been perfect. Reconstructing the layout will not only subvert the user's past operating habits, but may even lose a batch of users.

What would a UX Designer do to optimize the user experience to a powerful and a To-Business product?

Designing for a 2B enterprise management software is not only the designing about a process but also about management. CEO Mental Model, a thinking model refined by AIUX, is prepared to optimize the design of 2B products.

Control

Why does the sense of control have to be involved in a 2B product?

Suppose the user is at the starting point, and the task that he tries to do is to get to the endpoint. What would you do to get to the endpoint from the starting point?

A common practice is to ask for directions.

Standing at a strange crossing and asking for directions, you will usually be told by an enthusiastic passer-by to turn left at a crossing and then turn right at the next one. In the end, you end up asking another enthusiastic passer-by.

Why is this happening?

Your view is limited by, and so is your cognition.

You might reach the end point, but it might take you a while.

Let's see it from an aerial view

An aerial view brings you completely different information. The directions of the road, every building and even every plant are in your sight as a panoramic view. This is also what the users of a 2B product want, a sense of control, which can show you each phase of a task, as well as what is done and what to do, so you can easily plan for tasks.

Below is another example.

Can you find the delayed tasks in the lists?

A list is often used in the modules of a 2B product. Usually, designers would only arrange the information in the order of states or chronological order. When the users landed on this page, they will see all the information.

Users will miss the target of the page and lose the overall control of the page, because the extremely high similarity among the modules, which makes it difficult for the users to get the most important information in a short time.

What would a UX designer do?

Based on creating a sense of purpose and control, a module of statistics as shown below has been added, which is not just an overview of data.

First of all, a UX Designer would analyze the important data that flow in the product, such as my task, my bug, my story, etc.

Secondly, conduct an in-depth discussion of the data. Take the data of a bug as an example. Besides the total number of bugs, what do users care about? It can be categorized briefly as,

1. Whether the bug to be fixed is delayed; 2. How many bugs have been added; 3. How many bugs have been resolved？

Finally, the data overview of the added module is generally completed. It creates an atmosphere that the users understand the whole situation of bugs once they land on the page through the overview of key factors and tags. (What bugs I am going to deal with? What are they? Is any bug delayed?...)

Efficiency

Before talking about efficiency, let's talk about the process of making coffee. Some love the mellow taste of handmade coffee, and some prefer instant coffee.

It takes about 10 steps to make a cup of handmade coffee, but for a cup of instant coffee， it only takes one. For different purposes, consumers choose different coffee. In a sunny Sunday afternoon, enjoy the handmade coffee and its mellow taste; on a busy working day, instant coffee can quickly refresh you.

It is also true in UX design. Users' current scenario is analyzed and a suitable "coffee" is then selected for them. It is the purpose of 2B product design to improve efficiency.

The efficiency of a 2B product is more reflected in quickly obtaining valid information and completing tasks. Features such as editing are added in 2B products, but users' ability to quickly and directly land to the feature is overlooked.

My team optimizes the UX of a 2B product which is for enterprise management.

This product has a lot of batch actions for different stages and modules of each workflow. However, the hierarchical design of batch actions is relatively deep (as shown in the original path below), for users who have just started to use it, so it is difficult for them to find the right actions quickly and accurately.

Based on the research and interviews with users, we learned that in the actual use scenario, the user first completes the entire requirements document online, and after confirmation, the relevant person in charge is uniformly entered into the system.

Based on the research and interviews with its users, my team learned that users first completes the entire PRD (product requirements document) offline and then the manager will enter the requirements into the system after getting confirmation within the team.

Based on the analysis of various aspects and scenarios, the conclusion is that “batch action” is an important action with a relatively high-frequency. The solution is to enhance the presentation of batch actions, display the batch action in a more conspicuous position and shorten the path for users. Therefore, the efficiency of the users' action is improved.

Operability

In 1956, George A. Miller discovered "The Magic number 7 (plus or minus two)' which provides evidence for the capacity of short term memory. It proves that most adults can store between 5 and 9 items in their short-term memory. If there are more than 9 items of information to remember, the human mind is prone to error. Therefore, the magic number 7±2 rule is often applied to the interaction design of mobile applications, e.g. design no more than 5 tabs for an application.

Based on this finding, my team believed that the error rate increases when the users select the same target for too many times, and it becomes relatively weak to accurately perform the corresponding action and control it. Let's call it a weak operable action.

For 2B products, the operability is closely related to scenarios, which also affects the psychological state of the user. A useful and practical 2b product enables an easy schedule for users and handles them conveniently. Therefore, it is essential to design the operability of 2B products.

The above image is a "list" module of a 2B product, which contains a lot of actions. My team has processed the information. The gray bars represent the name of the object in different states; blue bars represent the "assignee"; the blue action represents the "action". It is obvious the actions corresponding to the object in different states are slightly different, which is mainly reflected in whether "the action can be executed in the current state".

What issue do you see in the list module above?

1. The object has too many actions. For new users, it is easy but also can be discouraging. It is possible that they feel it very troublesome and give up. For long-term users, too many actions mean high memory costs and not so operable;

2. Considering the workflow that users use and listing all those often-used actions, it seems to be convenient and direct, but might be not so.

How to optimize this list?

1. Analyze what is the substance behind “actions” and classify them according to the analysis. Actions can be categorized into the following three categories,

2. Considering the workflow used by users and positioning the classified actions.

• “Assign” action is highly relevant to “Assignee”. C reate a stronger sense of the scene by integrating “Assign” action with “Assignee”;

• Integrate three actions regrading state changing, according to the state of the object, the priority of display, and the "hover state of the mouse". Hide other actions regarding state changing;

• For common and relatively independent actions, keep them on the list.

3. Design according to the analysis above. The revised version is more concise. Considering users' actual workflow, three important actions are remained, which improves the overall operability and lower the challenging to remember for users.

Conclusion

The essence of UX design in 2B products according to the "CEO" model is reflected in two aspects.

1. Abstraction of standard workflows

Abstracted standardized workflows enable employees in the company to work more professionally at a lower cost, and more efficient flow between tasks and workflows.

2. Production of management thinking

Management philosophy is demonstrate in a product/system, and work is done with basic controls, such as forms, buttons, labels, etc.

"CEO Mental Model" is not the only design method, but a product design thinking for the 2B product. Designing for 2B enterprise management software is not only about a process, but also about a management method. I hope that "CEO thinking" can be enlightenment.

My name is Niclas Hedhman, a long-term Apache Software Foundation contributor. I have worked 32 years as a software developer, and over the years I have made many observations. And latest observation is about something that is so obvious that we don’t notice it. The “Elephant in the Room” is an expression in English, aboutthe obvious things that no one dares to talk about. In this presentation, I want to bring up the topic in the Software Industry, that no one dares to talk about, but is paramount to bring us to the next level.

I mentioned that I have made observations. We all make observations. Almost everyone has seen beautiful code. It is concise, it is simple yet powerful, it speaks to us in an easy to understand abstraction, it is easy to use, easy to extend. We can quickly do our job, get things done. However, if we ask people if the work on beautiful code, most people say No. So where is this code coming from? Well, very few developers are responsible for these gems.

On the other hand, Bad Code is everywhere. We have all seen bad code. Many of us are fighting bad code on a daily basis, and we are all guilty of creating more bad code.

But WHY? Why do you create bad code? You know it is bad when you write it. Why, why, why?

If we listen to ourselves, we will hear statements like these; It is already bad. I can’t improve it, because there are no Tests or that the codebase is too complex. It is too risky to make needed changes. I am so busy now. We have a deadline, and we will fix this later when we have more time. Right now, we need to focus to push this out the door.Hey, I don’t think it is bad. My teammates are unhappy about it, but I think they are not smart enough to appreciate this.

And I say that all of such statements are buuuuuulllshit. Those are excuses, because otherwise we can’t live with ourselves. How could we go to work, knowingly do a bad job and not be ashamed ourselves to the point of changing careers?

My hypothesis is that there is something much much deeper to the long-standing crisis in our industry. And I find it profoundly disturbing.

First, let’s look at some facts. Our industry is changing at a remarkable speed. New technologies appear almost weekly, and have done so for the last 30 years that I have been around. There are practically no limits to what people create. And the amount of things there is to learn is staggering. Open source is now so common place, that we never ever start from scratch. We build upon existing platforms, combining existing things in new ways, add our own innovations on top, and quite often we release that as open source for other to build on top of that, or be
inspired to build something else. This result in an unprecedented acceleration of output.

Can anyone tell me what this graph is?

This is a the growth curve of number of programmers in the world. The exact numbers are not important, although it is estimated to be in the 50-100 million range. What is important is that it doubles every 5 years or so. It has been doing that almost nonstop since 1950. Every 5 years, the number of programmers in the world has doubled.

So, we have an industry that is extremely inexperienced. There is a perpetual lack of experience. Worse yet, since the technology landscape changes so quickly, there is not enough time to become experienced before the technology is out of fashion and every cool kid on the block have moved on. This leads to the same mistakes are made over and over again.

Most programmers don’t invent new technologies for others to use. We adopt technologies that got talked about a lot. We trust others to have figured out what is good for us. We don’t apply critical thinking. Let me repeat that. We don’t think critically, and in faith-like fashion believe what we are told. That is a clue to where I am going with this.

Let’s move on to myths in our industry. And there are a lot. Since we act like a religious sect, many myths have risen incidentally or on purpose.

Myths are created and spread by certain types of people. People that we respect and therefor we are very vulnerable to what they have to say. Vendors try to sell us product and services. Likewise speakers at conferences, authors of books and bloggers that we read, more often than not are also selling their books, sites or services. At work, we listen to people more senior than us, typically those colleagues that have a string of successes behind them, but if it is a big company there are politics and prestige at play, which we should also question.

So let’s look at typical myths that are so called common knowledge.

Myth # 1. Software is Easy to Change.

Myth # 2. More People=More Result

This myth is prevalent in company management. If we need to do twice as much, we hire twice as many programmers. That will do it. The Mythical Man-Month was a book published in 1975. 1975. 40 years ago. The author Fred Brooks observed that adding more people to a project behind schedule would in fact make the project even slower. Eventually, the communication required to coordinate between people will take more than all the time of each person.

Myth # 3. Programmers are INTERCHANGEABLE!

Another favorite among managers in large companies, is that programmers are interchangeable parts. If one programmers leaves, we just pick a new one from the street to replace her. Except that doesn’t work. Software knowledge is not in the code. It sits in the brain of the people that created the code. If you have ever come in to rescue a codebase where all the previous programmers left without any handover, then you know what I am talking about. If the creator of the codebase quit, it takes 2 new people to replace her, and it may take them a year before they think they understand what the creator meant, perhaps never.

Myth # 4. Abstractions are GOOD!

Here is one of my favorites. We wouldn’t have the Internet and all its fascinating sites on it, if it wasn’t for abstractions. If we had to write binary instructions for the CPU, we would have problem to create the simplest of programs. Programming languages, protocols, data formats, frameworks and much more are abstractions helping us to do our job.

But most abstractions are in done in the programs that we write. We create our own small clever abstractions, without enough clarity, without the experience of what makes good abstractions, and we make a mess. Our own abstractions, more often than not, are horrible, confusing and outright detrimental to our projects.

Myth # 5. Methodology X solves Y

There are many peddlers of methodologies. It was Objectory with use-cases in the late 1980s, then came the Rational Unified Process and many other so called CASE (Computer Aided Software Engineering) tools, settling on Unified Modeling Language, or UML. Kent Beck introduced us to Extreme Programming, which was the first agile methodology as a revolt against the so called waterfall methodologies. Scrum, Kanban and others have been touted in the last 10 years or so. All promising to solve the complexity of creating software.

My observation is that no methodology works as advertised. Practically all software projects depend on heroes. People that make it work, no matter what the methodology is. For new projects, the heroes are skilled at getting things started. For codebases that are in maintenance or evolutionary mode, the heroes are the folks that don’t mind the bad code that they work with.

That brings us to the next myth. If we ask people which category they belong to, but without the exact definition of those categories, then we will get a result something like this. 60% in the Genius and Smart categories. and only 30% or so think that they are average.

But in my experience, the numbers are something like this. Very few geniuses, a handful of smart developers and the bulk of people in the average and weak category. Think about that for a moment.

So, when the Genius Developer shows us his remarkable, simple masterpiece, beautiful design, elegant abstraction, ease of use.... We think “I Can Do That”In Greek it is “Primus Inter Paris”, the First Among Equals, the view that truly outstanding people are still just one of us, no different, we can all do it.

When we see the end result, everything seems obvious. But the road there is really obscure and we ordinary mortals are simply too stupid to realize our limitations. Just because we
understand the end result, how it works, doesn’t mean that we could invent it ourselves. Illusory Superiority complex, and its subclassification of Dunning-Kruger Effect, is essentially;
We are too stupid to realize how stupid we are. We are confident in our abilities, we create complex software that barely works in the normal conditions, and fails miserably at edge cases.

So...Say after me,

I am too stupid to write good code.

Everyone now; Say it...

And that is the Elephant in the Room.

Is that a problem?

Yes, firstly there are financial reasons. More programmers are more expensive. And the more people involved in a codebase, the worse it gets. Banks have armies of programmers, just to keep the programs alive. Changes are slow.

If we look at so called Internet companies... What are all these people doing? Internet efficiencies was to reduce number of people needed

Secondly, the current situation has social impact.Unhappy programmers tend to change job. And I have tried to show that new people will most of the time make the situation worse. Another vicious circle, downward spiral into the big ball of mud. And we should be satisfied with our jobs. We should feel joy when we go to work. Another aspect of low retention is that many programmers will escape to other jobs, such as management, business analysts and even completely unrelated professions, because they are unhappy being programmers. And that leads to less experience, and more hopeless situations.

This presentation has been very negative, maybe even offensive to many people. But are there any solutions?

Yes, I think that there will be, but it is far into the future. Some genius will come up with new paradigm for creating software. I expect it to be radically different from what we are doing now. The equivalent of introduction of the steam engine to the mining industry in the 18th century. Tools that removes our ability to create bad code, maybe artificial intelligence that has a complete different approach to software creation. Who knows?

Until then, I think we are stuck in the bronze age of computing, handcrafting every detail but without generational knowledge transfer, so we are not improving our collective skills.

I would like to leave you with this advice. The KISS principle - Keep It Simple, Stupid. It is something to keep in mind when you write code. Don’t make additional abstractions. Avoid generalizations. Avoid inheritance. Don’t write code that you think that you may need in the future. You are done, when there is no more code to remove.

I would like to leave you with this advice. The KISS principle - Keep It Simple, Stupid. It is something to keep in mind when you write code. Don’t make additional abstractions. Avoid generalizations. Avoid inheritance. Don’t write code that you think that you may need in the future. You are done, when there is no more code to remove.

Even if the code that you are working on is really messy and bad, please don’t make the situation worse. Even if the codebase is horrible, when you make a change, improve it a little bit. If everyone improve a codebase a little bit every time you work on it, eventually it will improve quite a lot. And don’t let your team mates make it worse either.

Niclas Hedhman long-term Apache Software Foundation contributor and CEO at Bali Automation, specializes in Java, OSGi, Internet of Things, C, FORTH, Embedded Java, Java Mobile Edition, event driven, software architecture, redundancy, robustness, system fault tolerance, high performance, S OA , SCA, Jini, RMI, Apache, Open Source, Community building

China Open Source Conference 2019 is almost here!

China Open Source Conference 2019, the most influential conference in Chinese open source community, will be held in Shanghai. The theme of COSCon’19 is " Let's Cross the Boundaries Together!", which also represents our ardent expectation for open source in China.

The conference will last two days. The themes include open source software, open source hardware, community operation and governance, and open source education. We would also like to hear all kinds of success stories and bitter and bitter experiences related to free/open source. We sincerely invite you to participate!

• Date: November 2, 2019- November 3, 2019

• Revenue: East China Normal University (Zhongbei Campus), 3663 Zhongshan North Road, Putuo District, Shanghai

China Open Source Conference is hosted by Kaiyuanshe, a major open source community in China. If you attend the China Open Source Conference 2018, you will never forget Nat Friedman, CEO of GitHub, who gave a keynote speech at the conference. Nat Friedman brought us a fireside conversation, which had attracted a large number of fans with his brilliance.

Nat Friedman will attend COSCon’19 again!

Nat at COSCon'18

Back then Microsoft just announced the acquisition of GitHub. Now, a year later, have the promises of GitHub CEO been fulfilled? What exciting news will Nat bring us? At COSCon'19, these answers will be announced by Nat Friedman.

Who is Nat Friedman?

Nat Friedman, CEO of GitHub, ardently promotes building a global community for developers. Nat is keen on creating products that delight developers, and he has long been a leader in the open source community. As a co-founder, Nat founded Xamarin in 2011 (as CEO after being acquired by Microsoft in 2016) and Ximian in 1999. He is also co-founder and chairman of AI Grant, the GNOME Foundation and YIMBY, California. Nat lives in San Francisco with his wife, daughter and three dogs.

See you and Nat at COSCon'19!

About ZenTao Pro

For ZenTao Pro features, click HERE .

Installation and Upgrade

• For the first-time Installation, refer to http://www.zentao.pm/book/zentaopromanual/133.html
• For upgrade (from Open Source Version), refer to http://www.zentao.pm/book/zentaopromanual/131.html
• For update (from Lower Version), refer to http://www.zentao.pm/book/zentaopromanual/136.html

Git Branch Sync in Repo

Changelog

Story

6370 Add codes to be compatible with Office2016.

6146 Integrate SVN Chinese address.

6123 Update dHtmlx to the latest 6046 and optimize LDAP user import.

6017 Optimize the upgrade workflow.

5978 Database conflicts existing in updating ZenTao with plug-ins installed.

5886 Add tips when restoring deleted users (number of users exceeds the licensed)

5702 Use encrypted password for Repo.

5674 Add a feature to distinguish real ma,es in LDAP realm.

5623 LDAP support memberof.

4333 Add Sync Branch of Git.

Bug

1557 When path=GET, errors appear in File field using MSOffice to open it.

1741 Word export. Extra p> is imported.

1753 Export stories in Word but it is not open in Office2016, Office365, Office 2013 and Office 2007.

1756 Inaccurate data in use case execution report.

1757 Git repo diff issue.

1759 Story exported Word file error.

1760 Ailgn=left in exported Word file.

1769 File diff feature is not functioning.

1782 Log in ZenTao as LDAP user but the login time is not updated.

1789 Export a QA report but it is empty.

1792 H5 page of Report BUg. Linked Project and Affect Build are switched.

1798 Progress of a project in Report is not accurately calculated.

1805 Progress in Gantt Chart is abnormal.

1808 Linked Project is the same one no matter which project you are adding an Effort for.

1816 Gantt Chart->Group by Stories. Only one  story i selected.

1821 Issue in project progress report.

1822 Logic issue in Effort Report.

1823 Build report export issue and statistics error.

1834 Space and enter are not fixed in Word exported file.

1839 H5 page of Child Task edit page. It is separated from the parent after editing.

1840 Exported template in Office 2016. Drop-down is not working.

1851 Format error in story exported MS Word.

1853 My Dashboard. Add a task but the hours are not sync to the task history and cost hours.

1861 Template exported for user case can't open.

1862 Exported Word file can't include images.

1894 Decimals can't be included in effort hours on mobile app.

1911 ZenTao Ent 3.4. Exported template in .xls has no drop-down.

1933 Navigation name error.

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• PHP 5.3-5.6 package: Official Website SourceForge

• PHP 7.0 package: Official Website SourceForge

• PHP 7.1 package:   Official Website SourceForge

• PHP 7.2 package: Official Website SourceForge

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

Change Log

Bug

2722 Multi-user task is in abnormal status after it is finished.
2755 Search is abnormal in Project->Story.
2766 JS code is parsed when use cases are imported.

Download

Source Code Package

Official Website SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• DEB package: Official Website SourceForge

• RPM package: Official Website SourceForge

Help

Installation Manual

Update Manual

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

If you are a front developer, you should know fullPage.js. It is a well known open source JavaScript component which can create full screen pages fast and simple. Alvaro Trigo, the author of fullPage,js, posted a blog on  Indie Hacker, mentioning making a $15K income per month out of fullPage,js. What?! $150,00? A month? You must be as curious as I am that how an open source software author makes that much monthly. After reading his blog, I feel obliged to summarize the key points in this article, so open source community can be encouraged and learn from his experience.

Who coded fullPage.js

Alvaro Trigo. He is a Spanish working in UK. He was a full-stack developer working for a small team and quit his job when the incomes fullPage.js bring to him surpass his salary. He also mentioned,

"Making something is nice and all but it's an entirely new level when you see people actually using what you've created."

This is also ubiquitously true in the open source community that seeing people use your project and you are helping them are much rewarding and encouraging.

Alvaro Trigo currently ranks fifth on the list of top Javascript developers in the UK and 84th worldwide according to git-awards.com, and his fullPage.js is trusted and utilized by Google, SONY, ebay, etc. On GitHub, fullPage. js is starred over 28,000 times.

How fullPage.js is operated

After fullPage.js is release, Alvaro was not just waiting for it to grow. Instead, he started marketing immediately and did the following

• create a demo page
• post blogs and explain the technology of this project
• send emails to major Web community to promote this project
• submit the project to Web resource sites
• answer questions on Stack Overflow and promote this project
• use GitHub Trending
• upload tutorial videos on YouTube
• do interviews with tech media
• buy Google and Facebook ads (not working well)

How fullPage.js is operated for profit

Alvaro Trigo was first trying to make money out of fullPage.js by doing customizations, but it is a waste of time to confirm the requirements of the customization as there were more and more customization requests. Then he packed some of the customization and tried to sell it on his website.

With the features of this project optimized,  the author started to sell licenses of fullPage.js. Below are the main resources he uses to make profit.

• extension sales (on Gumroad)
• license sales
• commissions from WordPress Affiliate (40% from WP)

The revenue has doubled since July 2018 when he switched fullPage.js from open source mode to premium mode (GPLv3 is still free). But still, he regretted not creating a WordPress plug-in from the beginning, as the market on WordPress is huge. Therefore, Alvaro Trigo also suggested 

" Start charging from the very beginning; though this does depend on the product... Earn your place in the market, make yourself a name, and get others to help spread the word about your product. Once you have a good amount of people using your product start charging in some way or another."

Suggestions

No matter the technology, the project itself, or its marketing, fullPage.js has been done in the right way and excellent way. It is also what an independent developer should learn. To be one of them, you should,

• do something you enjoy
• design your project and release it to the market to test it asap ( as in The Lean Startup)
• do not waste too much time on the technology you use and release your product as planned
• you can produce a nice project even you don't know much about the technology
• brand your project if you go independent
• support your users via emails, at least at the beginning of it
• listen to your users
• think over and over your product and set reasonable goals; product first and then others

Conclusion

More and more coders would like to be independent, and they all want to be someone who can code a product that helps people and brings passive incomes, like the author of fullPage.js.

Just like the author of Vue.js said, 'Passive income is what makes you free. Programmers in this era have a natural advantage in creating passive income.(translated)

However, being an independent developer is still relatively challenging. When you can't find a team or partner in the early phase of your product, you have to be multi-tasking, such as the technology, design, product, marketing, etc. None of those can't be ignored. So you have to think whether your learning ability and self-control are strong enough.

If you are not satisfied with your current work situation, it is time t to start planning today and prepare for becoming an independent developer in the future. When the opportunity comes, you will be sure to grab it.

Collabora Office is offered by Collabora Productivity, the most powerful Cloud, Mobile and Desktop Enterprise Office Suite provider. Key features of Collabora Office include view and edit text documents, spreadsheets, presentations, and collaborative editing features. The layout and format of documents are supported in various formats, including

• text documents (odt, docx, doc,…)
• spreadsheets (ods, xlsx, xls, …)
• presentations (odp, pptx, ppt,…)

Document Management in ZenTao

ZenTao Enterprise has integrated Collabora Office and Collabora Online for document online preview and editing. You can also compare the versions and find the differences of documents via Document Management in ZenTao.

For the feature of Document Management in ZenTao, click HERE for more information.

Collabora Office Growth in the Past Year

Collabora Office team are the top code contributors to LibreOffice with 5986 code commits in the past year. Below are some interesting findings of Collabora Office and LibreOffice

Conclusion

Since the release of ZenTao 0.0 Alpha on July 30, 2009, ZenTao team has committed over 11,900 times, completed over 2,700 features, and released over 100 versions. Just like Collabora Office team, ZenTao team has been providing this professional project management tools to open source community, while keeping our team survive in this business.

Being open source is challenging but we will keep doing it as far as we can. Are you with me?

• Optimize the response frequency of misc-ping and message-ajaxgetMessage.
• Add links to the number of tasks, bugs, etc. to direct users to the task/bug list page.
• Add search index to the list page of Release, Story, and Bug.

Change Log

Story

3061  Statistics displayed on the homepage of each view.

3410  Remove bearychat from webhook.

3649 Optimize the response frequency of misc-ping and message-ajaxgetMessage.

4346  Scripts generated by executing init.sh should be the same of that of the Scheduled Task(Cron).

Bug

2713 Close a project, and its last added document library is still in the drop-down.
2712 If a '<' is in a case, the content after it is not displayed.
2711 Use customized template to report a bug. When converting it to a case, the format is wrong.
2710 Abnormal display of product drop-downs in Document Library.
2709 The color of the Create Document button is not the same as the theme color.
2708 Linked Story on the AssignedToMe case list in Test Request is not displayed.
2707 Project->Team. Add a team member and the joined date will be today.
2706 Return on Story , Bug, Case Editing page needs to be optimized.
2705 Abnormal display of documents.
2704 If the search value is 0, search is not done properly.
2703 Confirm Mysql8 issues.
2702 Recurrence creation is erroneous.
2701 Error in email sending test.
2700 Incomplete display of Priority when creating todos.
2699 Click other user's Effort and error prompts.
2698 Separation line is displayed for hidden secondary navbars on Dashboard page.
2697 Statistics on Stories by Plans is displayed abnormally.
2696 Test Request. Cases cannot be linked to by suites.
2695 Dynamics in ZTE 3.5 does not display task names.
2694 Error when clicking Report Bug in ZT Tutorial.
2693 Link stories in Accepted is not be updated.
2687 Manage Product Line is displayed in Project-Sprint mode.
2685 Sync error of Parent-Child tasks.
2650 Phase of a story is not calculated when its Linked Plan is selected.
2608 All label on Project Overview page does not working.
2605 Description on Project Details is not displayed.
2603 Project view can be deleted from Bug page.
2601 Inaccurate information displayed for separate page on Plan page.
2579 Check child tasks and the statistics at the bottom of the list is not accurate.
2527 If a parent-child task is transferred, tasks in Done status will be changed to Doing.
2476 Execution result is not recorded in Test Request if executing the last test case.
2447 The file format of a xmind uploaded via Safari will be changed.
2302 Change the order for cases on Manage Module page is not working.
1838 Tasks of a project is not the same as in story modules.
1529 Change the way to list, so the paging is abnormal.

Screenshots

Click the numbers and you will see the data that is related to the numbers, such as my tasks, My Bugs, etc.

Admin->Notification->Browser.Set Notification in Browser on/off and the polling time.

Download

Source Code Package

Official Website SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• DEB package: Official Website SourceForge

• RPM package: Official Website SourceForge

Help

Installation Manual

Update Manual

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

Sub-Status is added to Workflow in ZenTao. A lot of our users have asked whether they can customize the status of tasks or bugs. With the sub-status feature, ZenTao users can customize the status of a task/bug. The feature will be further optimized in the following versions. Note: This is BETA version. Do NOT use it for production.

About ZenTao Enterprise

For ZenTao Enterprise features, click HERE .

Installation and Upgrade

• For the first-time Installation, refer to H ERE.
• For upgrade (from Open Source Version), refer to HERE.

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website

• Windows 32 bit one-click installation

Official Website

• Windows one-click installation (No security Settings)

Official Website

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website

PHP package

• PHP 5.3-5.6 package: Official Website

• PHP 7.0 package: Official Website

• PHP 7.1 package: Official Website

• PHP 7.2 package: Official Website

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

About ZenTao Pro

For ZenTao Pro features, click HERE .

Installation and Upgrade

• For the first-time Installation, refer to http://www.zentao.pm/book/zentaopromanual/133.html
• For upgrade (from Open Source Version), refer to http://www.zentao.pm/book/zentaopromanual/131.html
• For update (from Lower Version), refer to http://www.zentao.pm/book/zentaopromanual/136.html

Download

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• PHP 5.3-5.6 package: Official Website SourceForge

• PHP 7.0 package: Official Website SourceForge

• PHP 7.1 package: Official Website SourceForge

• PHP 7.2 package: Official Website SourceForge

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

Change Log

Story
4259 Non-Chinese versions should follow the layout of English version.
4239 If session savepath is empty, remind the user when installing ZenTao.
4237 Add the product list to the page after ZenTao installation/update is done.
4195 Add cache time when exporting files using PHP.
4176 Add Y Disk and MeshIoT recommendations.
3713 Add man-hour change log in the history of child tasks.
3707 Optimize the drop-down of Doc Lib when creating a document.
3706 Add Create Document button on the home of Document.
3610 Edit tips for deleted data when editing it.
2866 Set max. height for images displayed on the details page.

Bug
2618 Log in ZenTao as the super admin and reminded as no right to access.
2619 Quit ZenTao tutorial and the jumpto is wrong.
2620 Turn on Weak Password Check but users can change it back to weak passwords.
2623 Inaccurate calculation of paging data on Task list page.
2624 Editor in Feedback displays errors when editing in it.
2638 Error in the time axis of Roadmap.
2643 zbox error on file names.
2644 zbox configuration. https certificate error.
2645 Port number error in the server configuration.
2646 Error in importing case libraries.
2647 Visit upgrade.php and an error prompts.
2649 Unclosed bugs. Same child tasks displayed on different pages.
2655 docker-entrypoint.sh privilege errors.
2658 Error on closing Force Change Password page.
2659 Error in running Mysql8.
2662 No response when clicking Create Story.
2667 Parent-child tasks are incompletely displayed when the number of tasks on the list page is not enough.
2668 Error in identifying steps of a test case.
2670 Incomplete display of linked tasks on Report Bug page.
2675 Security issue of the reflected XSS and random URL jumpto on the login page.
2676 Error in upgrading Pro 8.4 from community 11.6.
2680 Story 6106. Line breaks of the menu on the details page.
2682 Invalid Save button on the page of editing the whitelist for a document.
2683 Loophole in DOM-based XSS.
2688 Change the space on the Profile page.

Download

Source Code Package

Official Website SourceForge

One-Click Installation Package for Windows

• Windows 64 bit one-click installation

Official Website SourceForge

• Windows 32 bit one-click installation

Official Website SourceForge

• Windows one-click installation (No security Settings)

Official Website SourceForge

One-Click Package ( Packages for Linux have to be unzipped to /opt )

• Linux 64 bit one-click installation (Ubuntu17+ and Centos7.4+)

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu17+ and Centos7.4+ )

Official Website SourceForge

• Linux 64 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

• Linux 32 bit one-click installation ( Ubuntu16- and Centos7.3- )

Official Website SourceForge

PHP package

• DEB package: Official Website SourceForge

• RPM package: Official Website SourceForge

Help

Installation Manual

Update Manual

ZenTao has integrated ZenTao Desktop, with which you can communicate with team members, to start a group conversation, to transfer files, to assign tasks, and to manage projects. It would smooth your team collaboration. ZenTao Desktop is powered by Xuanxuan, a free, open source, and secure Instant Messenger by Nature Easy Soft. It is self-hosted and cross-platform with various plug-ins and rich features. Click HERE to know more about ZenTao Desktop.

ZenTao Desktop

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

ZenTao Desktop Server

Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOS

If you have any questions or would like to get a free trial for more than three users, contact Troy@easysoft.ltd for help.

Introduction

The difference between traditional testing and agile testing methodologies

Agile methodology relies on point to point communication and collaboration with teams working in groups. Responding to change is highly considered when compared with extensive  planning.  Extreme programming lays emphasis on changing the plan to accommodate any  changes in assumptions instead of forcefully following the original plan. Customer collaboration is highly considered in comparison with contract negotiation.  Customer involvement is an important part of an agile process.

Software testing process

If any changes are being applied in the program then the software needs to be tested repeatedly until all the defects are identified and fixed in the program, Test activities are reported and controlled on the testing process and the software status is under test. During the test, planning happens primary flaws are carried out by reviewing the needs and design documents. This testing process can eliminate the flaws but cannot enhance the quality of the software.

Agile methodology

Automated acceptance testing minimizes the manual work. The manual testing for whole Software will not work in the agile process. Doing manual testing leads towards the buggy software in agile testing, so it is not possible to test the entire built Software manually.

Agile unified process

Implementation

Test

Deployment

Configuration Management

Project Management

Environment

Conclusion

V-Model, Waterfall, and Agile models are chosen for the development of the software. Each has its own advantages and disadvantages, it depends upon the organization which model to choose.

Background

•  This project is about a long term O2O platform which features will be continuously developed. It contains 13 child systems and more to be added. 
• Componentization architecture is how this platform is designed, which means each component is separated and can be extended independently.
  
• Developers are not sufficient, especially ones who can work independently.

Agile Practice

• Each sprint should have four phases: Story writing->Designing->Coding->Testing.
• Apply ZenTao for all lifecycle management
• Each sprint last two weeks.

Job Roles in the project

1. Product/Project Manager 
2. Technical Manager
3. QA Manager
4. Master Coder (usually the Dev team leader)
5. General Coder
6. Front Engineer

Tips for using ZenTao

• Project in ZenTao is a definition of a periodical work done in the lifetime of a product. A version is defined as a project for this large-scale project, e.g. V2.0 is a project, so V3.0 is another one.
• Define the version names with care and details, so it will be more intuitive and self-explaining for Developers and QAs to understand.E.g., there is a online version named 'XX System V2.0.0', and a version named 'XX System V2.0.1' is in developing state and will be online soon. So Developers and QAs would not have to think about which version they should choose when reporting a bug, because it is obvious just checking the version number.
• Set Email notifications as Asynchronized Sending, so ZenTao can help make a 'work-chasing-worker' team.

Development Workflow

1. Discussion of user stories

Adopt static prototype to discuss user stories with party A as defined in the contract.

Responsible: Product/Project Manager 

Involved: Technical Manager, QA Manager, Master Coder, Front Engineer

Discussion of stories with party A is not recorded in ZenTao. Use Excel for meeting minutes and emails to communicate with party A. When the stories are clearly defined, front engineers use static prototype and documents to confirm stories. 

2. Confirm stories

Confirm stories that will be developed in the next release and prioritize them with party A.

Responsible: Product/Project Manager 

Involved: Technical Manager, QA Manager, Master Coder

After all the stories are confirmed, the project team will have a meeting and keep everyone on the same page. Meanwhile, QA team start to prepare test cases. 

3. Assign tasks

Decompose stories into tasks and assign them.

Responsible:  Technical Manager

In ZenTao, go to Project->Task. When decomposing stories into tasks, a story is decomposed to several development tasks. A task can be assigned to only one coder. For example,

Story: Change the page of XXX to display the information of his city for the operator.

So the three tasks of this story should be,

1) Change the page of XXX to display the information of his city for the operator-Detailed design.

2) Change the page of XXX to display the information of his city for the operator-Back coding.

3) Change the page of XXX to display the information of his city for the operator-Front coding.

Prepare the design document according to stories.

Responsible: Coders that have been assigned with tasks

Supervisor: Technical Manager

Coders prepare the design document for features that are not too challenging and master coders or technical managers prepare the document for challenging features. Then upload both to SVN/Git. If it is a simple algorithm design, just add it as a comment in ZenTao.

Document title format: Design Document_Story ID_Story Title, e.g. Design Document_Story001_ Change the page of XXX to display the information of his city for the operator.

5. Coding and unit testing

Responsible: Coders that have been assigned with tasks

Supervisor: Technical Manager, Master Coder

1) Coders refer to the tasks in ZenTao and start coding and unit testing.

2) Coders log in ZenTao every morning and 'Start' tasks and click 'Finish' when they finish a task. 

Note: 1. Face-to-face communication about assigning tasks is not necessary, but it is always better if you could do it face-to-face. 2. SVN/Git can be integrated in ZenTao, so technical managers could review codes in ZenTao( community version has no such feature).

3) Technical managers review codes each day and solve challenging problems.

4) Product/Project managers monitor the progress of development and deal with problems if any in time. They can update the status of the stories according the finished tasks, so party A could know the progress of the project. The progress of stories can be added in the comment of ZenTao, and the format is,

Development Finished Time: 7PM, 2016-04-18

Testing Finished Time: 7PM,  2016-04-19

Release Time: 2AM,  2016-04-20

Note: Scripts for changing the database should be upload to the directory "Development Document-Version" on SVN/Git, e.g. \01 Development Document\V2.2.0. And the name format is Script_v2.2.0.txt. This script is maintained by the technical manager.

6. Define version/build numbers

Before testing, set version/build numbers for each component.

Responsible: Product/Project Manager 

The version/build number specification is

1) The second digit is +1, so the third digit is 0, e.g. V2.2.0

2) After the release, add 1 to the third digit if any small changes, e.g. V2.2.1, V2.2.2.

Define the version number in Project-Build, and link relevant stories to this build. One story can be linked to several builds, e.g. Story 002: Change the page of Order List to display the information of his city for the operator. This story involves and should be linked to Order Central Component V2.2.0, Product Central Component V2.2.0, and WeMall/PC Mall Component V.2.2.0.

Note: The version/build number for the components should be defined separately, including

1) WeMall/PC Mall Component V2.2.0

2)  Order Central  Component V2.2.0

3)  Product Central Component V2.2.0

4) Shop System  Component V2.2.0

5) Call Center Component  V2.2.0

6) Shop APP  Component  V2.2.0

Go to Project-Build-Bug in ZenTao to check all the bugs that are linked to this build.

7.Integration testing

After the coding is done, submit a test request.

1) Technical managers verify that it is OK to be tested and submit a Test Request in 'Project-Build' of ZenTao.

2) Technical managers deploy the code to testing server.

3) QA managers arrange testing tasks and report bugs. Note: When reporting bugs, set the bugs that has to be fixed in this release as Priority 1 and other bugs as 2 or 3. Also set Mailto project managerial staff, so every manager will know how the progress of the test task.

4) If the testing is going to be finished and the release is getting ready, technical managers could branch for the code that has been submitted for test on SVN (name it as V2.2.0_Testing). Bugs should be fixed by senior coders so to lower the possibility of causing new bugs. Notify those senior coders to switch to this branch, and edit their read/write privilege to Trunk on SVN so to avoid errors caused by read/write privileges. Other coders could code on Trunk meanwhile.  

Note: 1) Select the build when reporting a bug in Request-Bug. 2) Notify everyone of the update on files that is uploaded to the testing server, and attach a list of bugs that needs to be fixed in this build

8. Acceptance testing

After the integration testing is done, review and do the acceptance testing. Note: All works here are for the Branch (V2.2.0_Testing) mentioned in Section 7. When QA managers reviews all the level-1 bugs, and confirm it is ready to release,

1) QA managers report to Product/Project managers that it is ready to release.

2) Product/Project managers should test it again to ensure the quality.

3)  Product/Project managers confirm that it is OK to release, then submit it to party A for acceptance testing( If necessary, party A can involve in the testing mentioned in Section 7 ).

9. Release 

After party A confirm that it is OK to release, release it. Note: All works here are for the Branch (V2.2.0_Testing) mentioned in Section 7. 

On the day that it is release,

1) QA managers go to 'QA-Build' and change the status of the tested build into 'Finished'. 

2) Technical managers package all the code that has to be updates, as well as the SQL scripts.

3)  Product/Project managers export stories which have been linked to this build in Project-Story as an Excel file, and this file is the changelog sent to party A.  

4)  Product/Project managers send the changelog to party A and party A should sign the release confirmation.

5) Technical managers deploy the released files to the production server.

6)  Product/Project managers create a release in Product-Release and add the release time and description. Like the release with the build.

On the following day that it has been released,

1) Technical managers export a Tag from the branch on SVN, and name is as V2.2.0_Release.

2) Technical managers go through tasks in ZenTa, and close all the tasks that have been included in the release. For unfinished tasks, link them to the next build.

3)  Product/Project managers close stories released in this build after technical managers finish step 2.

10. Version maintenance

Usually, there are bugs that were not found before have to be fixed after it is released. Therefore, the current version has to be maintained before the next big version is released. So

1) Technical manager export a Branch from Tag-Release on SVN, e.g. V2.2.0_Fixbug.

2) QA managers get feedback from party A and report bugs in ZenTao. Set priority as 1, and the build version number as V2.2.0.

3) Technical managers fix bugs on the branch of  V2.2.0_Fixbug. Pay attention to the privileges on SVN and assign privileges to the coders who are responsible for this branch.

4) QA managers arrange the regression testing.

5) Repeat step 2, 3, and 4 till it is ready for another release. Confirm the version number, e.g. V2.2.1, and export a Tag named V2.2.1_Release from  V2.2.0_Fixbug. Technical managers update it to the product server. Export the list of bugs that have been fixed and send it to party A to confirm.

Repeat step 2, 3, and 4 till this version is not maintained any more.

11. Stop maintenance

Generally speaking, the last release is not maintained five days earlier before the new one is released.

1) Technical managers inform coders to switch local directories to Trunk, and close their privilege to the Branch of the last build on SVN.

2)  Product/Project managers close the last release in Product-Release and set the release as terminated. Note: Do not forget to terminate a release, as it will be display in the drop-down of linked build when reporting a bug in ZenTao.

Product/Project managers should start to discuss stories for net release with party A after step 2 is finished. Then the technical manager can decompose stories into tasks and assign to coders, and coders start to get familiar with techniques required to finish the tasks. Then QA team start to understand the workflow and details, so the whole new sprint begins. It is also called the spiral Agile iterative development.

Image from Visual Workplace

Scrum Reading

To start with, get really familiar with The Scrum Guide which is the foundation and guideline of Scrum.

Scrumguides, The Scrum Guide

https://www.scrumguides.org/scrum-guide.html

For blogs and articles to get a quick start, you can check Mike Cohn's websites.

Mike Cohn, Introduction to Scrum PPT

https://www.mountaingoatsoftware.com/presentations/an-introduction-to-scrum

Mountain Goat, What is Scrum?

https://www.mountaingoatsoftware.com/agile/scrum

3-Min Introduction to Scrum(Video)

https://www.zentao.pm/basic/3-min-intro-scrum-310.html

Agile and Scrum

https://www.zentao.pm/book/zentaomanual/free-open-source-project-management-software-agileandscrum-31.html

Scrum Master

Below is a quite thorough reading recommended on Scrum.org. You can find almost everything you need.

Scrum.org,  Suggested Reading for Professional Scrum Master™

https://www.scrum.org/resources/suggested-reading-professional-scrum-master

Below are reading about practices and cases of implementing Scrum.

Barry Overeem,  8 Best Practices to Start a Scrum Project

https://www.scrum.org/resources/blog/8-best-practices-start-scrum-project

Pedro Liu, Apply ZenTao in Samwell PSA RCE Project

https://www.zentao.pm/blog/casestudysamwell-120.html

There was a rumor that Huawei started to dismiss engineers who are over 34 years old. It has caused a massive panic among engineers. Since the entry to QA engineering is not as high as to development production, and the skills and requirements of QA engineers are not as much as that of software engineers, QA engineers tend to worry about their career path as they are getting old.  Below are tips from a senior QA engineer and hope it helps you improve yourself continuously.

image from http://www.simonarcher.me/blog/wp/from-qa-to-developer-and-managing-the-different-disciplines-of-each/

1. It is all about you.

This is a common rule for everyone, not just for QA engineers. You either keep learning or you get eliminated. Therefore, you have to be self-driven and determined to learn something that help develop your skills.

2. Keep learning

Knowledge comes with learning and accumulation. You have to acquire must-have QA basics. So you would not panic when you see an issue. You actually have a lot of resources and all have to do is to pay attention and get it when you see it.

3. Think before you ask for help

When you have problems, you should try to fix it yourself. 80% of your problems can be fixed by googling it, especially tools and errors. For QA engineers, troubleshooting is an essential skill, as well as problem analyzing, and problem solving independently.

4. Can I?

Don't question yourself. Whether you can acquire a technique only has something to do with yourself. If you really want to learn it, you can absolutely do it. Always spend more time on it and ask questions if you don't understand it.

5. Challenge yourself

Is it challenging to learn a new skill? Well, it cannot be defined. What I find easy might be difficult to you, while you might have already acquired a skill which I find challenging. Learning something can be tedious. Only one who is persistent could defeat tediousness and eventually acquire the knowledge and skills.

6.  Ask questions

It is quite usual that you might have questions when learning a new stuff. If you ask a question clearly and provide details about it, people will just be happy to answer it. The premise here is that you know how to ask questions. Do not ask questions that you have not thought over it or too simple, or you can find the answer directly from the Internet. It would be a waste of time for the one who has already answered it on his blog.

7. Read more

Learning a new skill starts with reading the introduction books, so you will have an overview of the knowledge structure. Then start to learn the basics and on top of that, acquire in-depth knowledge of it.

8. Career path

Some QA engineers might want to change the career path, such as starting a developer job. Before you do that, do a thorough research on knowledge system of the job, and then ask yourself whether you like it and can excel in this job role. Don't just think about the salary. All high paid job requires advanced skills. So you would better improve yourself and be qualified for this job, rather than just care about the salary.

9. Still confused

After a few years' working in the same role, you might be confused. What is your future? What are your advantages and disadvantages compared to your peers? Leave a message below and we can talk about it.

Reference

1. https://www.quora.com/How-difficult-is-it-for-a-QA-engineer-to-switch-to-a-software-developer-of-the-same-or-another-company

2. https://www.testwo.com/blog/8355

sosconf is the very first student-held, student-centered international conference focusing on open source. It will be a great opportunity for students around the world to gather, connect and learn from each other. For companies and organizations, it will be a chance to show their commitment to open source and to search for student talents.

If you would like to know more about it, visit  https://2019.sosconf.org

Hi Guys,

The leak is caused by the misconfiguration of user privileges, and such in Jira. It also has something to do with Anonymous Login the Anyone user group. Although Anonymous Login is also supported in ZenTao , it is strictly managed by ZenTao Administrators.You can find the comparison of permissions between JIRA and ZenTao HERE.

Limited Users and Limited Actions

ZenTao standalone privileges are the privileges of actions and users that are set separately in ZenTao.  Limited User is a privilege group that is used to manage newcomers who might make mistakes and cause problems to the team because they are not familiar with how it works in the ZenTao. For limited users in ZenTao, they can only edit the content that is relevant to themselves, such as Tasks, Stories, and Bugs, and they cannot add them. They can edit the content that is about AssignedTo, Done, Closed, Cancelled, or Last Edited.

Limited User is also added in Project->Team->Manage Team to limit a user in a project. If a use is the Limited User in a project, s/he can only edit tasks, stories and bugs that are related to him/her in the project.

Note

If you still have questions about how to set privileges in ZenTao, check Groups and Privileges in ZenTao Manual or

• Privilege in ZenTao 1: View Privileges
• Privilege in ZenTao 2: Standalone Privileges

Reference

1. https://www.zentao.pm/share/jira-permissions-flexible-scrum-tool-284.html

2. https://medium.com/@logicbomb_1/one-misconfig-jira-to-leak-them-all-including-nasa-and-hundreds-of-fortune-500-companies-a70957ef03c7

3. https://www.zentao.pm/book/zentaomanual/free-open-source-project-management-software-groupsandprivileges-25.html