i had try to change the field issuestatus in table jiraissue but when i make search the status hasn't change. have i to change other table like OS_CURRENTSTEP, OS_HISTORYSTEP or changeitem?
Yes.
But don't. Status especially is one of the worst things to try to do. It is NOT a field for a start, it's an indicator of a position in a workflow, and you need to update the workflow tables as well as the issue.
If you are going to change the database, then you MUST:
I can't emphasise the offline or backup elements enough - this is dangerous and can destroy your installation.
To fix the current damage you've done, run the integrity checker. Then go back, work out exactly what you need to hack in the database, test the changes properly in a test system, book the downtime and backups and try again.
Or, do it properly, and use the workflow
Have tried reindexing JIRA after applying this SQL query. Or did you run by shutting down the JIRA instance. If not, reindexing JIRA should show you the updated the status for the issue.
EDIT: Posted after Nic's answer. Can anyone plz convert it into comment, as I can't from my side!
i see the update in my issue but not in my research witout shutting down. i don't know if it keep the old value somewhere. do you think i need to restart Jira?
Yes i unsterdant but to the beginning i want to when i change a customfield the status change and the only one solution i found is to change value in database. Have you any ideas to help me?
As before. You *must* have Jira offline if you amend the database. Even if it works sometimes, it won't always, and it's really not safe.
You should do this properly and use the workflow.
Could you describe the actual problem you have that lead you to hack the database instead of dealing with it properly?
As Nic mentioned, you should restart and/or reindex once you are done with exeuting the SQL query.
I have one customfield which have the same fonction that the status. when i choose some values in this customfield i need to close the issue. i need to keep this customfield because user use it and change the way to work couldn't be easy. it's just to make automatic these little things.
It looks like you're new here. Sign in or register to get started.
