Include "Feedback" in cycle time as well #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
okurz
commented
Feb 27, 2024
Only counting "In Progress" yields unrealistically low cycle time values and would not reflect overall time that a common development ticket is being worked on within a team as often we use "Feedback" when waiting for others within the team, e.g. for code review. This commit counts time in status "Feedback" same as "In Progress" to account for that. The test adaptions include the definition of "Feedback" in the mocked data as well as a mock entry for a ticket in "Feedback" with according adaption in the assertion but no assertion is added for the calculation to include tickets which had transitioned over that state. Related progress issue: https://progress.opensuse.org/issues/155917
okurz
force-pushed
the
okurz-include-feedback
branch
from
b76c070 to
99009f4
Compare
Martchus
approved these changes
Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only counting "In Progress" yields unrealistically low cycle time
values and would not reflect overall time that a common
development ticket is being worked on within a team as often
we use "Feedback" when waiting for others within the team,
e.g. for code review.
This commit counts time in status "Feedback" same as
"In Progress" to account for that.
Related progress issue: https://progress.opensuse.org/issues/155917