we just imported a project to our JIRA v6.3.11 and we shockingly realized that 2 custom field values were not imported. It's mysterious because bot fields are enabled for the project and the appropriate screens and the project import report screen put ticks nest to the custom fields. We checked the import xml and both fields are there with values!!
Anyway, we'd avoid the re-import because it's a really big project. Is there a way to add these custom field values by a script? Jelly or groovy? Or in SQL? We have the list of issues with the field values in a different JIRA and the projectID, issuekeys did not change.
Can you please advise?
You can re-import the list - if the lines have the current issue number in them, then the fields will be imported as changes. But you'll need to work out why they were ignored the first time.
Scripts can do it, including groovy. Jelly is deprecated, so I'd avoid that, and the standard rule for SQL is "don't". Just don't bother with SQL, it's harder than you think it is and can completely trash your system.
Or use bulk edit, if the data is simple enough
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs