Capture Ticket Compliance to Lifecycle Milestones

[David Prince]

How can I create tracking in JIRA Tickets to capture adherence to our milestones for a sprint lifecycle? Is there an app or custom field solution that I can implement for this? 

Example: If we are working on a two week sprint, I expect that when a ticket is created and assigned to a sprint I can automatically capture four due dates based on the sprint delivery date and rules below:

• Due date 1: date the ticket MUST move from status "Planning" to status "Ready" no later than 15 days before the sprint delivery date. Can be earlier than this date, but not later.
• Due date 2: date the ticket MUST move from status "Ready" to status "On Stage" no later than 7 days before the sprint delivery date. Can be earlier than this date, but not later.

• Due date 3: date the ticket MUST move from status "On Stage" to status "Live" no later than 0 days before the sprint delivery date. Must be on this due date. 

My goal is to track how well each team is adhering to these milestones in our process. Im not looking to track how long each ticket is IN the status, but instead track if the ticket moved from status A to status B on or before the assigned due date (which is calculated on sprint date). 

Does anyone have a recommendation for providing this type of transparency in our ticket management?

[Trudy Claspill]

Hello @David Prince 

Welcome to the Atlassian community.

I don't know if there is an app for that, but you could implement a solution leveraging custom fields, automation rules, and workflow customization.

If you want to be able to track adherence to the milestones you would need 6 custom fields; one for each target date and one for each actual date. The target date fields could be set by automation rules. The actual date fields could potentially be set by workflow transitions.

The next question that would have to be answered is how you want to try to report on the information. 

Jira doesn't natively support comparing one field directly to another in JQL, so you would not be able to create a filter to find issues where the actual date was later than the target date.

You could potentially use automation rules to compare the target and actual dates, and set some other custom fields (to be used in filters) to indicate adherence or lack thereof.

There are a few other questions to consider:

1. You said you want the target dates set when an issue is assigned to a sprint. However, if the sprint is not yet started it may not have an end date specified.
2. Additionally, what if the target end date of the sprint changes? Should the target dates in the issues be updated?
3. And what if the actual date of completion for the sprint is different than the target date for completing the sprint?
4. What if an issue is removed from a sprint?
5. What if an issue rolls over to another sprint?
6. What if the issue moves forward and backward through the workflow so that it is transitioned to the specified statuses multiple times?