Can't seem to get this to work. Keeps throwing error on invalid identifier; no matter what the last line is, it's always invalid.
The reason we're doing via DB is because we have (per ITIL) all issues set to lock for editing on closure. Since it's a holistic property, UI Admin cannot bypass it and we don't want to turn it off...
update customfieldvalue set customfieldvalue.textvalue = 'test_text' where customfield = 16540 and jiraissue.issuenum=297 and jiraissue.project = 17650 and jiraissue.id = customfieldvalue.issue ;
Community moderators have prevented the ability to post new answers.
Please don't do it. With an high probability it will broke the index. Better set, just for few seconds, the properties jira.issue.editable as true on the status of the workflow.
Thanks! All I needed was someone from an Atlassian team to advise against it Going to screenshot the same and push back on the request...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Never write to a JIRA database when it is running. Avoid writing when it's offline, and get a backup before you try it!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Nic Brough. I'm glad there are resources who can swiftly point out the dangers of altering the DB! Adding it to my business case.
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.