Automation clone issue and move to different project

[Vanessa]

Here I am, once again.

Dear Community,

I have trouble starting an automation:

We would like that when a custom field (the custom field selects another assignee), is filled.

The issue should be cloned into that certain project of that assignee from the custom field.

Maybe someone has an idea on how to start it.

Thank you so much in advance!

All the best,

Vanessa

[Stefan Salzl · Accepted solution]

Hi @Vanessa once again ;)

I would suggest to start with a „Field value change“ (guess that‘s the name of it) trigger.

You could then add any condition (eg. if only should run for special issue type).

Then add a clone issue action. As far as I know int can be configured directly in the action to clone in a different project. (—> keep in mind to configure as multi-project rule in rule details)

Best
Stefan

[Vanessa]

Hey there Stefan!

Thank you again for your help.

The field value change I already managed, the action with 'clone issue' too.

Now where I am stuck is:

I would need the automation to check in what project the 'assignee 2' is and move the issue in that project of assignee 2.

Is that possible? Or is there something similar I can do?

Thank you! 

[Stefan Salzl]

mkay...I´m not sure if I got the requirement right so let´s take one step back:

entry point is

• a custom field is filled with a user name
  • is that field a user picker?
  • are ALL users of the jira instance available in that field?
• then there needs to be a verification in which project the user from step 1 is part of
  • can you be sure that each user could only be part of just 1 project?
  • if not:
    • which project should the automation rule clone the issue to?

As far as my knowledge reaches I´m afraid there is no such functionality within native A4J. There might be (no guarantee) any possibility to get this by API calls which would also mean development effort.

Best
Stefan  

[Vanessa]

Yes it is a user picker field and all users are available in that field.

Mhh maybe I have to think of a different approach.

I tried doing it like this now:

As soon as you choose a project in the custom field "project picker", the issue will be cloned and moved to that project.
I did this automation for the 5 projects I needed :) 

thank you for pointing me in the right direction!

[Stefan Salzl]

It´s my pleasure to be part of that journey to your approches. That looks really great 👌

One more hint: If you don´t want to have 5 different automation rules you could try solve this with a smart value within the clone action that will automatically take the value of the field to know where to clone the issue (see screenshot). 

Best
Stefan

[Vanessa]

Ahhh yes, that is even better.

I will change the automation :) 

Thank you so much!

All the best,

Vanessa