The only way to do this as you describe it would be developing some custom code, which is complex. The sensible solution would be to make sure your Epic workflow reflects your stories' workflows and still make the measurement based on Epic workflow.
I suggest you configure your Story workflows to make the linked Epic issue transition from, let's say, Open to InProgress when the story has started. You can do something similar when the last story is resolved and transition the Epic, let's say, from InProgress to Resolved. This way your Epics' InProgress times will show the cycle time for those Epics.
You can probably do this automation with apps like Jira Workflow Toolbox, Automation for Jira or Script Runner. There are probably others but these are the ones at the top of my mind. The exact steps to configure the Story workflow is actually too complex for me to explain here but you can find other questions&answers in the community about "transitioning linked issues".
At that point you will be ready to use your Epic workflow times as Cycle Time. For that, our team at OBSS created Time in Status app.
Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. If you have longer workflows, you can also combine statuses into consolidated columns to see metrics like Issue Age, Cycle Time or Lead Time.
You can get the app to calculate averages and sums of those durations grouped by issue fields you select. (For example see the average Issue Age per project and per issuetype.)
All data can be exported as XLS, XLSX, CSV. The app introduces a REST API for accessing the calculated report output. All the report data can also be visualized by various chart types.
Hi @srinath_17 ,
Enhancer Plugin for Jira allows you to measure time spent between date fields/statuses/events. For your use case, you can populate a date-time custom field when the linked issue starts and then use this date to configure the Enhancer custom field: Time between custom field.
You can then track the cycle time like this:
Please note that I'm one of the folks behind Enhancer plugin for Jira, there might be other solutions out there and I might not be impartial.
Let me know if you have any questions.
Go “behind the screen” to meet some of the Confluence Cloud team. In this video series, we tackle some of the hard-hitting questions you never knew you wanted the answer to! Meet some of the ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events