Stories no longer shows up in Agile board after update

Thorbjørn Sørensen March 25, 2015

For some reason, after I updated Agile and Atlassian Universal Plugin Manager, all the Epics in the Agile board no longer showed their name, instead they showed "unlabeled" I bulk changed them all by adding a label to them.. and then their names showed up... however, all the stories attached to them are no longer showing up in the board if I "sort by epic". It is as if some sort of connection was lost. We had to reastart the service after updating Atlassian Universal Plugin Manager.. and I suspect that this is the reason for our issues.

Anyone know of any "tricks" so I can get all the issues/epics to "reattach" to each other?

If I open an Epic, it all is there... only on the agile board it appears broken.

3 answers

1 accepted

1 vote
Answer accepted
Simon Kegel //SEIBERT/MEDIA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 25, 2015

Hey there,

had such an issue in the past it just crashed the filters on the agile board - after reconfiguration it worked again.
did you reindex after the update ? I missed it back then ..

Greets
Simon 

Thorbjørn Sørensen March 25, 2015

Yes, I re-indexed... I will try to do that again... will let you know what happens.

1 vote
Benito Picarelli
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 26, 2015

Hi Thorbjorn,

The background index is not as complete as the locked re-index:

  • Background re-index — This will re-index all issues in the background.
  • Lock JIRA and rebuild index — This will delete and rebuild all indices, including the comment and change history indices.

This page does a good job talking about indexes: https://confluence.atlassian.com/display/JIRA/Search+Indexing

0 votes
Thorbjørn Sørensen March 25, 2015

Re-indexing a second time seems to have fixed it.

Only difference was that I did not do background indexing the second time.. do not know if that have anything to say?

Simon Kegel //SEIBERT/MEDIA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2015

uff - logical it shouldn't affect the index itself ... but could be I'm not sure on this

Suggest an answer

Log in or Sign up to answer