You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user is responsible for supplying a JQL (Jira) or WIQL (Azure DevOps) query that Quality-time uses to get the user stories from the source. So it's up to the user to decide which user stories to include. The user could just as wel use this metric to count the points of e.g. completed user stories or user stories in the current sprint.
Tasks:
Rename the key of the metric to user_story_points in the data model
Change the name of the metric to "User story points" and update the description
Add both user_story_points to the Quality-time source, and keep ready_user_story_points so Quality-time can measure old versions of itself.
For metrics that use the old default name "Ready user story points" add a custom name "Ready user story points" to prevent the name from changing to "User story points"
The text was updated successfully, but these errors were encountered:
Rename the 'ready user story points' to 'user story points' as it can not just be used to count ready user stories, but rather any selection of user stories. Closes#1415.
The user is responsible for supplying a JQL (Jira) or WIQL (Azure DevOps) query that Quality-time uses to get the user stories from the source. So it's up to the user to decide which user stories to include. The user could just as wel use this metric to count the points of e.g. completed user stories or user stories in the current sprint.
Tasks:
user_story_points
in the data modeluser_story_points
to the Quality-time source, and keepready_user_story_points
so Quality-time can measure old versions of itself.ready_user_story_points
metric from the Quality-time source on the next major version: see Code to remove on the next major version of Quality-time #1416The text was updated successfully, but these errors were encountered: