Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Make field Description mandatory for a project of type Escalation and issue type CustomerEscalation

Mouna Hammoudi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 25, 2023

I would like to make the description field required for the Escalation project and the issue type Customer escalation. How can I do this?

 

Capture.PNG

1 answer

1 accepted

1 vote
Answer accepted
Prerna Sony
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 25, 2023

Hello @Mouna Hammoudi ,

Welcome to Atlassian Community!

You can do that through creating a different Field Configuration for that project. 

Please refer this article for field configuration : Change a field configuration

So it works like this - 

You have a Field Configuration Scheme.

Then inside the Scheme you can have multiple Field Configurations - each attached to different issue types. In other words, you can make some fields mandatory for Tasks but not for Stories. 

Then you attach the Scheme to the project. 

So if you want Field Q to be mandatory on project ABC, then you would create a Field Configuration Scheme for project ABC. I like to abbreviate so something like Project ABC FCS (where FCS is Field Configuration Scheme). It would include an FC (field configuration) that has field Q as mandatory.

Then I would attach Project ABC FCS to project ABC.

I would leave the existing scheme on the other projects where it is not mandatory. 

Hope this helps !

Suggest an answer

Log in or Sign up to answer