We updated a required custom field, replacing it with a select menu which is required. All has been fine with new issues.
We added sub-tasks to the project, something we didn't need previously due to the nature of the work. But one issue in the project is better served with sub-tasks.
While creating a sub-task (in an existing issue), we get "Original custom field is required" and it indicates that the original custom field is needed.
I can't find anything in the config that says the old field is needed anywhere. How can I get the sub-tasks to
* ignore the missing original field
* ignore the new field (it's included in the parent task, so redundant in the sub-tasks)
It looks like you will have to create a separate field configuration for the sub-task so that the field not mandatory. Most likely you have a field configuration that is used for both issue types right now.
Here is a video that explains all the details: https://www.youtube.com/watch?v=C3Lb1T4liGw&t=1s
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events