Best practices of Workflow in ZenTao vs Jira

2022-08-04 14:24:46
Last edited by Yujia Li on 2022-11-08 17:20:53
Share links

1. Definition of workflow

A workflow is a computer model of a work process, that is, the logic and rules for how the work in a workflow is organized together. It requires that we represent the work in a computer with an appropriate model and perform calculations on it. The main problem to be solved by workflow is that in order to achieve a certain business goal, we need to use computers to automatically transfer between multiple participants, according to some predefined rules.

2. The workflow in Jira

In Jira, workflow is used to track the lifecycle of an Issue. Workflow is a record of statuses and transitions of an issue during its lifecycle. When we say about the Jira worflow is the combination of five main stages for any issue we have created: Open Issue, Resolved Issue, InProgress Issue, ReOpened Issue and Close Issue. Each Jira workflow is composed of a set of statuses and transitions that your issue moves through during its lifecycle, and typically represents work processes within your organization.

The following diagram shows a standard workflow in Jira:

Image source: Standard workflow in Jira


3. The workflow in ZenTao

ZenTao can be highly customized with the workflow module. As for now, Workflow has 15 built-in processes based on the usage process of ZenTao, the functional modules, and the customization needs, including product view, product plan, release, requirement/story, program, project, execution, build, task, bug, case, test request, suite, case library, and feedback.


Data-source records the database corresponding to the process. Data-source can be used for fields (generate data in the drop-down list), at the same time, it can be used for calling system functions, custom SQL, option lists, and system languages.


ZenTao workflow has the following features:

  • Add fields to the original process of ZenTao;
  • The added fields support import and export;
  • The added fields can be available on the Create, Edit, More, and Lists pages;
  • Add a button to the original process of ZenTao, click the button to modify other fields;
  • ZenTao supports customized processes, which allow for the interface design, action extensions, field links, CSS and JS extensions;
  • ZenTao customized process support flowcharts display;
  • Built-in data sources can be used;
  • Field support validation rules (IP, phone, number, date...).


4. Comparison between ZenTao and Jira

Jira's work is based on issue as the core object, providing a simple workflow definition function and the defined concept is very similar to Issue.

Jira does not have a fixed workflow, the design is simple and can be customized by the users. It is completely up to the user whether to develop the workflow or not.

ZenTao workflow can achieve the effect of handwritten code and concepts can be added to meet customers' individual needs:

  • Each concept can have its state and flow;
  • Each action can customize the interface, trigger conditions, and data modification mechanism;
  • You can customize various search labels, search conditions, import and export, batch operations, and other functions;
  • You can also enhance, redefine, and cover the ZenTao handwriting process.

ZenTao's workflow is mainly on the developers' side, so it is necessary to explain this clearly to users in advance. ZenTao's internal workflow is changeless and cannot be deleted. The built-in process does not support tagging, sub-processing, and detail table functions at this time. But based on the built-in processes of ZenTao, users can extend the workflow of requirements, bugs, use cases and tasks, etc. The external workflow can be set up by the user.


5. How to standardize workflow processes in ZenTao?

ZenTao's Built-in Flow Extensions:

  • The process of second development by changing the code: Database Design - Page Design - Code Development - Test and Release;
  • The process of adding fields by workflow: Adding Fields - Interface Demo;
  • The process of adding review function to built-in flow: Field Design - Interface Demo - Action Design.
Write a Comment
Comment will be posted after it is reviewed.