Can we get that automation setup for the following? or any better approach would be appriciated * A manual action in Jira for IHD items called "Move to Dev Hub Production Support" * It migrates the item from IHD to DH * It puts the item on the currently active sprint (Q2 Sprint 1) * It maps the team to the Production Support Team * It maps the status accordingly: * To Do = To Do * In Progress = In Progress * Waiting On Vendor/Shipping = On Hold * Cancelled = Cancelled * Done = Done * The assignee on the ticket remains * An automated email is triggered to the requestor saying "The Helpdesk request you entered for {{issue title}} has been identified as a Production Support item and been migrated to the Development Hub project. You can now see this item at {{link with issue number}}. Thank You" Am not able to create above rule in jira.

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

Automation rule for the below details

Ayush Lawania_c3cygh

Can we get that automation setup for the following? or any better approach would be appriciated

A manual action in Jira for IHD items called "Move to Dev Hub Production Support"
It migrates the item from IHD to DH
It puts the item on the currently active sprint (Q2 Sprint 1)
It maps the team to the Production Support Team
It maps the status accordingly:
- To Do = To Do
- In Progress = In Progress
- Waiting On Vendor/Shipping = On Hold
- Cancelled = Cancelled
- Done = Done
The assignee on the ticket remains
An automated email is triggered to the requestor saying "The Helpdesk request you entered for {{issue title}} has been identified as a Production Support item and been migrated to the Development Hub project. You can now see this item at {{link with issue number}}. Thank You"

Am not able to create above rule in jira.

Accepted answers

John Funk

Hi Ayush - Can you post a screenshot of the actual rule that you have so far. And then what is not working with it?

All comments

Trudy P Claspill

Hello @Ayush Lawania

Are IHD and DH projects or work items types within the same project?

If projects, what types of projects?

Company Managed or Team Managed?
Software, Service Management, or Business?

Automation Rules do not currently have a Move Work Item action because moving work items can be complex. The destination project/work item type may have different required fields, different permissions, different workflows, etc. Generally the work around is to instead clone the work item, link it to the original, and then "close" the original.

What is the root problem you are trying to solve by moving the work item? Can the problem be solved by using the work around of clone/link/close?

Ayush Lawania_c3cygh

IHD is a service desk project and DH is a software project and yes cloning would work but how to clone the issue with same assignee and how to map statuses?

Trudy P Claspill

Are the projects Company Managed or Team Managed?

Is the Assignee in the source project a user that has the Assignable User permission in the destination project? Does that Assignee have access to the destination project and permission to work with work items in that project?

Are there any conditions, rules, or transition screens in the workflow for the work item created in the destination project?

Are you familiar with Automation Rules functionality?

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

There is also a free, on-demand course on Automation available through the Atlassian Community Learning:

https://community.atlassian.com/learning/course/streamline-software-projects-with-jira-automation-and-integrations

Ayush Lawania_c3cygh

All are company managed projects and none have transition or any kinda rule.

Can you provide me the automation steps for this?

John Funk

Hi Ayush - Can you post a screenshot of the actual rule that you have so far. And then what is not working with it?

Ayush Lawania_c3cygh

Screenshot 2025-04-15 203116.png

I am not able to send email notification as mentioned in the request and also the status mapping as mentioned above.

John Funk

Have you configured the Rule Details to be a Multi-project rule? You need to include the Project from the Manual trigger and the Project where the Story is getting created. Or it needs to be a Global rule. Let's start with that first.

Ayush Lawania_c3cygh

No this is not a global rule but yes in the create issue action I have added different project and this rule works though but am not sure how to do status mapping and email.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management