nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue workflow status different in query search to status displayed within the issue

unknown

So i have a custom worklow, which is working fine.

When you click on an issue type it displays the status of the workflow it is in, whcih is correct.

I then run a query to show all the issue types which use this custom workflow. The results display all the issues, but the status of these issues is incorrect. For example it says the issues is still in 'Open' when in fact it is at the next stage along.

I have only come across this this mornig when i moved the issue to the next stage. I have re-run the query, instead of using teh saved query and it doesnt change.

Any ideas?

Ben

Accepted answers

All comments

Henning Tietgens

Hi Ben,

this is the typical behaviour for an index error. Something in your workflow has edited the issue in the wrong moment and this change was not indexed.

To fix this, you can install the Script Runner plugin and run the built-in script to reindex a filter result. Out of the it's only possible to edit the issue again or to run a complete reindex (which makes your JIRA instance inaccessible for that time).

You should investigate which changes in your workflow may cause this error. Maybe you changed something or installed a new plugin?

Henning

Ramiro P

Hi Ben, this could be a index problem. Have you already tried reindexing the Jira instance?

Radu Dumitriu

Ramiro has a valid point, but this may be shown also by an inconsistency in the db. Try to validate first the instance ....

You should check for errors in the logs ...

Ramiro P

Restarting the server is the worst solution always (ugliest), but it's funny how it resolves many things. Take that as the last option and check Radu's answer, the error could be in the DB.

unknown

Hi Ramiro, Yes I have tried re-indexing, this has not worked. Thanks

Jacques

You probably need to re-index JIRA in order to solve this. To re-index JIRA follow the steps:

Select "Administration" from the upper right corner
Select "Advanced" from the "System" menu (enter your password if asked)
On the (first) Indexing tab, click the re-index option which is most appropriate
Click the "Re-Index" button