Yes. Required fields, at creation time are controlled by the field configuration scheme. That scheme is composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme. Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html
It makes complete sense the way you say it, but it just won't work for me. This is what I have now:
Default field configuration scheme configured with:
- Default -> Default Field Configuration
- Sub-task -> Sub-Task Field Configuration
Default Field Configuration configured with:
- Description -> Required
Sub-Task Field Configuration configured with:
- Description -> Optional
The Description is required whenever I create a story, bug or epic. However, when I create a sub-task for a story, a modal pops up and tells me the description is required.
Nothing happens if I reverse it and change Description to required in the Sub-Task Field Configuration.
It seems like the sub-task is not recognized as a sub-task.
Hi @Jess Froholdt Stopa ,
Please, add a validator to that specific workflow and this workflow should not be used for sub-task issue type.
Create a two field configuration and add one field configuration to all issue types except sub-task and make the description as required and add another one to a sub-task issue type.
Kishore Kumar Gangavath.