Our Company has several projects in Jira: one "main" project and several client's projects. They all have the sam workflow/issue types/fields ect. If our Test Team find an issue in client's project, they look on the "main" project if such issue was reported already. If so, they copy this issue to a clients project. To do that they need to duplicate issue and then move it to another project. This way of doing has two major issues: * Our "main" project issue counter raise by one each time they copy issue. This create "holes" in numeration. * Sometimes issue in main project are already assigned to a sprint. When Testers copy this issue to another project , sprint field is also copied and "copy issue" also appear on the sprint for main project. Administrator of main project cannot close such sprint (he/she don't have permission to client project) and Administrator for client project see sprint from main project on his dashboard . If there somehow possible to copy issue to another project without go through 2-steps duplicate and move procedure? (plugin,configuration change ect)

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

How to copy jira issue directly to another project?

Piotr Wydrzyńsk

Our Company has several projects in Jira: one "main" project and several client's projects. They all have the sam workflow/issue types/fields ect.

If our Test Team find an issue in client's project, they look on the "main" project if such issue was reported already. If so, they copy this issue to a clients project. To do that they need to duplicate issue and then move it to another project.

This way of doing has two major issues:

Our "main" project issue counter raise by one each time they copy issue. This create "holes" in numeration.
Sometimes issue in main project are already assigned to a sprint. When Testers copy this issue to another project , sprint field is also copied and "copy issue" also appear on the sprint for main project.
Administrator of main project cannot close such sprint (he/she don't have permission to client project) and Administrator for client project see sprint from main project on his dashboard .

If there somehow possible to copy issue to another project without go through 2-steps duplicate and move procedure? (plugin,configuration change ect)

Accepted answers

All comments

Nic Brough -Adaptavist-

There's a "clone and move" add-on which can turn the move into a single procedure. I think it's been updated so that it clears the sprint field during the move which will solve issue 2 for you. (Holes in the numbering doesn't really matter much, it's information that an issue was moved or deleted, but doesn't affect your reporting or numbers)

Prashant Mali_vx7l3g

Hi Piotr,

Have you considered creating a board for each team, and one for the product owner/PM? If they have the same filter, they will show the same issues, and all 'started' sprints (if a sprint is in planning, it does not technically exist, so will not show across boards). This way, each team can work off of their own board, and report on their own sprints, without having to duplicate issues.

If that doesn't work, I would consider cloning the issue, which will create a copy that can be linked as well. Unfortunately, without some development, you won't be able to sync the tickets, and you couldn't do that with OnDemand.

Hope that helps!

Piotr Wydrzyńsk

Thank you for your quick responses.

Each project has separate product owners and separate dashboards.

To ilustrate the issue further: Lets call our main project as MAIN and client's project as CLI.

Tester Created issue in main project MAIN-1
Project Owner assign this issue to ongoing sprint SPRINT-1
Tester found the same issue in CLI project. They copy issue by duplicate the issue ( MAIN-2) and move MAIN-2 to CLI project ( MAIN-2 will now be CLI-1)
MAIN project Dashboard has filter "show only issues from MAIN project" .So CLI-1 will not show on the board HOWEVER during copy procedure it also copied sprint field and CLI-1 is now assigned to SPRINT-1.

Result: On CLI DASHBOARD you will see SPRINT-1 with one issue CLI-1. On MAIN DASHBOARD you will not see CLI-1 however if you want to close SPRINT-1 it will blocks you because you dont have permission to CLI project.

That why we would like to know is there any solution to specify project during copy issue. We use server installation not on demand.

Nic, we used this add-on sometimes ago but it keep the sprint field. We will try again and review new version.

Colin Campbell_htkuik

After creating your template project with tasks etc. You could do a bulk change to move them to a new project.

Thomas Bray

Does this remove them from the template project?

Colin Campbell_htkuik

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software