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:
If there somehow possible to copy issue to another project without go through 2-steps duplicate and move procedure? (plugin,configuration change ect)
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.
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.
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)
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!
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs