BACKGROUND: Several of Control Chart Gadgets were calculating issues' life cycle data depending on certain statuses, i.e. "Ready for Prod".
PROBLEM: We made an additional bulk change that transitioned many issues once more through the "Ready for Prod" status. Hence, now many issues have duplicated transitions to the same status and data in the gadgets are negatively affected, lifecycle is way too long because Time in status added up additional time range.
IDEAS to solve:
- undo a bulk change (as I know we dont have such function in JIRA)?
- delete a record from history (is there a way to do so?) i.e. delete the duplicated Time in status?
- maybe we can setup the control chart gadget in any way so it would exclude hourly range when the duplicated status was made?
You can consider Time Between Statuses app. It lets you set different statuses for the time counter`s start and stop. Additionally, this tool lets you set extra conditions for timer triggers such as first/дфіе transition to/from status.
Hope this function will help you calculate cycle and lead data in the way you need.
Regards
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.