Summary : Hello, everyone! ZenTao 16.0. beta1 is released！ With a newly added waterfall model, optimized Kanban function, improved branch management and details, and some bugs are fixed.

ZenTao 16.0.beta1 is released

Hello everyone, the first beta version of the ZenTao 16 series is released! The 16 series has a new upgrade to the project management model. A new waterfall management model has been added to this release. Users can choose the management model according to actual needs, which enhances project management flexibility. At the same time, the Kanban function is optimized. The users can manage requirements, tasks, bugs, and set limits on the number of products through the Kanban function, which greatly enhances the visibility of the project management process.

The improved function of ZenTao 16.0. beta1 mainly includes:

Integrate the waterfall project model into the Pro version, adding a new tool and new method to project management.
The Kanban function is optimized which makes it available to update and monitor the requirements, tasks, and bugs in time. The management method is more transparent and efficient.
Add the record of actual start time and actual completion time to the project and execution, making sure the project's complete cycle and execution are more accurate.
Add the state of linkage to start state of execution, project, and item set to reduce unnecessary manual operations.
Support dynamically for switching sorting in positive order/reverse order.
Add the status management to product branches and enhance the flexibility of branch management.
Add shortcuts to the documents to reduce users’ operation paths and improve the efficiency of document maintenance.
Solved the bugs of DevOps related.

Welcome to update and download.

Modified Records

Completed requirements

14005 Able to browse user’s needs according to platform branches
14429 Parent requirement supports to be changed
14761 After selecting a branch, click on other menus, expecting to keep the branch drop-down menu status
14771 After enabling the multi-branch function, the control of the display of branch words has been added
14772 A prompt will be given if there is a conflict when the branch needs to be modified
14778 Branch function is the default in the branch setting
14877 Prompt the name of the last version plan according to the branch
15134 Added remarks to the employee load table
15470 Kanban can set the arrangement of cards in a cell
15478 Added confirmation field to the bug list of my site
25665 Sort out the logic of projects and execute related product branches
25666 A branch can be closed
25667 Change all branch concepts to trunk and process historical data
25670 Separate everything from the trunk when browsing requirements for multi-branch products
25673 Add sorting function to branch
27484 Add a floating operation menu for files in the right directory of the document library
27485 Add a floating operation menu for the directory on the right side of the document library
27486 In the WIKI directory, when hovering the mouse to the name of the article, the article shortcut will be displayed
In the 27487 WIKI directory, when hovering the mouse to a specific chapter, the shortcut operation of the chapter is displayed
27927 The Kanban only displays one screen by default and continues to load when scrolling
28098 When you need to convert tasks in batches, a prompt for the needs of tasks that have been converted will come out
28131 The parent task is displayed before the subtask name in the pending task list
28138 Add project name information to the employee load table
28147 The list with the horizontal scroll bar in the statistics list can be displayed directly
28153 Optimize the execution query conditions in the bug’s creation table
28235 Add a record of the actual completion date when closing the project
28236 Add information about actual start and actual completion in project working hours statistics
28237 Add a record of the actual start date when executing the start
28238 Add the record of the actual completion date when closing the execution
28239 Add actual start and actual completion information to the execution time statistics
28310 The program state is automatically set to start when there is a project started in the un-started program
28466 Add the search condition by the project to the test bug list
28509 Add the display of project code in the project overview
28510 Add project code field display in the project list
28719 Summary of the number displayed in the Kanban column of the project Kanban
28727 When planning to create an iteration, select the project and click Next to automatically close the selection pop-up window
28809 Execute the adjustment of the sorting rules of the items in progress in the Kanban board
28810 The closed execution in the Kanban board only displays the latest 2 periods of data
28811 Execution in Kanban supports drag adjustment of Kanban columns and status
28812 Adjust the program and item sorting rules in the project Kanban
28813 The closed project in Kanban only displays the latest 2 data
28814 Projects in the project Kanban support to drag and adjustment of Kanban columns and status
28814 Projects in the project Kanban support to drag adjustment of Kanban columns and status
28815 Summary of the number displayed in the Kanban column of the product Kanban
28816 Adjust the sorting rules of item sets and products in the product Kanban
28817 Adjust the sorting rules of item sets and products in the item set Kanban
28818 The summary of the number displayed in the Kanban column of the program Kanban
28819 Adjust program/product/project/implement the same-name rule
28833 Create an execution page to directly maintain relevant person-in-charge information
28834 Remove useless modules and methods from the group permissions of the project
28835 Items associated with multiple products can also be merged
28904 Optimize the filter results of "I participated" in the project list
28928 Can set who does not need to be reminded
28929 When editing the bug modification status, if the modification is not successful, expected that there will be an error message
28931 Adjust branch management function
28932 Realize the batch operation of branches
28941 The product drop-down menu should keep the last selected product name after logging in to the system again
28944 Add the related functions of the waterfall model in the open-source version
28959 When the old version is upgraded and the new version data is merged, the project and execution name can be modified.
28960 Adjust the width display ratio of the product list page
28965 Realize the new/edit operation of the branch
28970 The demand list is selected in batches and expected to be operated by the Shift shortcut key
28972 The module setting on the left side of the product list is adjusted to the display setting
28973 When submitting a bug, the branch and the affected version must be linked together
28974 Display the branch information before the plan name when the product list is adjusted in batches
28993 Adjust the query logic of the requirements when creating or editing use cases
29000 Adjust the display width of the field in the product list
29002 Dynamically supports switching sorting in positive order/reverse order
29030 The suspended project/execute the following tasks are not shown in to-do/to-be-processed tasks
29059 Set the branch field as the default item when creating requirements in batches for multi-branch products
29069 Add priority sorting function in the organized team member task list
29074 Add the staff profile picture/department/position information to the user drop-down menu
29078 Realize that you can select the requirements, tasks, and bug functions related to this request when creating a merge request 29079 Implement the merge request details page to display the requirements, tasks, and bugs associated with the request
29079 Implementation of the merge request details page to display the requirements, tasks, and bugs associated with the request
29081 Implement the function of displaying code comparison information on the merge request review page
29082 Realize the log record function of merge request related requirements, tasks, and bugs
29083 Achieve the combined display of the source project column and the source branch column in the merge request list
29084 A build task can be selected when creating a merge request
29085 Implement the notification function after the completion of the construction task associated with the merge request
29086 Any user in the system can be assigned when creating a merge request
29087 When creating a Jenkins build, you need to select a branch to add the build if the repository is not SVN
29088 The code base control needs to be reloaded when the build engine is switched
29108 Add the provider of feedback and notify email information to the submit/edit software requirements page
29109 Add the provider of feedback and notify email information to the submit/edit bug page
29116 Add the provider of feedback to the notifiers who create/edit the released information
29127 Added batch editing and plan adjustment functions to the list of planned bugs
29131 Added the setting of reviewers in the product overview
29132 Achieve the combined display of the target project column and the target branch column in the merge request list
29133 Implement the logging function after the merge request is merged
29134 The refresh of the Kanban page should not be jittery and presented in a smoother way
29141 After enabling the multi-branch function, use cases to increase the control of the display of branch words
29142 After enabling the multi-branch function, the bug should increase the control of the display of the branch words
29143 When creating requirements/Bugs/use cases in batches, the subordinate module selection is the same as above. It is necessary to check whether the subordinate branch of the previous row of data is consistent with the subordinate branch of the current row
29144 Batch edit requirements/Bugs/use cases under all branches, and when the module data belongs to the module of all branches by default, you need to deal with the problem of inconsistency between the branch and the module
29145 Adjust the display mode of the overview page when the project and execution are associated with multiple branches of the product and the plan
29147 The software requirement list under the product displays the branch name of the trunk before the requirement name
29156 After the multi-branch function is enabled, the project requirements list increases whether to display the branch name
29157 After enabling the multi-branch function, the list of execution requirements is increased, whether to display the branch name
29158 After the multi-branch function is enabled, the task list to be executed increases whether to display the branch name
29161 Realize the sorting function of the GitLab project list page
29162 Implement the paging function of the GitLab project list page
29163 Realize the search function of the GitLab project list page
29166 When the demand is adjusted branch, the module that the demand belongs to is the backbone, and the module does not need to be cleared.
29167 When the bug adjusts the branch, the module that belongs to the trunk does not need to be cleared.
29168 When the use case adjusts the branch, the module that belongs to the trunk does not need to be cleared.
29173 It is not allowed to associate the parenting plan when the project is associated with the product plan
29174 It is not allowed to associate the parenting plan when executing the associated product plan
29182 The closed branch status is displayed in the branch drop-down menu
29189 Modify the Title of the "Add GitLab Server" page to GitLab-Add GitLab Server-ZenTao
29190 Change the project list and group list icons on the GitLab list page
29191 Delete the "Theme" control in the "Edit GitLab Project" page
29192 When merged data encounter the same-named data, the same-named data can be modified
29193 Adjust the triggering method of the message notification in the release
29194 On the GitLab "Add Group" page, change the control name
29195 GitLab group URL cannot be modified after creation
29196 The "Account" control data on the GitLab "Group Member Management" page only displays users who have been bound to ZenTao
29197 Adjust the layout of controls on the "Add GitLab User" page
29198 The "User Name" information in the "Edit GitLab User" page cannot be changed
29199 GitLab "User List" page information display is adjusted
29200 Implement the sorting function of the GitLab "User List" page
29201 Fix the UI display problem of the virtualization list
29202 Fix the UI display problem of the management account on the add host page
29204 Realize the page sorting function of host details
29205 Create a virtual machine to display in the form of a pop-up window
29206 Virtual machine list needs to display host information
29218 The product type can be adjusted to normal only when the status of the branches is all closed
29234 Sort out the logic of the branch

