Is there a tool / plugin for jira that measures Cycle time (InProgress-Release date)

[Igor Stanisic]

Is there a tool / plugin for jira that measures time between:

1. Status changed to InProgress
2. Release date/time (meaning that ticket must be added to Jira release and have defined released date)

Note:

• I am not searching for the tool that measures duration in specific status (or cumulative duration for statuses between InProgress till Done). There are many tools measuring this.
• I need this tool to measure Cycle time, which means time from the moment work on the ticket is started (InProgress status) till the moment implementation is available to end user on production environment (Release date should reflect this information)
• As an example, below are listed parameters we can find in jira and what information is needed
  • Jira ticket changed the status to InProgress on 1st June 2023, 12:00
  • Jira ticket changed status multiple times and is set to Done status on the 5th June 2023, 12:00 (implemented & tested but not yet released to production environment and available to user)
  • Jira ticket is added to Release June delivery 3.1.0 and delivery date is 10th June 2023
  • Calculate Cycle time from the moment Jira ticket is started till it is released to production environment (InProgress-ReleaseDate)

[Craig Nodwell]

Hi @Igor Stanisic welcome to the community.
I'm not aware of any one plugin that will satisfy this.
How integrated are your delivery tools with Jira?  Re: version control system, build system, deployment system.

Example: with my current client, with a bit of effort(not a lot) all tools are fully integrated and scriptrunner is an available plugin.  All app/servers are self hosted.  Jira GitHub and Jenkins are all integrated.  Jenkins reads the git changelog, and reports back to Jira when builds are completed (and the branch it completed on), Jenkins also reports back to Jira when deployments are completed (and the environment it completed on).  These details can all be queried on via jql.  Bringing all this data together and performing calculations is where scriptrunner comes in.

[Mehmet A _Bloompeak_]

Hi @Igor Stanisic

For cycle time, you can try Status Time Reports app developed by our team.

Here is the online demo link, you can see it in action and try without installing the app.

For your case, you can have a look at Cycle Time by Assignee report, Cycle Time by Components report, Cycle Time by Project report, Cycle Time for Each Issue report, Cycle Time by Issue Creation Month report as examples.

For more detail, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

If you are looking for a completely free solution, you can try the limited version Status Time Free.

Hope it helps.

[Markus Fredén]

Hi Igor,

I would suggest rethinking the workflow used in these projects. For example, is the ticket really "Done" when it haasnt been implemented in production? Consider adding a status representing whether it has been released or not and using the many existing tools measuring this.

Otherwise I would look at Roadmaps for jira.

If you're using Scriptrunner you could create a scripted field that will calculate this using statuses or version releases e.t.c. However this can be performance heave so make sure to test it out properly first.

Best regards,

Markus

[Igor Stanisic]

Hi Markus, thank you for suggestion. It sounds as a good direction.

I was thinking to setup a jira flow in following manner:

1. ToDo
2. InProgress
3. Review
4. Testing
5. Done
6. Acceptance
7. Resolved

In my current Jira there is a status Closed and for now it represents everything that is moved to Done column.

How should I apply Resolved status so that it represents Released to Production:

1. add Resolved status that can be assigned to Ticket after it is Closed - Does Status Closed must be the last status in Jira flow
2. make the new status called Done and connect it with status Resolved and connect both of those statuses to Closed