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!
@laura iacob Some things to check:
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:
When I click on Country required Field Configuration Scheme I get the 2 configurations and their mapped issue types:
When I expand the Default Field Configuration
Scroll down to Country, I can see Country is not required:
When I expand the Blue Field Configuration
Scroll down to Country, I can see Country is required:
Does this raise you any flag?
Thank you so much
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.