Set value in transitionscreen for postfunction-created subtask

[Fred Massner]

Hi guys, 

with the help of a transition I am creating a sub-task as a child of a story. 

Is there any way to ask the user in the transition-screen for an input of a specific custom-field which should be transfered to the created sub-task WITHOUT changing the values of the same custom-filed which is used in the story?

So this is what i am trying to do:
--> Transition in Story --> set value of custom field in transition-screen for the sub-task --> create sub-task --> don't change the previous set values for the same custom field in the story (parent of sub-task)

Problem: 
with my solutions so far I'm always changing the values of the story...

Thanks a lot for your help!

[JimmyVanAU]

Hi Fred,

Welcome to the community. To solve your predicament, what I typically recommend is to create a new custom field. Give it an appropriately transit name.

Say your custom field is called "Business value ($)", I'd call the new custom field "Business value for sub-task ($)". Then in your transition screen, add the "Business value for sub-task ($)" custom field, and then use this value to create your sub-task.

As you have found, the transition screen always attempts to update the value for the issue it belongs to, so you can either calculate it (if possible), or use an entirely different field.

Cheers, Jimmy

[Fred Massner]

Hi Jimmy,

thanks for your quick answer. Unfortunatly we can't use another custom field. We have pretty complexe Worflows with different stakholders, all using this custom field in different issue types. There it needs to be the same (same name and same ID).
Otherwise your suggestion would have been the solution. 

Any other thoughts/workarounds maybe? 

Best
Fred

[JimmyVanAU]

Hi Fred,

Interesting predicament. Not sure why anyone other than an admin cares what ID it is. Unfortunately (or maybe fortunately), you can have the same custom field name multiple times. Maybe add a custom field of the same name (but new ID), and then do the creation magic with the new custom field ID? This does have some downsides in creating filters, updating screens etc, so be very careful.

Otherwise, can you tell me more about how you're creating the issue?

The question is tagged unknown hosting, so I'm not sure if you're using Cloud or Server.

If you're using Cloud, then you will have Automation for Jira, and some wizardry can be performed (but I'd probably still push for this transient custom field). If Automation for Jira is available, then update the field in transition, create the task, then try to change the field value back.

If you're using Server/Data Center, then you'll be using an add-on, but I'm not sure which - Automation, Scriptrunner, JMWE, or something else entirely. Some of these will have the ability to tackle the approach similarly - create the sub-task, and then edit the issue.

Cheers, Jimmy