Forums

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

"original custom field is required"

Bruce Fint
Contributor
April 30, 2021

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)

 

2 answers

1 vote
Fabian Lim
Community Champion
April 30, 2021

Hi Bruce,

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

Regards,

Fabian

0 votes
Vikrant Yadav
Community Champion
May 1, 2021

@Bruce Fint It seems that in Sub-task field configuration "Original" is set Required and field not avaialble on the create screen. Add field on sub-task issue screen or make field OPtional from sub-task field configuration. 

 

thanks,

Vikrant Yadav

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events