Allow components to be manually set for created (destination) issue as part of a Workflow transition

[Paul Seekins]

Hello,

So I have a scenario where we are escalating an issue via workflow validators and post functions. Basically the post functions create a new issue (in a different project) and then set certain field values in the destination issue. This all works great, but I need to force a screen pop that will allow the user that invoked the workflow transition to be able to manually select a component (system field) value from the destination project. I can get the components field to pop, but it displays the values from the originating project and not destination (which are different).

Any ideas? Cannot find a solution after searching for many hours.

[David Friedrich]

Hi @Paul Seekins , this is a tricky one. Currently, I can only recommend displaying a custom list field in the pop-up that contains the same values as the components in the target project. During creation, this value is then copied to the component field, either by workflow or by automation rule.

Let me do some more research. There may be an app solution to avoid having to adapt your list field to the components of the target project again and again. I'm thinking primarily of smart fields or dynamic custom fields.

[David Friedrich]

Maybe Scriptrunner > Scripted Fields is a way to have the values set dynamically:
https://docs.adaptavist.com/sr4jc/latest/features/scripted-fields

[Paul Seekins]

@David Friedrich thanks for the quick response. I have used Scripted Fields before, but the challenge is still forcing the field to appear in a transition screen as an editable field in the destination project. To your earlier point, I really don't want to create another custom field that mirrors the components field in the linked (destination) issue. Also to clarify, the component in the source issue (project) would not be completed prior to invoking the transition step.