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
{{ message }}
This repository has been archived by the owner on Feb 21, 2019. It is now read-only.
Currently, we use scrumbugs to specify which sprint a story goes in.
However, we still use the p= whiteboard data in Bugzilla to specify how many points a story is.
This is a total pain in the ass for sprint planning where we're estimating the point values for the stories and then figuring out which ones need to be in the sprint because there's a 10-minute lag between when we set the point values in Bugzilla and when they show up in scrumbugs. Ew.
My vote is we move setting the point values to scrumbugs.
Possibilities:
Scrumbugs does all point values: create a new column, migrate all the existing p= data to the new column, add point-value-setting code to the various views and remove code that parses the p= whiteboard data
Set initial point values in Bugzilla and override them in Scrumbugs: create a new column, add point-value-setting code to the various views, add code that uses point values from Scrumbugs if they're specified instead of point values in Bugzilla
Are there other possibilities? Does doing this make it more likely we want Scrumbugs to institute what point values actually mean?
The text was updated successfully, but these errors were encountered:
Currently, we use scrumbugs to specify which sprint a story goes in.
However, we still use the p= whiteboard data in Bugzilla to specify how many points a story is.
This is a total pain in the ass for sprint planning where we're estimating the point values for the stories and then figuring out which ones need to be in the sprint because there's a 10-minute lag between when we set the point values in Bugzilla and when they show up in scrumbugs. Ew.
My vote is we move setting the point values to scrumbugs.
Possibilities:
Are there other possibilities? Does doing this make it more likely we want Scrumbugs to institute what point values actually mean?
The text was updated successfully, but these errors were encountered: