Have you faced with the problem of monitoring the actual Jira time in status data? We guess, yes. It’s challenging to track time in each Jira status or in all statuses in general. Jira is a great tool that aids teams in planning, managing, and reporting on their work. Jira is one of our favorite project management tools, especially because it allows us to track and monitor issue progress in Jira workflows. But how can you track the task’s progress if the team forgets to move tasks to the correct statuses?
Workers do not move tasks to the relevant columns. That’s why managers frequently face the problem of Jira status mismatching in tasks. Managers lose current data regarding the workflow process as a result. As a result, some of the manager’s decisions are ineffective.
At this point, a manager may either begin the uphill struggle of forcing people to make the proper transitions or start using Automation rules to guarantee that the problem status reflects the current situation accurately. If everything goes smoothly, managers get the correct Jira time in status data.
I’ll write about the second option in this article. We’ll look at the solution that perfectly suits development teams working in IT, releases, and upgrades. Only 4 short paragraphs and you’ll forget about these problems.
1. Set up of the store
If your team use BitBucket, there will be no problems because Jira and BitBucket are both Atlassian products and can simply be integrated. Such popular repositories as GitHub and GitLab would require the installation of a separate Add-on. In most circumstances, it’s free. Make sure that your Jira is linked to the Repository successfully.
You’ll notice the “Create branch” button on the right side of a bar of the Issue layout when it’s finished.
2. Set up the Jira project
Then, you should configure the Automation rules to match your Jira workflows.
Go to the Project setting -> Apps -> Project Automation -> Create rule
3. Beginning point to measure Jira time in status data
Let’s begin by configuring the rule that assists in moving the issue to the In progress status in Jira after the Developer has created the Branch in the repository.
So, we’re just doing a logical action here: If (branch created) – THEN (change the Jira status).
4. Adjust settings according to your workflow
You should automate Jira’s workflow.
Look at the following straightforward process:
Situation
Example of Automation
A. The developer has created the Pull request and wants to review the Code.
B. Reviewing of the code is successful, so QA team can test it.
C. Certain issues have been identified during the Code reviewing. So the developer has to put in more work to make it look attractive.
D. QA team validated the modifications, and the build was marked as Green, so the feature candidate would be deployed.
Make sure you have connected the Building tool. Or ignore it, if only QA decides if it’s ready to be marked as Done.
F. Because the tested functionality failed during the Test and Deployment, Developers must go through it again and make sure it works as planned.
Ignore it if only QA should decide whether it can be marked as Done.
You may also divide these stages into two categories: QA review and Deployment health check.
Try other additional conditions in Automation Rule Library.
Which advantages will you get with the actual list of Jira time in status data?
You may completely use extra Jira options in addition to monitoring the Jira statuses of each issue. For example:
- Keep track of actual data on built-in Jira time in status reports (Control Chart, Cumulative flow diagram, etc.);
- Create automation rules that are based on statuses;
- Create SLA conditions based on statuses (for Jira Service Management tickets, Jira Core and Software issues);
- Track how much time it takes to solve a task on each step.
To perform the last one, our SaaSJet team has created the Time in Status for Jira Cloud add-on. It provides automatic data generation about the Jira time spent in status and status groups. You may use a Gadget on your Jira Dashboard to display this data, and you’ll have access to up-to-date information on the time spent on tasks at various levels. Also, you can use Pivots to get more configurable reports according to your needs.
The overview that has been presented is fairly straightforward. However, we feel it will help you become more familiar with Jira Automation and demonstrate the power of real-time issue status data. Please let us know if this article has assisted you in getting actual status data for your team’s process! How do you monitor Jira time in status data? How do you manage statuses in Jira? Share your experience with us, so we can help other community members and Jira users to learn more about the Jira automation or apps.
Find out more about the Time in Status for Jira Cloud
Visit the app page for more information