Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Keeping Epic Name and Summary in Sync

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.

3 answers

1 accepted

1 vote
Answer accepted
miikhy Community Leader Jun 22, 2018

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

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

miikhy Community Leader Jun 22, 2018

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!

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.

Like Christine Gardner likes this

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. 

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

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

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.

Like Ayelet Ben-Tzur likes this

I'm with @Patricia Mayer - I can't pass the mandatory setting - post function or any automation runs AFTER the issue is created and it can't be created in the first place without the Epic Name.

Can anyone assist on this please?

I see @Arkadiusz Głowacki  you mentioned epic name is gone in cloud version - my company is using datacenter -- we are trying to keep epic name and summary in Sync.. If Epic name is gone then what is sued in all displays as that short name was used on boards

@Ayelet Ben-Tzur @Patricia Mayer - were you able to solve this? I would like to setup an automation rule so that the epic name equals the summary at both creation and for any subsequent updates. 

I haven't. If you manage to, PLEASE tell us how :)

@Ayelet Ben-Tzur I was not able to get it to work on epic creation but I was able to write an automation so that if the epic summary changes, so does the epic name. 

When: Issue Updated

If: Summary does not equal the Epic Name from the Current Issue

Then: Edit Issue fields (Epic name = Copy from Summary from Current issue)

Yes, this part is no problem, the problem is with the creation.

Thank you.

@Ayelet Ben-Tzur @Sara Watson I've posted what worked for me in the answers.

Navigate to Project settings > Automation

1) Create a new rule (a global rule will use your monthly limit, a project based one will not.)

2) At the 'New trigger' screen pick 'Issue created' as the trigger. Save.

3) At the 'Add component' screen pick 'New condition'

4) At the 'New condition' screen pick 'Issue fields condition'

5) In the 'Field' dropdown pick 'Issue Type'

6) In the 'Value' dropdown pick 'Epic'. Save.

7) At the 'Add component' screen pick 'Branch rule / related issues'

8) The 'Type of related issues' should be set to 'Current Issue'. Save

9) At the next 'Add component' screen pick 'New action'.

10) At the 'New action' screen pick 'Edit issue' (it's located under 'Issue actions' subheading)

11) In the 'Choose fields to set...' dropdown pick 'Epic Name'

12) 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.

13) In the 'Field to copy value from' dropdown menu pick 'Summary'.

14) Save. Name your rule and turn it on

15) Create another rule (this is to keep changes in sync).

16) At the 'New trigger' screen pick 'Field value changed' (it's located under 'Issue triggers' subheading).

17) In the 'Fields to monitor for changes' dropdown menu pick 'Summary'

18) In the 'For' dropdown menu pick 'Edit Issue'. Save

19) At the 'Add component' screen pick 'Branch rule / related issues'

20) At the 'Branch rule / related issues' screen press Save.

21) At the next 'Add component' screen pick 'New action'.

22) At the 'New action' screen pick 'Edit issue' (it's located under 'Issue actions' subheading)

23) In the 'Choose fields to set...' dropdown pick 'Epic Name'

24) 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.

25) In the 'Field to copy value from' dropdown menu pick 'Summary'.

26) Save. Name your rule and turn it on.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

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

Events near you