Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Summary field - autofill or remove

Using JiraCore Cloud is there a way to have the Summary field either:

  1. Not appear at all?
  2. Or autopopulate with pre-defined values?

We do not desire to users enter values here, as we need them to be consistent, and will have required fields that need to be entered into a specific format.

The Summary field being freeform is not ideal for the set-up we would like to create.

Thanks for your help!

3 answers

We've done something similar for Description (no idea why, but that's another convo). Our solve was to create a 'tab' in the screen config and put anything we don't want to have readily visible on that 'tab'. 

You don't want to remove it from summaries even if you could because it's a required field and any third-party plugins/integrations you end up using (maybe not now, but perhaps later on) won't be able to create or manage issues without it.

0 votes
M Amine Community Leader Apr 19, 2018

Hi Bridget,

I can suggest a workaround. 

Since you cannot remove/hide the summary field, you can use a post-function in your workflow to set a default value. Besides, you can add a description to the summary in order to inform your user that the summary will be overwritten. 

Hope it helps. 





I have this issue, the Summary field is required and has no user facing purpose. 


We either need to autofill this filed or autofill and hide this field.  We are using Jira cloud and the script in the description field does not work.  (am assuming this fix is for Jira server) 

Can anyone help with this obvious Jira usability issue ? 

Running into the same issue as well.  Seems strange to even have this requirement, as the point of service desk is to give a portal for users to enter values we require.  Why Atlassian would assume that means "write a block of text saying whatever you want" as a default required field seems out of sorts.


Going to have to investigate workarounds to keep this from our users.

Hi ,

My solution:

I leave the Summary field visible on the creation screen.

In the schema fields corresponding to the type of incident, I set the value in the description of the Summary field below code:

<script type="text/javascript">
if (document.getElementById("summary").value == "") {
document.getElementById("summary").value = "Auto Completed by the System, fill in the fields below requested.";}

Then the user in the creation screen appears the field with the preset message.

Then in the post function I fill it with data from the registration form plus the creation date if desired.

it work on Jira Server 9.x.

I discovered when I use the javascript solution mentioned here, it disables the inline editing for the project, so I need to go back to the drawing board to figure out a better way to auto-populate the Summary field. :|

0 votes

Hi @Bridget Annear and welcome to the Community!

The Summary field is one of the core required fields in Jira. Yet, you are not the first one to ask this question. I have not tried it myself.

You should take a look at the answers to this old question: Hide Summary Field and Populate During Ticket Creation.

Thanks @Sebastien Jacques, I did some searching through the forums and tried the following: 

I am unable to set Summary Field default value

Summary field required

Unfortunately neither gave the results we were hoping for, so I wonder if it's a limitation to JiraCore Cloud? vs JiraCore Server/Jira, etc?


It also appears the link that you supplied may just be for Jira rather than JiraCore?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,085 views 18 32
Read article

Atlassian Community Events