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; } } }

Is it possible to auto-create a JIRA ticket for a a different project based on a label ?

Anthony Martinez_dqmxly

I setup workflow builder in Slack which prompts the user to fill out a form then populates and creates a JIRA ticket based on the users responses.

I need to be able to open up a new JIRA ticket in a different project depending on the answer to the question in the form. Example "Is there customer impact?" if they answer yes then this will insert a label into JIRA project A as "customer-impact".

The question I have is:

Is it possible to implement some rule where JIRA will auto create a JIRA ticket in Project B based on a label that is present in project A for example if "customer-impact" label is in project A ?

Accepted answers

All comments

Bill Sheboy

Hi @Anthony Martinez

Yes, you can do that with an automation for Jira rule, triggered on the issue create in "project A" and checking the labels before creating another issue in "project B".

To get you started on creating your rule, please review this documentation and examples:

Kind regards,
Bill

Trudy P Claspill

Yes, this should be possible.

Is the "customer-impact" label added to the Project A issue only when the issue is created, or might it be added at other times?

If the label is added at another time, would you still want the issue in project B created?

Do you want the issues to be linked?

What action do you want taken with regard to the issue in project B if the "customer-impact" label is removed from the issue in project A?

Here is a partial example

Screen Shot 2022-12-28 at 3.33.23 PM.png

Ste Wright

Hi @Anthony Martinez

Yes, you can do this.

You can either...

Create this as a multi-Project / Global rule, if it is applicable to more than one "Project A"
Create this as a single-Project rule within Project A (assuming the same Project type)

---

The rule will look something like this:

Trigger: Field Value Changed
- Field to Monitor = Labels
- Change Type = Value Added
- For = Create Issue
Condition 1: Issue Fields Condition
- Field = Project
- Condition = equals
- Value = Project A
Condition 2: Issue Field Condition
- Field = Labels
- Condition = contains any of
- Value = customer-impact
Action: Create Issue
- Project = Project B
- ...populate other details

---

A few notes:

Trigger: I've limited it to the "Create Issue" operation in "For" - but it could be for all operations, or include "Edit Issue", etc
Condition 1: This is only needed if it's a multi-Project/Global rule. If it's a single-Project rule, it's not needed
Action:
- I've used the "Create Issue" Action - but if much of the information is the same in the new Issue, you could also use "Clone Issue"
- I find Smart Values useful when creating a new Issue - for example, you could reference Project A's Summary using {{triggerissue.Summary}}
- You could also link back to the original Issue if needed - search for the "Linked Issues" field in the Action

---

Let us know if there's more specifics you'd like to include in the rule, and if you need help to clarify how to include them

Ste

Bill Sheboy

Hi @Ste Wright

Just an FYI that rules like this no longer need to be global/multi-project scope.

The clone and issue create actions allow creating issues in other projects from a project scope rule. The one limitation is going to/from company-managed to team-managed projects...due to the issue type and field changes.

Kind regards,
Bill

Ste Wright

Learn something new everyday, thanks @Bill Sheboy !

I've updated my original answer.

Ste

Audrey Engstrand

Why cant I clone an issue from a project management project to a service management project?

Screenshot 2023-12-21 141245.png

Trudy P Claspill

Hello @Audrey Engstrand

Welcome to the Atlassian community.

Your question is not the same as he original question. Please start a new Question to get your question seen by more members of the community.

In addition to showing us your automation rule, please explain what is happening that results in you concluding that you can't clone an issue from a project management project to a service management project. Is there an error message when the rule runs? Show us the details of the rule Audit Log for an execution of the rule.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

label