I want my issue type with custom fields (without jira default fields like Summary, etc.)
HI @Kateryna Holub
There are limited options to work without standard fields as some like Summary are intrinsically mandatory
If you create your own field configuration for your issue type you will be able to hide a number of the other standard fields.
Hi @Tom Lister
Is it also possible to make fields like "Attachments" a mandatory? Right now, in my project, we see some people filling a bug report without much "Description" no "Attachments" and I want to make it a mandatory to file a bug.
Could you please help if there is a way to do it?
Thanks,
Siva
Hi
You can't make attachments field mandatory in the field configuration.
You could add a workflow condition to check number of attachments > 0
Do you use any add-ons like scriptrunner etc.
e.g.
Scriptrunner standard scripted condition
import com.atlassian.jira.component.ComponentAccessorComponentAccessor.attachmentManager.getAttachments(issue).size() >= 1
@Siva Garjala
1. Go to "Jira Settings"
2. Go to "Issues"
3. Go to "Fields Configuration"
4. Click on "Default Fields Configuration" link (or where you want to apply this fields)
5. System opens "View Field Configuration" page
6. In the actions section next to your field choose "required"
@Tom Lister
Also could you help me with the next issue:
I want to customize fields for my issue type. For this:
1. I created new issue type
2. Created new field configuration and hide all field that I don't want to see in this issue
3. Created new field configuration scheme and associate it with my issue type
BUT
when I open my issue ticket - I see all fields that I've hidden before
What is the reason?
Is your field configuration scheme associated with your project?
You can amend the field configuration scheme currently associated with your project and add your issue/field config mapping there.
@Tom ListerWhere I can associate the new field configuration scheme to your project?
you will need to go to the administration/ projects menu and select your project
there will be a section for the field configuration scheme being used. You can either replace with yours or update current scheme with your new issue mapping.
It looks like you're new here. Sign in or register to get started.