nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I auto-create a Jira issue from another issue when its status changes and copy required fields?

Phương Hoàng Thị Mai

Specifically, I want to automatically create Issue A when another issue (Issue transitions to Status C on Jira DC. During the creation of Issue A, the automation should copy data from Issue B into Issue A.

I’m currently using ScriptRunner to handle the logic. However, the automation creates Issue A first and only then populates the fields. Some of those fields are required, so Jira blocks the issue creation before the values can be copied over.

Is there a way to populate required fields at creation time (or otherwise work around this limitation) so that the issue can be created successfully?

Accepted answers

All comments

Bảo Phạm Gia

You must use IssueInputParameters to collect all the data (including required fields) in one place before calling the create command.

Do not create the issue first and then try to set the values, as this will fail Jira's validation checks

Izabela França

Hello @Phương Hoàng Thị Mai ,

You could use a Jira automation to achieve this.

The key point is that, in the clone work item action, you must select all fields that are required for issue creation and ensure they are copied from the original issue.

Here is an example:

Would Jira automation work for you?

Phương Hoàng Thị Mai

Unfortunately, I’m currently using Jira Data Center, so I’m not sure whether your instructions apply. Is there any workaround or alternative approach for Jira DC?

Tinker Fadoua

@Phương Hoàng Thị Mai

What is the relation between issue A and issue B? (Parent/Child)

Little bit elaboration will help.

Best,

Fadoua

Phương Hoàng Thị Mai

The relation between issue A and B is "Created by".

Izabela França

Hello @Phương Hoàng Thị Mai ,

I believe it is also possible to use this action in automations for Jira Data Center. Here is a link to an offical Atlassian document about cloning issues in Data Center.

Clara Belin-Brosseau_Elevatic

Hi @Phương Hoàng Thị Mai

As an alternative to ScriptRunner, I can suggest trying our app Elements Copy & Sync. It will create the target issue and injects field values in the same operation, instead of “creating first, updating later”.

These are the steps you should follow to configure the app:

Create an Operation that creates Issue A

Go to Administration → Manage apps → Elements Copy & Sync → Operations
Click Add operation
Choose Create a local issue
Configure:
- Target project (where Issue A will be created)
- Target issue type (Issue A type)

Configure field copy (this is where required fields are solved)

In the same operation, configure the Fields section:

Copy values from Issue B → Issue A for all required fields
(Summary, Description, Priority, custom required fields, etc.)
For required fields that should not be copied, set:
- A static/default value, or
- A value based on another field

Trigger the operation on the workflow transition to Status C

Edit the workflow used by Issue B
On the transition that moves Issue B to Status C, add a Post-function
Select Elements Copy & Sync: Create and link issue
Choose the operation you created
Publish the workflow

You can find all the detailed steps here in the documentation.

Let me know if you have any question.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center