Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Updating Text of Specific Issue's Custom Field via SQL

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 = customfieldvalue.issue

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

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 wink Going to screenshot the same and push back on the request...

Never write to a JIRA database when it is running.  Avoid writing when it's offline, and get a backup before you try it!

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

AUG Leaders

Atlassian Community Events