we use JIRA tasks to follow up patch deliveries.
The JIRA task description includes all the JIRA bugs included in the patch.
Anyway, we have manually splitted these tickets per status (open, fixed, closed) in order to follow up the progress.
The point is that we have to edit the JIRA task each and everytime a JIRA bug is fixed, in order to move it to the related chapter (from "under analysis" if it is in open status, to "to be validated" if it has been fixed by R&D).
Does anyone know if we can make it dynamic?
e.g. in the chapter "under analysis", include all the tickets based on a search results (ex tickets open and with a specific label).... same for "to be validated"...
Thanks per advance for your answer,
Sounds like you are trying to fight the inherent design, which is just gping to make life more difficult.
Why not use a combination of versions and components to manage the status of a patch, and some custom dashabords to show progress. (Built-in Version reports are also great)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs