I have created two custom fields which are required for some projects.
Success - Able to create Epic and prompted for custom field values as expected.
Success - Able to create Story and prompted for custom field value as expected.
Error - Unable to create Sub-task, two fields require value as expected, but also getting this error which is preventing me from creating subtask.
-----------
Epic Link
A subtask cannot be assigned to an epic.
Choose an epic to assign this issue to.
-----------
I have not changed any Epic Link related requirements.
How can I make the two custom fields required and be able to create subtasks?
Current Workaround: I've implemented the logic to requiring custom fields on transition of creating an issue or when completing it, but this requires making the transition requirements for every transition, otherwise I risk fields not being populated all the time. Hoping to find an easier solution.
You need two field configurations - one for the top-level issues, the other for subtasks (with the field optional on the sub-task configuration)
This is helpful to know. I've implemented this and it solved the issue.
Only follow-up question now is that, using this approach, I cannot make make a field mandatory through field configuration at the sub-task level. I'd have to make it mandatory during transitions, is that correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No. You have separated out the field configurations so that issues and sub-tasks behave differently already. You can change the field configuration for sub-tasks to make a field mandatory.
This flag is for every step though. If a field is mandatory, you need to enter it on issue creation and you cannot blank it out at any point. If you want to do "field mandatory during a transition", you need to use "validators" in the workflow to say "must fill this in here"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- Hello. I bumped into the same issue. 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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing from what you've said. I would want to closely check that you really do have a field configuration scheme that says to use two separate field configurations for Story and Default, in this project.
I can't find a way to replicate this issue unless I'm sharing the field configurations across all issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Also, this seems to be a separate issue, not sure if it's connected, but when I try to create a Story, the Country field is marked with asterisk while on creating a Sub-task is not and it's requested only when I try to submit it
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 by searching why the asterisk is not displayed. 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.