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

Story cannot be removed #78

Open
whimboo opened this issue Sep 11, 2012 · 10 comments
Open

Story cannot be removed #78

whimboo opened this issue Sep 11, 2012 · 10 comments
Labels

Comments

@whimboo
Copy link

whimboo commented Sep 11, 2012

We accidentally added a story to the scrumbu.gs website for Mozmill Tests. Later we removed the appropriate whiteboard entries from the bug in bugzilla. But the story still remains in the list of backlog stories. There is no way to get rid of it. There is a high chance that an admin could add it again to the current list of stories.

Please make it possible to fully delete a story.

@bensternthal
Copy link
Contributor

Can you add the specific bug number? I'll take a look.

@pmclanahan
Copy link
Contributor

So, scrumbugz is about to get an update to how it pulls in and keeps stories up to date. My guess is that the issue is either that the update for that backlog hasn't run yet (only every 4 hours), or the backlog is huge and has fallen back to only updating bugs with scrum data in the whiteboard. The problem with the later is that it won't update any bug that previously had whiteboard data but now does not. This will be fixed in the next release.

@whimboo
Copy link
Author

whimboo commented Sep 12, 2012

Can you add the specific bug number? I'll take a look.

Please see: http://scrumbu.gs/t/Auto_Dev/Sprint_Q3/bugs/

It is bug 517982 in the backlog entry list.

The problem with the later is that it won't update any bug that previously had whiteboard data but now does not. This will be fixed in the next release.

So this seems to be the reason here. We have removed the entries from the whiteboard.

When will this update go live?

@pmclanahan
Copy link
Contributor

Should be in the next day or two.

@whimboo
Copy link
Author

whimboo commented Sep 17, 2012

I can't see an update yet. Has the new version not pushed yet?

@bensternthal
Copy link
Contributor

Henrik... the new build was put on dev on friday but we have not tested/deployed yet.... and pmac is now on PTO so we will not be updating until he returns in a week.

I'll poke around today and see if i can get a workaround to remove that pesky bug..

@ssssssssssss
Copy link

Dear Mozillians,

Is this code base still in active development? I see some bugs involved in data syncing between Scrumbugz and Bugzilla, and the CI is always failing. Is it mature enough to use in daily basis?

@pmclanahan
Copy link
Contributor

@ssssssssssss While the development isn't particularly active at the moment, and there are certainly bugs, many teams at Mozilla use this on a daily basis. I hope to spend more time on it soon.

@ssssssssssss
Copy link

@pmclanahan Thank you for your answer. Which commit shall we pull? Is it always latest master?

@pmclanahan
Copy link
Contributor

@ssssssssssss I'm using latest master on scrumbu.gs. If you need to patch some things to get it working on your installation then basing a branch on master would be good. Rebasing should be easy. Though if you do I'd like to know so we can hopefully upstream more flexibility.

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

No branches or pull requests

4 participants