Jira Support Request

[bianca_meze]

Hello,

I’m working with two Jira projects:

• CLIENT – each issue represents a client, with various custom fields (specific to this project)

• ACCOUNTING – every month, on the 1st, we start work for each client

Here’s what I want to automate:

1. On the 1st of each month, automatically create a new issue in ACCOUNTING for each client (each issue from CLIENT).

   • The new issue should copy all custom field values from the CLIENT issue.

   • The new issue should be linked to the CLIENT issue (e.g., "is related to").

2. If I modify a custom field in the ACCOUNTING issue later on, the CLIENT issue should be updated accordingly.

My questions:

• Do the custom fields have to be global in order to be copied/synced between projects?

• How can I configure an automation that:

  • Runs monthly on a specific date (not triggered by status changes),

  • Selects all issues from the CLIENT project,

  • Creates linked issues in ACCOUNTING,

  • Copies all custom field values (automatically, not one by one)?

• How can I ensure that any future changes made in ACCOUNTING custom fields will automatically sync back to the corresponding CLIENT issue?

Please let me know the exact steps to implement this (or if I need to use any marketplace apps).

Thank you!

[Trudy Claspill · Accepted solution]

Hello @bianca_meze 

Welcome to the Atlassian community.

You can find the documentation for the native Automation Rules feature here:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

You can also find free, on-demand training on the feature in the Atlassian Learning area available from the Learning link at the top of the Community pages.

What is the Project Type of each project? To get that information go to the View All Projects page under the Projects menu. Find your projects in the list. What does it say in the Type column for each project?

Looking at the components of an Automation Rule:

You can use the Scheduled trigger to have a rule run automatically on a schedule you define.

You can include in that trigger a JQL filter that will select the issues against which the remaining actions of the rule will run. 

You would use the Create Work Item action to create your new issue in the Accounting project for each issue in the Client project selected by the JQL you specified in the rule trigger.

In the Create Work Item action you can set the fields in the new issue. For many fields, but possibly not all, you can select the field from the "Choose fields to set" list, and you will find a built-in option to set the field by copying the value from another field. And you can specify that the data should be copied from the issues selected by the trigger. Some fields may not be available to set that way. There is an alternate way to set fields using JSON code if necessary.

In the action you can also select the Linked Issues field which will enable you to link the new issue to a specified issues. Here also you can specify the issues selected by the rule trigger.

You would need at least one, and possibly multiple rules, to detect changes to the field in the Accounting project and update the issues in the Client project. These rules have to be rules where the Project Scope on the Rule Details page is set to Multiple Projects, and you will have to specify both the Accounting project and the Client Project.

I have not given you the exact steps to create the rules because I'm hoping that you are motivated to learn how to create such rules. I'm hoping you will take the information I've provided and try to create the rules, and ask us questions if you have difficulty.

[bianca_meze]

Thank you so much, I managed to do it.

[Trudy Claspill]

That is AWESOME! Good job!