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
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 ...
Hi ,
Did you tried , the integrety checker?
https://confluence.atlassian.com/display/JIRA/Using+the+Database+Integrity+Checker
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ben,
We have run into the exact same issue. Did you reach a resolution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You probably need to re-index JIRA in order to solve this. To re-index JIRA follow the steps:
When finished you searches should work fine!
hope this helps,
Jacques.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ben, this could be a index problem. Have you already tried reindexing the Jira instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ramiro, Yes I have tried re-indexing, this has not worked. Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have tried re-indexing a few times today, bu this is not working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.