nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Keeping Epic Name and Summary in Sync

Amy_Hall

Is there any way to automatically set the Epic Name to the Summary or vice versa? We want these values to be the same. Because we are integrating with Roadmunk and their cards display Summary whereas the Jira Boards we have generally use the Epic Name field. When these two fields differ, it causes confusion and we see no value in them being different anyway.

Accepted answers

miikhy

Hi Amy!

There's unfortunately no native feature for that.

That being said, you could use third party apps to have a post-function in your Epics workflow after creation (before reaching first status) which would be copying summary to Epic Name. If you already have any script app such as PowerScript or ScripRunner you can even script it

Hope this helps!

Cheers

Abdul_dth56h

Navigate to Project settings > Automation

(A global rule will use your monthly limit, a project based one will not. By default a global rule is created.)

Create a new rule
At the 'New trigger' menu pick 'Field value changed' (located under 'Issue triggers' subheading).
Set the values as follows:
Field value changed: (select both) ‘Epic Name’ and ‘Summary’
Change type: (select) ‘Any changes to the field value’
For: (select both) ‘Create issue’ and 'Edit issue'
At the 'Add component' screen pick 'New condition'.
Select ‘If / else block’.
Select ‘Add conditions…’.
Select ‘Advanced compare conditions’.
Set the values as follows:
First value: {{fieldChange.toString}}
Condition: (select) ‘does not equal’
Second Value: {{issue.epic name}}
At the next 'Add component' screen pick 'New action'.
At the 'New action' screen pick 'Edit issue' (located under 'Issue actions' subheading)
In the 'Choose fields to set...' dropdown pick 'Epic Name'
Click on the '...' (ellipsis next to the new text field) and click on 'Copy from'. The text field will turn into a button. Click the button.
In the 'Field to copy value from' dropdown menu pick 'Summary'.
Save.
On the left hand side right at the bottom click ‘Add component.’ (This link will be above ‘Add Else’.)
At the 'Add component' screen pick 'New condition'.
Select ‘If / else block’.
Select ‘Add conditions…’.
Select ‘Advanced compare conditions’.
Set the values as follows:
First value: {{fieldChange.toString}}
Condition: (select) ‘does not equal’
Second Value: {{issue.summary}}
At the next 'Add component' screen pick 'New action'.
At the 'New action' screen pick 'Edit issue' (located under 'Issue actions' subheading)
In the 'Choose fields to set...' dropdown pick ‘Summary’
Click on the '...' (ellipsis next to the new text field) and click on 'Copy from'. The text field will turn into a button. Click the button.
In the 'Field to copy value from' dropdown menu pick 'Epic Name'.
Save.
Name your automation and click ‘Turn it on’.

All comments

miikhy

Hi Amy!

There's unfortunately no native feature for that.

Hope this helps!

Cheers

Amy_Hall

that's what I suspected but I wanted to be sure I wasn't missing something. Thanks for your reply.

miikhy

I’m happy to see you’re having this consistency between Name and Summary as it’s getting very confusing when they differ!

Have a great day, Amy!

Dave Furlani_ly96ix

I'd also like to keep the Epic name and Summary as the same, or more importantly, only prompt the user for one. Unfortunately Epic Name is a required field and locked on the instance we have, so users are forced to enter data to both.

That said, epic name isn't offered when creating an epic through Boards > Backlog > Epics > Create Epic, so I assume something has been added to our Jira (v7.11) that changes the behaviour of the field without changing the default create epic screen.

I think my only option is to stop Epic Name from being a required field, but as it's locked I can't do that through the UI. https://confluence.atlassian.com/jirakb/how-to-unlock-a-locked-jira-software-field-779158866.html

I'd love to know how the field became required and locked too, but I'm new here so I doubt I'll find that answer.

Arkadiusz Głowacki

If anyone is still looking for an answer to this question in (or after) April 2020, then two things changed here:

1. Next-gen epics have only summary, the epic name is gone.

2. You can use automation to set epic name to summary or vice versa without a need to install any addon, it is available in Jira-Cloud natively.

Coco S Chaussée

hi -

I'm assuming that you're referring to Classic projects in #2. Can you provide more information on the native automation, please?

Thank you

Arkadiusz Głowacki

Hi @Coco S Chaussée ,

You can read more about it here: https://www.atlassian.com/software/jira/features/automation and take a look at this video: https://www.youtube.com/watch?v=iMxv8u30DH8
or read in more details here: https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Or you can navigate to System > Automation rules and try it by yourself.

Regards

Arek

Patricia Mayer

Hi can I have further details? I tried to create an automation rule, to get the Epic Name from Summary at creation stage, but since Epic Name is a required field, it doesn't allow me to create the ticket without putting a value there.

Abdul_dth56h

Navigate to Project settings > Automation

(A global rule will use your monthly limit, a project based one will not. By default a global rule is created.)

Create a new rule
At the 'New trigger' menu pick 'Field value changed' (located under 'Issue triggers' subheading).
Set the values as follows:
Field value changed: (select both) ‘Epic Name’ and ‘Summary’
Change type: (select) ‘Any changes to the field value’
For: (select both) ‘Create issue’ and 'Edit issue'
At the 'Add component' screen pick 'New condition'.
Select ‘If / else block’.
Select ‘Add conditions…’.
Select ‘Advanced compare conditions’.
Set the values as follows:
First value: {{fieldChange.toString}}
Condition: (select) ‘does not equal’
Second Value: {{issue.epic name}}
At the next 'Add component' screen pick 'New action'.
At the 'New action' screen pick 'Edit issue' (located under 'Issue actions' subheading)
In the 'Choose fields to set...' dropdown pick 'Epic Name'
Click on the '...' (ellipsis next to the new text field) and click on 'Copy from'. The text field will turn into a button. Click the button.
In the 'Field to copy value from' dropdown menu pick 'Summary'.
Save.
On the left hand side right at the bottom click ‘Add component.’ (This link will be above ‘Add Else’.)
At the 'Add component' screen pick 'New condition'.
Select ‘If / else block’.
Select ‘Add conditions…’.
Select ‘Advanced compare conditions’.
Set the values as follows:
First value: {{fieldChange.toString}}
Condition: (select) ‘does not equal’
Second Value: {{issue.summary}}
At the next 'Add component' screen pick 'New action'.
At the 'New action' screen pick 'Edit issue' (located under 'Issue actions' subheading)
In the 'Choose fields to set...' dropdown pick ‘Summary’
Click on the '...' (ellipsis next to the new text field) and click on 'Copy from'. The text field will turn into a button. Click the button.
In the 'Field to copy value from' dropdown menu pick 'Epic Name'.
Save.
Name your automation and click ‘Turn it on’.

Shaun Newman_z384my

This was a MASSIVE help thank you!!

Brannon Fay_w9s7ig

Agreed! Big help. Thank you!

Jim Jacoby

I created another issue type (Epic Creator) that has the same fields as an Epic. Then, I have an automation task that, on creation of an Epic Creator task, copies Summary to Epic Name, and then changes the issue type to Epic. It seems to be working so far.

NSurtani

Worked like a charm!!! Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud