- 1. A Brief Overview of ZenTao
2. Best Practices Comparison: ZenTao VS Jira
- 2.1 Best practices of Project in ZenTao vs Jira
- 2.2 Best practices of Workflow in ZenTao vs Jira
- 2.3 Best practices of Stories in ZenTao vs Jira
- 2.4 Best practices of Roadmap in ZenTao vs Jira
- 2.5 Best practices of Users and Roles in ZenTao vs Jira
- 2.6 Best practices of Reports in ZenTao vs Jira
- 2.7 Best practices of Dashboards in ZenTao vs Jira
- 2.8 Best practices of Search in ZenTao vs Jira
- 2.9 Best Practices of Agile in ZenTao
- 2.10 Best Practices of Waterfall in ZenTao
- 2.11 Best Practices of Automation in ZenTao vs Jira
- 2.12 Best Practices of Requirements & Test case management in ZenTao vs Jira
- 3. Use cases Comparison: ZenTao VS Jira
- 4. Get started with ZenTao
- 5. Import Jira Data to ZenTao Tutorial
- 6. Reference: Glossary of items in ZenTao VS Jira
1. Common automation use cases
Automation empowers you to focus on the work that matters, removing the need to perform manual, repetitive tasks by allowing your teams to automate their processes and workflows. Rules allow you to automate actions within your system based on criteria that you set. Automation rules are made up of three parts: triggers that kick off the rule, conditions that refine the rule, and actions that perform tasks in your site.
Jira's built-in operational processes and content modules are relatively simple, so they rely on custom workflow to make up for this shortcoming. But it also means that users need to spend more time learning, operating and writing processes.
ZenTao has built-in perfect operation process based on scrum, kanban, and wanterfall which can basically meet the requirement of customer project management. Of course, ZenTao also has its own custom workflow.
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.
The built-in process does not support tagging, sub-processing, and detail table functions at this time. Built-in processes cannot be deleted.
2. DevOps automation tutorials in Jira and ZenTao
DevOps is a set of practices that works to automate and integrate the processes between software development and IT teams, so they can build, test, and release software faster and more reliably. For teams practicing DevOps is the backbone of Atlassian’s open, integrated toolchain known as Open DevOps. Jira Software integrates with first- and third-party tools throughout the DevOps lifecycle, including code and version control tools like Bitbucket, GitHub, and Gitlab, documentation and knowledge management tools like Confluence, and monitoring and operating tools like Opsgenie. Jira Software also integrates with tools across a variety of categories to help DevOps teams ship better software, faster.
Image Sources: What Is DevOps?
Jira relies on a series of product features to implement devops. Means you need to spend more cost to implement.
The support for DevOps of ZenTao, including Git, GitLab, Subversion system integration, Jenkins build task triggering and ZTF automation test scheduling.