Forums

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

Making a field required for Story makes it required for Sub-task as well which is not wanted

laura iacob October 16, 2020

Making a field required for Story makes it required for Sub-task as well. In my project's Field Configuration Scheme I have 2 field configurations: a Default Field configuration where my field is not required - this is for all unmapped issuetypes where Sub-task is included. The second Field configuration is associated with Story and it has my field required. What am I doing wrong? Thank you!

1 answer

1 accepted

1 vote
Answer accepted
Callum Carlile _Automation Consultants_
Community Champion
October 16, 2020

@laura iacob Some things to check:

  • Are both field configurations correctly mapped to the issue types in a Field Configuration Scheme?
  • Is this field configuration scheme definitely mapped to the project you are using? (You can see this by going to your project settings > Fields, which will tell you the field configuration scheme that the project is using as well as the field configuration/issue type mappings within this scheme)
laura iacob October 19, 2020

I have made some screenshots.

In Project settings I can see my field configuration scheme. I will call the second field configuration (the one I painted over) Blue Field Configuration:

project settings scheme.png

When I click on Country required Field Configuration Scheme I get the 2 configurations and their mapped issue types:

field configurations in scheme.png

When I expand the Default Field Configuration

Default Field Configuration.png

Scroll down to Country, I can see Country is not required:

Country not required.png

When I expand the Blue Field Configuration

Blue Field Configuration.png

Scroll down to Country, I can see Country is required:

Country required.png

Does this raise you any flag?

 

Thank you so much

laura iacob October 19, 2020

I managed to figure it out. When I try to create a Story, the Country field is marked with asterisk while on creating a Sub-task it's not and it's requested only when I try to submit it. It was about validators in the Create transition which I didn't know about

Niels Juel
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!
May 5, 2022

Hi Laura

I'm having the same problem, with required field on Story, that also becomes required on Sub-Task. 
Could you tell what it was in the Transition you find out ?

Thanks

Suggest an answer

Log in or Sign up to answer