action #155917
closed
openQA Project - coordination #127031: [saga][epic] openQA for SUSE customers
openQA Project - coordination #152955: [epic] Metric-driven project management in SUSE QE Tools team
[backlogger] Count "Feedback" ticket state for cycle time as well size:S
Added by okurz 3 months ago.
Updated 2 months ago.
Description
Motivation¶
As discussed in the coordination call where we now look at our metrics, it would be a good idea to take Feedback into account for the cycle time.
Acceptance Criteria¶
AC1: The cycle time treats "Feedback" like "In Progress"
AC2: We are aware that "Blocked" needs to be used (instead of "Feedback") when waiting on external progress
Suggestions¶
- Count "Feedback" the same as "In Progress". We include tickets in "Feedback" when just waiting for others within the team would be counted towards cycle time
- Document in the wiki that waiting for external feedback should use Blocked
- Due date set to 2024-03-12
- Status changed from New to In Progress
- Assignee set to okurz
Thinking about it, if we would change https://github.com/openSUSE/backlogger/blob/main/backlogger.py#L154 to count "Feedback" same as "In Progress" then the times when we include tickets in "Feedback" when just waiting for others within the team would be counted towards cycle time which would be helpful. But for external feedback, like waiting for others outside the team that would also be counted towards cycle time which means that our cycle might increase significantly. I still think we should do that and when waiting for others we should ensure that we get feedback quickly or properly "block" on external issues.
Created
https://github.com/openSUSE/backlogger/pull/32
- Parent task set to #152955
- Tags set to reactive work
- Subject changed from [backlogger] Count "Feedback" ticket state for cycle time as well to [backlogger] Count "Feedback" ticket state for cycle time as well size:S
- Description updated (diff)
- Status changed from In Progress to Feedback
- Priority changed from Normal to Low
- Due date deleted (
2024-03-12)
- Status changed from Feedback to Resolved
Also available in: Atom
PDF