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

Adding custom field values in an automation rule

Hi all,

When creating a Service Desk ticket via the portal, I'd like our customers to not enter the title in the summary and select the item they require from a dropdown list.

To that end, I've created a custom field with the drop down elements, and hidden the value of the summary. I'd like the summary to change its value to that of the dropdown list. 

Is there a particular JQL script I need to use here? 

1 answer

Hi, the summary field is a required field since it's the title of the issue, and if you hide it you won't be able to create any issues. It's one of the hard rules of Jira.

Perhaps making the component field required on your issue creation screen would help since you can configure the values of the component field and it works as a dropdown list.

JQL is a search language, not an automation/scripting language, so you can't update issues using JQL in the way you want to.

By the way, are the choices you would like to have in the custom field drop down from external sources? Like a product database or list of locations managed outside of Jira?

Hi there,

I should have clarified, I've hidden the value of the summary as it is still required, but I'm looking to use an automation rule to change the value of the summary. 

For example:

X raises a ticket that they require a new phone. they use a "request new hardware" issue type where the summary field is hidden. They are presented with a custom field called "hardware" which is a multiline choice custom field wherein they select "phone", they complete the rest of the ticket and submit it.


In this instance, I'd like the automation to find the value of "Hardware" and replace the value of "Summary" so that my customers are not having to put in the same detail twice. The custom field is created within Jira itself and added to the screen scheme so there's no issues about it being external (apologies if I misunderstood that part) 

Pretty sure no one will be able to create an issue (the button will not be available) if the summary field is empty (the case if the field is hidden).

You could try updating the summary field after the issue creation, but it can't be empty on issue creation.

Its not that the value is empty, its filled with a predetermined value as part of hiding the field. 

During the automation creation process, I can choose to then replace the predetermined value based on the issue meeting the criteria. I've tested and proven that this is possible however I cannot find the correct way of making the automation use the value selected in the custom field to fill the value of the summary, 

Suggest an answer

Log in or Sign up to answer

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