Making some fields mandatory only for the bug creation screen

Özge Özgenç March 11, 2024

Hello all,

I have a project. I have different issue types such as task, subtask, test request, bug etc. This project only has one workflow for all issue types. 

I want to make some fields "required" on the "BUG" type issue creation screen.

I don't want to affect other issue types or workflow. I don't prefer adding a validator to the workflow because other issue types share the same workflow and I don't want to create another workflow.

Could anyone please explain how to do it step by step? 

1 answer

1 accepted

2 votes
Answer accepted
Joe Pitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2024

Can I have Different Required Fields for Different Issue Types?

Yes, as long as it is a different issue type. Required fields, at creation time are controlled by the field configuration scheme. That scheme is composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme.  Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events