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 transfert some ticket from a Project to another one ?

Manon Ledda

Hello,

As I said in my question I wonder if it is possible to transfert some tickets from a Project to an other one ?

For exemple I have 2 team and they are working in 2 different project : Project A and Project B. But some of the tickets of the Project B will need the intervention of the team od Project A.
But I don't want that the Team of Project A had acces to Project B and the full visibility on the project.

Do you think it is possible ?

If not do you know if their is some way to duplicate the tickets from Project A to Project B ?

Accepted answers

John Funk

Hi Manon - Welcome to the Atlassian Community!

Yes, that can be done with a Move function. While on the issue/card, click the 3 dots menu in the upper right and select Move.

You have the ability to change the Project and the Issue Type if you want. Or just one of those things.

All comments

John Funk

Hi Manon - Welcome to the Atlassian Community!

Yes, that can be done with a Move function. While on the issue/card, click the 3 dots menu in the upper right and select Move.

You have the ability to change the Project and the Issue Type if you want. Or just one of those things.

Ravi Sagar _Sparxsys_

Hi @Manon Ledda

This is a common use case. The suggestion here would be to not move the ticket, instead create a linked ticket.

Move ideally should be used when issue/ticket was created by mistake in wrong place.

Using linking feature you will have traceability and later on can report on issue that required other team's help. For transferring the information between those linked issues you can also use Automation rules. For example - transition the original issue or add comments.

Of course you can also move the issue. There should be an option on that ticket.

I hope it helps.

Ravi

Julie d_Antin _Elements__bsgnak

Hi @Manon Ledda ,

I'm with Elements and our app Elements Copy & Sync could help you out. It allows you to copy issues with fields, attachments, and comments and you can choose to link issues if you need to.

For your use case where you regularly need to copy issues from Project A to Project B, you could configure a recipe that is triggered either manually or as a post-function when you transition the Project A issue.

Like Ravi mentioned, you can use Automation to create linked clones, but Automation doesn't copy over attachments and if you aren't on Jira Premium you could quickly use up all your executions for the month.

Manon Ledda

Thanks a lot!!

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