Forums

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

field obligated

Ivan Andrieiev
Contributor
April 27, 2023

can I make a field obligated in one project project only for two of the three types of tasks, so that this field is not obligated in the rest of the projects?

1 answer

1 accepted

4 votes
Answer accepted
Fabio Racobaldo _Catworkx_
Community Champion
April 27, 2023

Hi  @Ivan Andrieiev ,

yes, you can. You need to setup a specific field configuration (https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/) and associate it with one or more issue types within a Field Configuration scheme (https://support.atlassian.com/jira-cloud-administration/docs/configure-a-field-configuration-scheme/). Field configuration Scheme needs to be associated to your project.

Hope this helps,

Fabio

Ivan Andrieiev
Contributor
April 27, 2023

@Fabio Racobaldo _Catworkx_  Hi

yes, but this field is visible in other screens, won't it affect other projects?

Fabio Racobaldo _Catworkx_
Community Champion
April 27, 2023

Hey @Ivan Andrieiev , you need to create a specific Field Configuration Scheme/Field Configuration for your project. Field will be mandatory just for project associated to that Field Configuration Scheme.

Ivan Andrieiev
Contributor
April 27, 2023

@Fabio Racobaldo _Catworkx_  It works, thanks for your help.

Like # people like this
Fabio Racobaldo _Catworkx_
Community Champion
April 27, 2023

you're welcome @Ivan Andrieiev . Please accept my answer ;)

Suggest an answer

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

Atlassian Community Events