Create subtask screen not auto coping the scope cateogry field (custom field) from the parent issue

[Thinesh]

Problem : I want to auto copy the custom field (scope category );

1. from backlog to all the subtaks created under that backlog.

2. All the bugs to have the scope category from the parent linked backlog

This rule works fine, if the scope category field is a non-mandatory field. After the issue creation the scope category field from backlog gets auto populated in the scope category.

But If I make this field as mandatory, then during subtask creation the scope category values from the parent backlog is not getting auto populated (need to manually select which I don't want my users to do) thus I am not able to create a subtask.

Please provide suggestion on how to achieve this use case

[Trudy Claspill]

Hello @Thinesh 

Welcome to the Atlassian community!

An Automation Rule cannot be used to populate a field in a Create screen. There is not a native capability in Jira for populating a field in the Create screen by copying a value from a parent issue.

Are you open to using a third party app to achieve this?

[Thinesh]

Yes I am open to using third apps. Are they payable?

[Trudy Claspill]

When you say that you don't want your users to select the value manually when they create a subtask, do you mean...

1. You never want them to set the field manually, or

2. You want the field set automatically and you want to allow the user to manually override the value?

If you never want to allow the user to manually change the value of this field, you should not make the field mandatory, and not include it on the Create or Edit screens. Simply have the Automation Rule set the value after the subtask is created.

For third party apps, the only one I had experience with for this type of scenario is Adaptavist ScriptRunner, using its Behaviors feature. Unfortunately, that was in the Jira Server/Data Center hosted product. ScriptRunner has recently incorporated some basic Behaviors options to support Jira Cloud, but per this page they don't currently support Behaviors for custom fields.