direct jira database changes can not immediately take effect

[fabby]

i want to auto release version using sql script.

so i set "RELEASED" field's value to 'true' in table "projectversion".

when i update RELEASED' value using sql script,it doesn't immediately takes effect.

the updated version will display 'released',only after some manually changes on "Versions" tab.

for example,i changed version "V1" 's released state using sql script."V1" still displays "unreleased" in UI.

but when i manually change the version "V2"'s version name(i think this manual action trigger the synchronizing between jira ui cache and the database ),then the version "V1"'s released state will be 'released'.

[Nic Brough -Adaptavist- · Accepted solution]

No. You can NOT use SQL to amend a Jira database while it is running.

It caches data, and has no way of knowing that you're doing the updates. You can irrepairably damage your installation.

You REALLY need to do the following IMMEDIATELY:

• Stop Jira
• Run the SQL to reverse your changes
• Restart Jira
• Re-index it
• Run the integrity checker

In the longer term, you need to code something that uses the API, but I'd concentrate on undoing the damage you may have done already

[Radu Dumitriu]

That should be placed in the FAQ, here. https://confluence.atlassian.com/display/JIRA/JIRA+Administrators+FAQ

[Nic Brough -Adaptavist-]

Yes. Somewhere near the top, in big red letters ;-)

[Jobin Kuruvilla [Adaptavist]]

Just to add on, releasing a version does more than just setting that value to true in the table. It also looks at unreleased issues in the release and prompts the user to move to a new release or resolve them.

It is wise to follow Nic's advise on coding something that uses the API.

[fabby]

thanks for all your advisement!

[fabby]

i use CLI as the resolution.

https://answers.atlassian.com/questions/74037/is-it-possible-use-soap-api-via-php