I have a JIRA project that has a custom field dropdown which is multi level and has a few hundred values in it. There are people using this custom field in their JQL to add issues to their board and in their filters, so if I use this custom field in another project its possible these issues will also appear. This is a central custom field that a lot of other projects depend upon.
For this reason, I'd like to make a copy of this custom field, but how? There is no option for this. I can find solutions on taking the value of one custom field and setting it in another (with Scriptrunner), but this is not what I'm talking about. I simply want to copy a custom field instead of re-creating it and hundreds of values within it.
You can add a new Context to the field and show different values for that field based on project or issue type or a combination of both.
Go to Settings > Issues > Custom fields
Then search for the custom field
Click on the 3 dots to the far right of the field and choose Contexts and default value
Then click on Add New context
You will need to add the options from scrap (or cut and paste one at a time)
Be sure to Edit configuration to limit to certain issue types and/or projects.
True - so we use an add-on called External Data For Jira Fields found in the Marketplace here: https://marketplace.atlassian.com/apps/1219994/external-data-for-jira-fields?hosting=cloud&tab=overview
You can connect your field to a database or XML or other sources. I use both types of sources right now until I fully move to a database with a small Ruby front end to it so non-Tech people can update and maintain separate lists. Right now I am generating an XML file from a spreadsheet for a few fields.
It's only for Jira Cloud.
There is also this one that I saw yesterday but I have not looked at it at all yet:
There are versions for Cloud and for Server.
Either route is worth the investment for me. :-)
At that moment we didnt have anything to manage it. Now I have an excel sheet, as in this custom field drop down we have items that when issues are created with those items, map to individual Slack support channels, so I keep track of which items will send an "issue created" webhook to which channel, and the JQL for the webhook.
I needed to copy at the time, but have now convinced the project admin to use the existing one, and work with a team to clean it up instead of making his own version.
Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events