Copying values in custom fields

[Dmitry Alabyan]

Greetings, community!
following up on

https://community.atlassian.com/t5/Jira-Service-Management/Re-Linked-Issue-Update-Automation/qaq-p/2659024/comment-id/165914#M165914

I am interested whether one can copy values from one project to another via a specific automation. Rough idea - to trigger a bulk edit (further refine this as a regular update).
Given:
we have a Work Management project, where we use issues as dossiers for marketing campaigns, with automated calculations of CPC, publisher costs, revenues, etc.
also with a margin field.
this project is also synced with a kanban board where we keep track of our invoicing. aka when a dossier is created and filled > respective invoice task is created in the kanban board, carrying over the numbers.
Problem:
sometimes dossiers get updated after creation.
so I need an automation that would update certain fields for linked issues (here, invoice issues are alway linked through causes/caused by).
How could that be implemented, if at all?
a sketch of my automation rule encolsed:

[Rebekka Heilmann (viadee)]

Rather than doing a "Lookup issue" you can insert the JQL search directly in your trigger. The option for that is quite far down when you edit the Scheduled trigger.

However just listening to a field change/issue update like @Gerusa Lobo _e-Core_ suggested in his last screenshot would probably work even better?

Which part of the rule isn't working as of yet?

[Dmitry Alabyan]

yes, lookup is just for this one-case of a bulk migration.

problem is - there can be multiple field changes, I would need to account for a general "anything changed in the issue" then.

when the rule is run manually for one issue - no problem. when you scale it up to be scheduled (and try for testing to run it) - no actions performed. Although the JQL query is validated and correct

[Dmitry Alabyan]

@Rebekka Heilmann _viadee_ any further suggestions?

[Rebekka Heilmann (viadee)]

Have you tried the "issue updated" trigger then or do you want to listen to specific fields?

You could either have the same rule for multiple fields and use the "Field changed" trigger in all those rules, otherwise the Scheduled rule limited by a JQL search is the way to go.

So what you're saying is, that the JQL does find issues but no actions are performed on these issues?

How does your rule look like now and what does the Log say?

[Gerusa Lobo _e-Core_]

Hello @Dmitry Alabyan

At first you can develop a manual trigger to check if the rule is ok, as in bellow:

It is important to configure the scope for both projects.

To have a periodic processing, we can use something like this:

Also, to have a automatic updated, keeping all issue synchronized, you can use, something like this:

I hope help you.

[Dmitry Alabyan]

as said, yes, that would be the way to pursue, yet when scaling it (step2 as you described) up to be a scheduled rule - I get no actions performed. Although the JQL query is validated and correct.

[Gerusa Lobo _e-Core_]

Hi @Dmitry Alabyan,

The both projects must be in the automation scope to be able edit an issue in the second one.

You could verify it.

Also, if it is ok, the problem could be any permission for the automation actor or issue security.

I help hope you.

[Dmitry Alabyan]

yes, both projects are in the scope. moreover, automation actor is me, II have all-access admin account.
and it works on and individual level (manual trigger) without problems.
somehow specifically scheduled bulk idea does ot

[Gerusa Lobo _e-Core_]

Hi @Dmitry Alabyan,

For schedule, In automation I defined the jql inside the schedule parameters.

Using that way, the automation works as a loop for all issues searched in jql.

Please, Look at the second automation image configuration in my previously post.

[Dmitry Alabyan]

did exactly in the same manner, I'm familiar with scheduled looping