The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Problem with field configuration

t.tsikolia
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2019

I added custom field to my project "Acceptance criteria", it's just simple text field. Action for this field is required. Default issue type is "Task" on which added field is visible and required, as it should be. But if I make "Bug" issue(which is part of the same project) custom field is not visible, but is somehow required. I am not sure if my configuration is correct or it's some other issue with Jira.

I don't need "Acceptance criteria" field on "Bug" issue at all. 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
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 Champions.
June 3, 2019

Take the field configuration you created and copy it.  Go into the copy and make the "acceptance criteria" optional.

Now create a new field configuration scheme and add both of the field configurations to it - using the new one for bugs (and other issue types that should not have the criteria field)

Associate the new field configuration scheme with the project.