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

Automate moving tasks to another project

Taylor Chappell

I'm trying to move issues between projects because one team may complete their portion and need fulfillment from another team. Is there a way to use automation for that? I'm thinking of having a workflow for "In Progress -> Move -> TeamA/TeamB/TeamC" that will then reset the status to In Progress and the right team can work on it.

So far what I've done is started using labels to clone the tickets into other projects. Seems serviceable, but I think I'd like the comments to follow. Is there a way I can automate the moving of tickets? Or is cloning going to be my best bet if I don't want my teams to be too muddled with people having access to everything?

Accepted answers

Esther Strom

Hi, @Taylor Chappell - unfortunately there's not an automation action to move tickets to a different project. You can vote on and watch the ticket for this request in Atlassian's Jira instance.

In the meantime, cloning is the only way to do it. You can set up your rules to clone the comments from the original ticket into the cloned version. Here's how one of ours is set up.

All comments

Esther Strom

Hi, @Taylor Chappell - unfortunately there's not an automation action to move tickets to a different project. You can vote on and watch the ticket for this request in Atlassian's Jira instance.

In the meantime, cloning is the only way to do it. You can set up your rules to clone the comments from the original ticket into the cloned version. Here's how one of ours is set up.

Taylor Chappell

Thanks!

Taylor Chappell

This rule would go in the project of the new copied issue right? Not in the same automation as the copying? So then would it inherit the triggerIssue still in the new rule?

Esther Strom

Nope, ours is in the same automation, which is a global rule (because for us, we want it to be available to run on any project.) Your rule would need to live in the global automation section of the site even if it's only one origin project and one destination project, because that's still two projects (a project-level rule can only clone issues into the same project.)

Our rule, as shown above, is triggered when a ticket in any of our engineering projects is transitioned to Closed and has a resolution of Duplicate, Delete, or Canceled. When the issue matches those conditions, it clones it to the Trashcan project, copies all comments, and then deletes the original issue.

David Perez Martorell

Hello. I want to know how to start tickets task proj1task1 for exanole in project 1 and end it in project2. but i don't wont to duplicate the ticket and link, i preffer to move from project 1 to project 2.

I understand that it"s not possible but...

It's possible to tag the proj1task1 with a label or category or labels or components and catch it from project 2?

I understand that it could be better to divide the task proj1task1 in 2 parts. proj1task1 and proj2task1 and link them as "proj1task1" blocks "proj2task1".

What do you think?

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-cloud

atl-gruland

automation

jira-service-management-cloud

team-managed-projects