Why the field Summary is "required"?

[Raph NOno]

Hello,

When I'm in a field configuration, the summary field is always "required" and can't be changed.

May somebody explain me why ?

That involves another problem : when I hide it from a screen, for exemple a creation screen, the creation can't be done because this field is required.

Thank you in advance.

[Callum Carlile _Automation Consultants_ · Accepted solution]

@Raph NOno The Summary of an issue is the issue's name. An issue can not be created with a blank name, so that's why this field is required for all issues

[Raph NOno]

Thx for this answer !

Indeed I didn't noticed that "Summary" was in fact the name, now I'm wondering why they didn't name it "Issue Name" or somthing like that, more obvious I mean.

[Nic Brough -Adaptavist-]

Because for many types of issue (and process), "name" is the wrong word.  As is "title".  Bugs, Incidents, Changes etc - name or title are the wrong words for what the field does.

Summary is probably the most generic thing they could have chosen.

[Raph NOno]

Yes thanks I can see that now.

[simarpreet singh · Accepted solution]

Hi @Raph NOno -

'Summary' is a jira system field and is set Required by default. You cannot make it optional and SHOULD NOT make it optional either way. It's a source of truth for all the jira tickets. It signifies your moto or thought behind the ticket and also keeps a record of changes happening in ticket based on it.

There may be some javascript code available, but again it's a really bad design of making summary optional.

Thanks and keep posting,

Simar

[John Funk]

Hi Raph - Welcome to the Atlassian Community!

I echo the previous couple of answers. However, I am curious why you would want to hide the field? What is it that you are trying to accomplish?

[Raph NOno]

Thx for the answer, all things said in the first comment :)