-
Notifications
You must be signed in to change notification settings - Fork 20
Story disappears from Sprint after hard refresh #99
Comments
One more thing. The story doesn't just disappear from the new Sprint, it reappears in the old Sprint. |
Removing the s= tag from the story fixed the problem. The story previously had s=2012-10-16 in the whiteboard. It would be nice if Scrumbugs removed the s= tag for the user in cases like this. The last Sprint that was set should take precedence, whether it was through the s= tag or through the Scrumbugs interface. Right now, the s= tag is taking precedence even if a change was made on Scrumbugs more recently. Or better yet, Scrumbugs could write to the status whiteboard to always keep the s= tag and the current Sprint in sync. |
Yeah. This is the problem with using both methods to manage sprints. If a team wants to use scrumbugs, they probably shouldn't use the |
Scrumbugz updating the whiteboard is possible, but a bit scary. We're not writing to bugzilla so far, but we easily could. The scary part is that there are A LOT of different styles of info in the whiteboard. We'd just have to be very careful to preserve all of that and only change the |
Understood. I think it could be a nice feature. In addition to helping out with things like this, it would make it possible to search/sort/filter/etc. by Sprint in Bugzilla |
Exactly. It'll most likely happen. Hopefully sooner than later. |
Steps to repeat
Actual results
The story disappears from the 2012-11-16 MDN Sprint.
Expected results
The story remains in the 2012-11-16 MDN Sprint.
The text was updated successfully, but these errors were encountered: