You've made changes that may require Jira to be re-indexed (this message is a little too frequent - it appears after some changes that do NOT need a re-index, but it's being cautious)
It is saying what you need to do - re-index Jira.
The index is a cached copy of some of the data in the database, optimised for searching - this srops Jira having to read the database for every single filter/search/report your users run. What you've just changed has invalidated some of that data and it needs to be rebuilt.
It's not critical, just something you should do as soon as you can. Your users may find searches don't work properly until you've done it, but your core data is safe.
just to add some additional information to "Nic Brough"s answer,
it's possible to index the system in the background while your users still have access to jira. This would take longer than rebuilding the index while locking jira down.
From my experience it's more practical to use the rebuild index function but that's just my preference since i have experience some freezing issues in jira after using the background indexing function.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG