*CRITICAL* Unable to Reorder Backlog

Edit Subject

Hi Jheinen,

Sounds like it might be an issue with the Client. Try stopping it, and running through the steps on this topic:

http://community.danube.com/danube/to...

When you start it back up, if you still can't re-order the backlog items you may want to try accessing the backlog from another client system. That will narrow down where the issue lies and we can troubleshoot from there.

Followed the steps but still have the same problem. Also tried a different client, same result. I also noticed that some of the PBI's I can move to one place in the backlog, but not another. Also, some appear in the list as duplicates (i.e. two with the same key and data appear in two place on the list). Adding a task to one of them results in the task appearing in both of the PBI's.

What version of ScrumWorks Pro are you currently running?

You can access this easily through the Help - About ScrumWorks Pro menu in the desktop client.

Version: 4.4.0
Build: 2010-06-25 15:03 r28030

Hi!

Could you gather some information for us so we can take a deeper look at this?

Could you please enable your Java console and then go back into Scrumworks and try to adjust the PBI's again? Then send us the text output from the console, along with the Scrumworks.log file and the text from the Scrumworks 'About Scrumworks' area of the in program help menu. Please email all this to Support@danube.com.

The log file can be found here: (installdirectory)\server\scrumworks\log\server.log

And here are the instructions for enabling the Java Console:

1. Launch the WebStart CacheViewer:

http://danube.com/docs/scrumworks/pro...

The Java Control Panel will launch behind the CacheViewer.

2. Choose "Edit" menu > "Preferences" > "Advanced" tab > "Java Console". Select "Show Console".

Or

2. Select the "Advanced" tab > "Java Console" > select "Show Console".

Files have been sent. Note that there was no output in the console. I attached a thread dump.

Great! We will look them over and contact you as soon as we can.

We have been working with Jheinen and identified the core issue causing this. The import had a fairly large number of PBI's being brought in at once, and this caused some corruption issues within Scrumworks. We are working to create a permanent fix for a future update of Scrumworks to prevent this kind of corruption with large scale imports.

In the short term here are some suggestions for user who have a large number of PBI's to import:

Try to import them in groups of 10-20 PBI's at a time.

If, once they are imported, you see duplications or encounter UI issues like those described above, try creating a new empty release within Scrumworks and drag the problematic PBIs to that release. This should reset them within the UI and you can then return them to the correct release. Any PBI's that cannot be moved at all will have to be deleted and recreated.

Thank you to Jheinen for his patience as we diagnosed this issue, and if anyone has any questions or concerns, please let us know!

We had this problem as well but it was not from an import; all of our Stories were manually entered. There were 148 of them which

Dragging all the stories to a different product and cleaning up remaining "stuck" ones seems to have corrected the issue.