Configuring fields for a new issue type

Question

Hi,

I created a new issue type for an existing project that will require a different workflow and different set of fields from the other issues. But I am still having trouble with fields appearing in the new issue type that I dont want there. Here the steps I took to do this:

1. Created the new issue type

2. Created the new workflow

3. Associated the new issue type with the workflow and added the new workflow to the projects current workflow scheme

4. Created new screens and screen schemes

5. Associated the new screens and screen schemes to the issue type

6. Created new field configuration  and added new field configuration to the projects current field configuration scheme

Here is where I am running into the issue, a field called Summary is not shown when I go to create the a ticket using the new issue type but it keeps saying its required in order for the ticket to be created. I dont want this field to be a part of the ticket, however, when i go to the new field configuration I see that it is already marked as required and there is no option to make it optional.

Any help would be much appreciated.

Thanks,

Lina

Lina Abu-Baker · Answer

@Sam Nadarajan Thanks for the response! So we currently use the Description field instead of the Summary field and always thought that was a system field and not a customized one. I actually have never seen the Summary field on any other issue types when creating a ticket so I am wondering if the workaround for having a set value is already in place and I wasnt aware. I will have to check!

Sam Nadarajan · Answer

Hello Lina,

The summary field is required for all issues in Jira, and there is no workaround to make this optional as this is a system field.

The link above provides a workaround that will automatically set a default value for the summary even if it does not appear on your new issue type, however this would set a default value for the summary field across all issue types. I don't recommend using custom javascript to set this field value behind the scenes. I do recommend using the summary field in your new issue type.

I know it seems like a limitation and frustration point for your new issue type to require adding a value to a field that doesn't tell you anything about the new issue type, but do you have any other fields in your new issue type that closely resemble the summary field? For example, I created a new issue type of "Candidate" for a Jira project and decided to use the "Summary" field to store the full name of the candidate. It took a little bit of education and communication but the team using the project now is used to this standard.

Hope this helps