Referring to other fields during bulk edit?

[Rich Pixley]

When moving issues from a team managed project to a company managed project, all "epic name"s got set to the same value.  This isn't useful so I'd like to bulk edit them to something that is useful, like, perhaps, the title of the epic.

Is there a way I can refer to a second field while setting a field?  Like, is there a variable dereference mechanism?

I checked the doc but I don't see anything.

[Ste Wright · Accepted solution]

Hi @Rich Pixley 

As far as I know, there isn't an option to do this.

There's two good options here though.

---

(1) CSV Export/Import

Once you've migrated your Project across...

• Export the Epics, inclusive of Issue Key, Summary, and Epic Name
• Create an Import file, customise the Epic Names
• Upload it, mapping the Issue Keys so they update, and the Epic Name, so they can be customised

See more information on importing here: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

---

(2) Automation 

Use an Automation Rule to set the Epic Names - this is an option when the data can be copied from somewhere else (eg. the Summary field)

You can use a Scheduled rule to run the rule once, then delete/deactivate it - the rule might look like:

• Trigger: Scheduled
  • Run a JQL Search = TRUE
  • JQL = issuetype = Epic
• Action: Edit Issue
  • Field = Epic Name
    • COPY Summary from Current Issue

You could also use Smart Values if the Epic Name is the Summary and another field, or some manual text - for example, if the Epic Name should be "Epic: <Summary>" - the value to enter in the Edit Issue Action would be "Epic: {{triggerissue.summary}}

See more information on Automation here: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

---

Let us know if either of these options would work for you!

Ste

[Rich Pixley]

Both look good.  Thank you!

[Mark Segall · Accepted solution]

Hi @Rich Pixley - Instead of a bulk edit, you can create a one-time automation rule to bulk update.  It would look something like this:

• TRIGGER: Scheduled (frequency doesn't matter as you can manually kick it off)

  • issueType = Epic

• ACTION: Edit Issue (Epic Name)
  • {{issue.summary}}

Note - Automation has limits so if you have more than 100 Epics, you could add the JQL clause AND "Epic Name" ~ "TEMPEPICNAME" which will allow you to keep executing the automation until all of the Epics have been addressed.

[Rich Pixley]

Thank you!