Post function to copy Original Issue-key to custom field when moving between projects is not working

[Valdis Mezdreis]

HI Community

I need to capture the original Issue Key (in a custom field when moving the ticket from a general project to a specific project (that is used to standardise a more detailed workflow that is part of the overall end to end workflow)

Think of it Moving from Dept A's workflow that has X steps (at some point midway through that workflow)  into Dept V's workflow that has Y steps, and once completed Dept B's workflow, move it moves back to Dept A's workflow to complete the rest of Dept A's workflow and close the end to end process

Reason why we want to do this is that we have Depts A through L all which have  slightly different workflow steps but must go through the Dept V workflow and it is simpler to have that stand alone rather than embedded in each of Depts A to L's workflows

So I don't break Dept A-L's dashboard views, i want to capture the Dept A-L original issue Key - say DPTA-254 into a custom field (and they can update the filters behind their dashboard to search for this)

When Moving the issue from Dept A-L to Dept V it will only ever go into the first step into Dept V's workflow (Follows the "create" transition step)

I've tried 2 options

Option 1

Use Copy Value From Other Field post function

I set it to copying source field "Key" to destination field  Original JIRA Key (my custom field which is a text field) 

Option 2

Use Update issue Custom Field post function

I set it to The value "%{00015}" will be appended to field Original JIRA Key, or set if it is a multi field. I researched that 

Neither worked

Any thoughts or suggestions?

[Bastian Stehmann]

Hi @Valdis Mezdreis,

I don't think that s post-function will work here, as this is not a transition but a move.

So maybe a listener (can be created with script runner for example) that is triggered by the move event might work, but I never tried this before. 

[Nic Brough -Adaptavist-]

@Bastian Stehmannis absolutely right.  A move is not a transition, so a post-function simply won't happen.  There's nowhere for it to be placed. 

A listener can catch an "issue moved" event.

I have to say though, any process that uses "move issue" is broken - it's the wrong approach when you're using Jira.  Move is for "mistake where user chose wrong project/type on create" and for housekeeping or re-organisations.  If it's part of your "process", don't try to fix it with code, fix the process properly.