0

I have updated the Project Backlog plugin from version 1.2 to version 1.2.3 and after that, the backlog of one of my project was in an inconsistent state:

  • Several cases had the same priority
  • Several cases had 0 as priority
  • When I started fixing the backlog, I started to see values like -1 for some cases

Is this something that has been reported before? And is it something that the backlog database fix/repair method described in "How do I fix a backlog order with a duplicate number" would have fixed?

flag

1 Answer

0

It sounds like your project backlog was in a correct order before upgrading to 1.2.3...is that the case?

It's also possible to see duplicate values in the backlog column when more than one project is visible (the backlog is per-project, so every project can have a backlog 1, backlog 2, etc.). The 0 and -1 backlog entries are definitely incorrect though.

The method described in the linked question should repair this problem. If you continue to see invalid backlog values, please update this question with details of what actions you took that resulted in the incorrect backlog values.

link|flag
The backlog was indeed in correct order before the upgrade. When I saw the duplicates, I was only looking at one milestone for one project. The backlog has been reordered manually now but I may try and use the repair method. – Rodrigue Nov 16 2010 at 9:59

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.