-
Suggestion
-
Resolution: Unresolved
-
3
-
42
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
This is somewhat related to JRA-2581. This is our most pressing problem regarding JIRA right now. We have a number of projects which depend on a rather large set of common libraries. When issues are reported they are reported against a given product even though the bug may be down in the common libraries affecting a number of products. Many times it is not obvious if the issue is at the application level or down in the common library when it is first reported, but the issues are always reported against the product, not the libaries. What we need is a way to easily report the same issue against multiple projects and to track them separate if need be, but also to apply changes to this issue across all the projects it is reported against.
Basically, I'd like to see a feature that allows me to clone an issue to multiple projects and versions in one step. This would be available at the Create, Edit , or Resolve issue stage. Once an issue was cloned then anytime a change was made, other than to the Version or Component, it could be applied to zero or more of the linked (of type clone) issues. This would give us the ability track issues separately if need be or to report them against multiple products and resolve them in multiple projects (for tracking purposes) easily without having to clone/move-clone/move-clone/move for each project.
Perhaps a UI where I could check a box saying to 'Apply to multiple projects' and then Add Project/Versions to a list. If it was a new issue it would automatically create the clones and move them to the specified projects and if it was an existing issue you could select which project to apply changes to and/or add/delete projects from the list.
We've tried to use the Cloning feature currently available to address this issue, but we're finding it is just to cumbersome to create, clone/move, clone/move, clone/move, etc to be practical. Also, if you apply a change to one issue such as a comment, this is not propogated to the other cloned issues. You can still get to it via the links, but it is easy for people to miss relevant information if they don't review the linked issues.
- incorporates
-
- Closed
- is related to
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-7948] Ability to Create issues and automatically Clone/Move to multiple projects and maintain changes across Cloned issues
Anh Vu
added a comment - This is my specific use-case and would love any updates that might help me achieve this.
My team's workflow has two different projects that are associated with one another (let's call them project1 and project2). All issues in both projects have the same (custom) fields. Upon receiving certain samples, my team would update some of these fields in one of the projects to indicate things like what kind of sample was received, when it was received, etc. However, instead of manually updating these fields in the other project, my team would like a way to somehow automate this process. So if some fields in an issue are updated in project1, we would like a way to automatically populate the same fields in the corresponding issue in project2.
Anh Vu
added a comment - This is my specific use-case and would love any updates that might help me achieve this.
My team's workflow has two different projects that are associated with one another (let's call them project1 and project2). All issues in both projects have the same (custom) fields. Upon receiving certain samples, my team would update some of these fields in one of the projects to indicate things like what kind of sample was received, when it was received, etc. However, instead of manually updating these fields in the other project, my team would like a way to somehow automate this process. So if some fields in an issue are updated in project1, we would like a way to automatically populate the same fields in the corresponding issue in project2. 
Russell Siachico
added a comment - We are rolling out S.D for our internal teams. Having to duplicate, and then move it out from S.D project to another JIRA project is troublesome. So a definite +1 for us.
Russell Siachico
added a comment - We are rolling out S.D for our internal teams. Having to duplicate, and then move it out from S.D project to another JIRA project is troublesome. So a definite +1 for us. 
Zach Lanich
added a comment - @carl.stewart247713222's thoughts are interesting. +1 on the blocking functionality. +1 for "optional" comments sync. We keep ours separate, but it would be nice to have.
Zach Lanich
added a comment - @carl.stewart247713222's thoughts are interesting. +1 on the blocking functionality. +1 for "optional" comments sync. We keep ours separate, but it would be nice to have. Hi,
I would also like it if when creating a task, that is then cloned, moved to other projects that I specify, that those other tasks should be set as a blocker to this main task. Comments should be synced up as well. Then as each task that is a blocker for the main task is verified by QA, they will then close each one. When all the tasks that were blockers for the main task are closed, the main task is automatically closed.
We are using the exact same process though our use case is different. And suggestions to improve upon this would be a major add for us as well.
Zach Lanich
added a comment - Hey folks, I'm adding some details regarding our needs to help in the decisions made for this Feature Suggestion:
Our Use Case
We provide development services fora large company who is split into many subsidiaries. We have a single Service Desk Project where all incoming requests are made from the client, and we have a Jira Software Project for each subsidiary for the mass of general maintenance/development tasks that always come in. Large new builds would deserve their own Software Project.
Our Current Process (painful)
When an Issue in the Service Desk is assigned to me, I "Clone->Move->Rename" into the relevant Software Project, then assign it to a specific developer.
Issues with this Process
- There are several steps every time we have to do this
- Nothing is synchronized between the Service Desk Issue and the linked Project Issue at this point, other than the link itself
- Often times, developers will accidentally make comments on the Service Desk Issue instead of the Project Issue, and this happens with everyone, often. These comments are not synchronized in any way, which leads to majorly fragmented communication. Even a "Customer" ended up commenting on a Project Issue some how!! (please tell me how this happened if you know)
- When developers update a Project Issue Task Status from ToDo to In Progress, the Service Desk Issue remains as "Open" and I have to manually mark it as "In Progress" so the customer knows it's as such. What's more, if I decide to put the Issue "On Hold", I have to manually tell the developers to put all their related issues "On Hold" as well, or dive down into each related project myself to do it. What a nightmare!
- Media assets are not synchronized, so the Customer adds a new asset to the Service Desk Issue and it's not available for the developers. I have to manually download all "new" attachments and re-upload them to EVERY project-level Issue. Nightmare again!
Final Notes
Please let me know if there's a better way to do what I'm doing right now, as this is getting very cumbersome and we're beginning to make significant mistakes with this large client due to poor communication. If you guys know of a temporary workaround for my issues, please let me know. Either way, please use the above gripes to help fuel this feature!
Zach Lanich
added a comment - Hey folks, I'm adding some details regarding our needs to help in the decisions made for this Feature Suggestion:
Our Use Case
We provide development services fora large company who is split into many subsidiaries. We have a single Service Desk Project where all incoming requests are made from the client, and we have a Jira Software Project for each subsidiary for the mass of general maintenance/development tasks that always come in. Large new builds would deserve their own Software Project.
Our Current Process (painful)
When an Issue in the Service Desk is assigned to me, I "Clone->Move->Rename" into the relevant Software Project, then assign it to a specific developer.
Issues with this Process
There are several steps every time we have to do this
Nothing is synchronized between the Service Desk Issue and the linked Project Issue at this point, other than the link itself
Often times, developers will accidentally make comments on the Service Desk Issue instead of the Project Issue, and this happens with everyone, often. These comments are not synchronized in any way, which leads to majorly fragmented communication. Even a "Customer" ended up commenting on a Project Issue some how!! (please tell me how this happened if you know)
When developers update a Project Issue Task Status from ToDo to In Progress, the Service Desk Issue remains as "Open" and I have to manually mark it as "In Progress" so the customer knows it's as such. What's more, if I decide to put the Issue "On Hold", I have to manually tell the developers to put all their related issues "On Hold" as well, or dive down into each related project myself to do it. What a nightmare!
Media assets are not synchronized, so the Customer adds a new asset to the Service Desk Issue and it's not available for the developers. I have to manually download all "new" attachments and re-upload them to EVERY project-level Issue. Nightmare again!
Final Notes
Please let me know if there's a better way to do what I'm doing right now, as this is getting very cumbersome and we're beginning to make significant mistakes with this large client due to poor communication. If you guys know of a temporary workaround for my issues, please let me know. Either way, please use the above gripes to help fuel this feature! 
Naresh Dasari
added a comment - Is there a way to automatically add a issue in two projects at a time in JIRA
Example: If i create a issue in "Sample-A" project that same issue will automatically create in "Sample-B" project.
Naresh Dasari
added a comment - Is there a way to automatically add a issue in two projects at a time in JIRA
Example: If i create a issue in "Sample-A" project that same issue will automatically create in "Sample-B" project. 
S Guru
added a comment - Guys, am wondering why this feature request is considered despite it has been there for several years. I heard JIRA could be used for service desk related tasks where it is crucial to have use-cases. Please consider this ASAP or suggest a viable solution (excepting manual cloning).
S Guru
added a comment - Guys, am wondering why this feature request is considered despite it has been there for several years. I heard JIRA could be used for service desk related tasks where it is crucial to have use-cases. Please consider this ASAP or suggest a viable solution (excepting manual cloning). 
Chris F
added a comment - The ability to add a clone to a workflow to allow creating a new issue for other fix-for-versions is essential.
This eliminates human error where it may be forgotten to be created as the clone has to be manually created.
Chris F
added a comment - The ability to add a clone to a workflow to allow creating a new issue for other fix-for-versions is essential.
This eliminates human error where it may be forgotten to be created as the clone has to be manually created. 
14 years since this ticket was created, I still think this is necessary functionality, specially when working on a multivendor model, in which you normally have a centralized project for the backlog and then you copy (clone + move) tickets to each vendor's project.