Skip to content
This repository has been archived by the owner on Feb 21, 2019. It is now read-only.

Story disappears from Sprint after hard refresh #99

Open
openjck opened this issue Oct 25, 2012 · 6 comments
Open

Story disappears from Sprint after hard refresh #99

openjck opened this issue Oct 25, 2012 · 6 comments

Comments

@openjck
Copy link

openjck commented Oct 25, 2012

Steps to repeat

  1. Visit the 2012-10-16 MDN Sprint
  2. Click Manage stories
  3. Click on the red arrows for the story Start some basic implementation for Revision Dashboards
  4. Click Save
  5. Visit the 2012-11-16 MDN Sprint
  6. Click Manage stories
  7. Click on the green arrows for the story Start some basic implementation for Revision Dashboards
  8. Click Save
  9. Notice the story appears in the Sprint
  10. Do a hard refresh
  11. Wait a minute or two
  12. Do a normal refresh

Actual results

The story disappears from the 2012-11-16 MDN Sprint.

Expected results

The story remains in the 2012-11-16 MDN Sprint.

@openjck
Copy link
Author

openjck commented Oct 25, 2012

One more thing. The story doesn't just disappear from the new Sprint, it reappears in the old Sprint.

@openjck
Copy link
Author

openjck commented Oct 25, 2012

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.

@pmclanahan
Copy link
Contributor

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 s= whiteboard tag, and vice versa. It's possible that SB could keep track of the source of the last sprint move, but that seems as though it'd be confusing for people as well if you, for example, moved a bug via SB, and then Les changed the s= tag in bugzilla. His wouldn't work in that case.

@pmclanahan
Copy link
Contributor

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 s= tag.

@openjck
Copy link
Author

openjck commented Oct 25, 2012

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

@pmclanahan
Copy link
Contributor

Exactly. It'll most likely happen. Hopefully sooner than later.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants