Summary field made up of Issue field values

Question

We have a naming convention for a particular project for logging 3RD Party email notifications. Format: 3RD PARTY - : - - : All these fields are required in the Jira portal form, is there a way the summary field can be automated based on selected values? Additionally, could the summary field change/update if fields are updated.

Danny Barber · Answer

Thank you, I am going to try this. I'll make sure to feedback to you.

Danny Barber · Answer

This particular project relates to 3rd party outages, these notifications are created by myself and the naming convention is all made up of these fields anyway.

These notifications come in daily and sometimes in the masses, I am looking for ways to streamline the process and make it a little more efficient.

I've also noticed the quality of the summary changes slightly depending on the person who creates the change if it's not me.

I have a dashboard which just has Due Date, Issue Type, Issue Key and Summary visible so having a standard summary really would help in this instance.

Nic Brough -Adaptavist- · Answer

Welcome to the Community!

Do not try to do this.

At least, not for your people.  It's fine if it is an automated report, but you should never denigrate and ignore your humans by destroying what they wrote to summarise their issue.

There is nothing wrong with your naming convention, but it should be going into dedicated fields for reporting, not the summary which is for humans to briefly describe (and recognise later) the problem.

This might seem grumpy, but I've recently had a customer who had problems with issue reporting and "you ignore what people are telling you" came out at the top of the list of reasons people were unhappy with Jira.  Removed the script that was destroying people's summaries and that complaint disappeared!