Sprints lost after Jira update

[GeraldAT]

Hello,

I did an update of Jira from 5.1 to 5.2.2 Today I have Greenhopper 6.1.0 installed.

After the update I had to re-index. After that all Sprints were lost. Also the story estimations weren't displayed in the backlog.

How can I get back my Sprint data? Also the finished Sprints are gone.

Thanks

Gerald

[GeraldAT · Accepted solution]

We had duplicated fields (due to a Greenhopper update).

https://confluence.atlassian.com/display/GHKB/How+to+Fix+the+Duplicate+GreenHopper+Custom+Fields+After+Upgrading

That explains why the sprints were gone. After the update new fields for Sprint and Story Points were created. I merged the data. Now it's ok.

[Jeffrey Davidson]

We just had this exact issue as well. I ended up just updating the propertyvalue column of the propertynumber table from the newly created field id to the old field id, and all the sprints showed back up immediately. Thanks so much for pointing me in the right direction.

[C_ Faysal]

hi gerald.

can you confirm that all issues still exist?

could you add a screenshot of your empty planing board please?

[C_ Faysal]

No i mean the issues inside the sprints you are missing. My thought was aiming on some epic labels that might be highlighted unwanted wich will cause empty backlogs as well

[GeraldAT]

well, the issue basically exist, however some estimations were gone.

Unfortunately we already created new sprints, so I've got no emtpy board anymore.

[GeraldAT]

at this point - we just have started using Greenhopper - there were no Epics.

As I said the issues in the backlog were present. It seems that the Sprint Objects have been deleted.

[Renjith Pillai]

What does the database query say?

select * from AO_60DB71_RAPIDVIEW

[Theinvisibleman]

Hi Gerald,

Hmm, it's rather unusual that your Sprints were lost. In that case, may I know if your boards still show up fine?

If it does, could you try restarting your instance, and see if it helps?

[GeraldAT]

Thanks for your answer.

The boards were empty. I'll try the restart approach.

[GeraldAT]

It's been a while.

Restarting Jira did not change anything.