29438 Create test cases under execution 1 can also be seen in the list of execution 2 cases

Fixed Bug

6917 The number will be changed when the user cases turn to bugs
6978 The multiple branch product bug search affects the version is not clear
11290 The content of the subject field in the mailing list is partially obscured
12023 Suggested optimization of product branch page
13756 The bug page does not display the control of the product branch normally
14101 Youth Blue-International version of the guide page with pictures in Chinese
15665 The maintenance catalog is the same as the icon before version management
15675 Bugs that were resolved and activated under version, they should have the previous version information when re-solved
15686 After the project is created and filled with data, the selected project set data is cleared
15687 Custom task priority display problem
15688 Corresponding error of new build case, module, and requirement
15689 The reported percentage of the test order wraps
15690 After switching products, the new use case does not appear in the use case list
15691 The style of the operation button in the upper right corner of the suit's use case list is inconsistent
15693 When the card displays the project, the project status is not displayed correctly
15694 Create a use case under execution, you can select all the modules and requirements of the product
15695 Build use case, there are default belonging modules to choose all requirements
15737 Statistics view cannot be canceled through permission control
15780 When changing the parent item set of an item set, the product line below cannot be changed to the top item set
15781 Cannot select the product branch when creating a version of the project
15798 The pie chart is not displayed after the report is exported
15826 After the background review process is started, the R&D requirements created in batches in the product do not need to be reviewed by default
15828 When deleting the top item from the item setlist, error jumps out
16000 The title of the test case is displayed in a new line under the execution of the test case
16018 Project-Test-Bug interfaces do not show multiple branches/platforms when submitting bugs
16130 The data listed in the related requirements when creating test cases under the project is incorrect
16139 Set the branch as the default branch icon is not displayed completely
16257 Projects that have been closed during creation and execution can still be selected
16302 The branch belonging to the search drop-down column under the project software requirements is displayed as %s
16527 When editing use cases in batches, all branches are listed
16567 The name of the main branch before the task name of the multi-branch product is displayed, and the names of other branches are not displayed
16570 The title is not filled in when the bug is raised in batches for multi-branch products in classic mode, and click save without prompting
16573 Classic mode multi-branch product batch creation of use cases does not fill in the use case title save directly jump list without prompting
16574 Linked products on the related product page can drop down to select other unlinked branches
16582 Branch 1 version can be associated with other branch requirements
16583 Batch edit test case branch display error results in failure to select modules
16584 The execution version cannot be searched according to the branch it belongs to
16585 The trunk ID is not displayed before the trunk version
16587 Suggested optimizations of the branch display method at the stage of the demand edit page
16588 Project/Execution shows unrelated branch requirements
16589 Multi-branch product test case list The use case type display is obstructed
16591 Batch edit R&D requirements after modifying the branch and then modify it back, the plan does not follow the linkage
16592 The display of the R&D requirement module of the multi-branch product project is incorrect
16593 The module tree on the left side of the Bug page under the test highlights the backbone by default
16603 The project name in the project list is not displayed completely
16605 All branches are shown under the use case of the project
16608 After selecting a branch on the edit module page, the upper-level module is still listed as the main module
16609 The template of the exported use case shows all branches
16612 The use case template does not show the modules under the branch
16616 The drop-down list of imported use case branches shows all branches
16620 R&D requirements change list is displayed multiple times for one use case
16621 When searching for use cases, all branches are listed
16622 The module drop-down searched on the R&D requirements page under the product only lists the modules under the backbone
16623 The closed branch of a multi-branch product is still displayed when the project is associated with the product
16624 There is no current product option in the product drop-down menu in the upper left corner of the product details page
16626 No other branch modules are displayed in the test suite, only the main module is displayed
16631 The trunk is not displayed before the use case name of the suite
16637 The test list is associated with the use case list, and the use case list displays the branch ID
16639 The test case details page is assigned to the user to display the number
16640 The priority of the test order is displayed as 0
16641 The relevant R&D requirements of the use case batch editing page under the site to be processed are not brought out
16643 The position of the "Contribution" menu on the batch editing task page under the site is displayed incorrectly
16645 No link address when creating dynamic Gitlab
16646 The product in the product library of the document is displayed incorrectly
16647 The test order generation report prompts that there is no associated non-Trunk test order
16648 The project name in the project list is completely collapsed and hidden
16650 The multi-branch product test suite details the module that belongs to only the trunk module
16653 released the requirements that can be associated with all branches
16676 There is a code error in the batch execution use case page under the site to be processed
16680 When the product library creates a document, it is not possible to select other product libraries from the drop-down list of the document library to which it belongs
16681 The test case branch of the imported case library and the module do not correspond
16682 There is a code error on the copy use case page under the site contribution
16683 The use case cannot choose the trunk when the test order is associated with the test
16684 The trunk branch of the use case title in the suite is not displayed
16685 Test list related test case branch = empty searched data for the main test case
16689 The related modules of the test case can’t display in the test case list
16690 The plan of the demand batch editing page under the product is displayed incorrectly
16692 The branch of the software requirement batch editing page under the project is displayed incorrectly
16694 The test sheet submitted for testing should not be affected by the branch selection in the upper left corner
16697 The branch to which the test order is associated with the test case selection should only be the branch associated with the version
16700 The product branch will disappear after the project is created and released the selected version
16708 When editing the R&D requirements in batches for multi-branch products, it reports an error
16713 The trunk module in the product requirement module is directly displayed without increasing the level

Download

Source Code Package	Official Website
One-Click Installation Package for Windows	64 bit 32 bit
One-Click Installation Packages for Linux (unzip to /opt )	64 bit (Ubuntu17+ and Centos7.4+) 32 bit (Ubuntu17+ and Centos7.4+) 64 bit (Ubuntu16- and Centos7.3-) 32 bit (Ubuntu16- and Centos7.3-)
PHP Package	DEB package RPM package
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