You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I migrated tickets from another system into Jira. That other system had 4 different label fields. I want to capture all the labels for each ticket in those different fields and put them all in the `Labels` Field in Jira.
Hi Robert - Welcome to the Atlassian Community!
You can do that using Automation For Jira. Here is some information on the tool to get you started:
There are two types of automation:
Automation Basics: https://www.atlassian.com/software/jira/guides/expand-jira/automation
You can do this via global rules to apply to all projects also. You'll need to be a Jira Admin/Site Admin, go to Jira Settings > System > Automation Rules (left-hand menu).
For more on using Automation For Jira see these help pages.
Jira Automation Template Library to help get you started quickly:
https://www.atlassian.com/software/jira/automation-template-library#/labels/all/customLabelId/1453
For your process, you would start with a Schedule Trigger for 1 day.
Then use JQL to identify the issues you want to modify.
Then do a new Action for Edit Issue.
Choose the Labels field
Click the 3 dots menu and select Copy From
Select Current Issue
Click on the words Current Issue again and select From this Issue and then select the field.
Then save and publish the rule.
Then click on the Run rule button.
You will probably need to do that 4 different times, changing the Copy from field value for each of the 4 fields you imported.
You can use Jira Automation to do this.
When you use the "Edit issues" action with the "Labels" field, it gives you an option to "add/remove" values. You'd use the "Add" part to copy a value from one of those custom fields into the "Labels" field.
Use that same action several times, once for each custom field.
An outer loop through all the issues of interest in the instance should accomplish the goal with one theoretical click.
If the "Labels" field already has values in it, then I might suggest creating another "Labels-temp" field to help you test this rule. That way you can clear it out while you debug your rule, and then run it one last time against the real "Labels" field when you're confident it's working.
If you're new to Automation, here are a few other tips:
Best wishes!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.