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

bmacdonald05 March 24, 2013

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

7 answers

1 vote
Radu Dumitriu
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 24, 2013

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 ...

0 votes
Filipe March 11, 2014

Hi ,

Did you tried , the integrety checker?

https://confluence.atlassian.com/display/JIRA/Using+the+Database+Integrity+Checker

Regards,

0 votes
Saurabh Malik March 8, 2014

Hi Ben, Same issue here. Any luck.

0 votes
Saul Perdomo June 4, 2013

Hi Ben,

We have run into the exact same issue. Did you reach a resolution?

0 votes
Jacques
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 24, 2013

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

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

When finished you searches should work fine!

hope this helps,

Jacques.

0 votes
Ramiro Pointis
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 24, 2013

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

Ramiro Pointis
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 24, 2013

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.

bmacdonald05 March 24, 2013

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

bmacdonald05 March 24, 2013

I have tried re-indexing a few times today, bu this is not working.

I will have a look at the logs, as restarting the box is definatley on the bottom of the list.
0 votes
Henning Tietgens
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 24, 2013

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

Suggest an answer

Log in or Sign up to answer