Subtask creation updates custom fields for parent

[werner kolze]

Hi there,

on a workflow transition, we ask the user to make two decisions

  (all these decisions and fields are presented on a transition screen)

decision 1 - to create a subtask  - yes or no
decision 2 - ( if yes ) what type of subtask to create - subtask A or subtask B

furthermore the user can enter four different custom field values:

customfield 1 - customer

customfield 2 - contact

customfield 3 - category

customfield 4 - reference number

all works well, the subtask gets created, when the user enters yes, etc. all fields are entered in the subtask - all works well for the subtask.

The problem is that the parent also takes on the newly entered values for the four different custom fields !! 

But the parent issue may has different values and they should remain as they are - I do not understand how and why these values on the parent are changed.

I attempted this via groovy and also via the post function "Create subtask" (Create on Transition by Bob Swift) - same result, the parent issue does have the custom field values changed.

Thank you for all your help in advance

this is on Jira v 7.7.2 ( Server )
with Scriptrunner - 5.4.12

and Bob Swift Add-ons version 7.0.0

[Fazila Ashraf · Accepted solution]

Hi @werner kolze  

What you collect from the parent's transition screen is for the parent's fields. They are then passed on to the subtasks when the create subtask post function executes.

So it works by design.

For your use case, you could collect the values in the parent's transition screen on a different set of custom fields and then pass them through scripting to the subtask ticket. Make sure that you do not place the different set of cfs in the view screen of the parent. Hope this idea helps you to build the solution

[werner kolze]

Thank you @Fazila Ashraf , appreciated. It would be a good idea to do this as you described and suggested, but unfortunatley we are not in a position where we can create custom fields. Especially nFeed in my use case. I have to find another workaround then.

Interesting that a transition screen is updating the parent issue by design.

I accept this as an answer. Thanks again