Hi,
I've been asked to provide some metrics on the time it takes for a feature to move from 'done' on a scrum project to be implemented ( 'done' on the release team project ).
As I've implied, the scrums have their own JIRA projects and the release team have theirs. Currently there is no link between the 'done' feature story on scrum boards and the release ticket. The release ticket currently contains a link to the release notes on a Confluence page. The release ticket could link to the features developed on the scrum by a 'dependant on' link for example if that would help me query.
So really, 'resolved' on the release project, minus 'resolved' on the scrum board, should give me the time it takes from 'done to implemented'.
I know we could have further statuses after 'done' on the scrum project which only show on the release board, but I'm trying to avoid anything that fundamental.
So I'm really looking for advice on the best way to link, and then the best way to query.
If it helps for querying, we've got 'Adaptavist ScriptRunner for JIRA' installed.
Any help gratefully received!
Thanks,
Simon
Dear Simon!
I similar cases we used a SQL query to Jira DB into change history tables.
For me this is simplest way to get such information.
Best regards,
Vasiliy.
Hi Vasiliy,
I'd like to be able put the output on a dashboard or a Confluence report though. Not sure that would be possible if the DB is being queried using SQL would it?
Regards
Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We manually make this SQL query and published result every month at confluence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.