|
I have a very similar need. As changes across a number of separate units (each represented by a project) are identified, we need to raise an issue to signal action is required on most projects. This might be as high as 70 projects, meaning that we would have to clone a single issue 70 times.
We would much prefer to raise an issue across multiple projects or to raise the issue on one project and then easily copy it to many others. Has any simple way been identified to do this? Alternatively, is any work underway to include it? This talk of cloning issues and then trying to keep them in synch suggests something is broken in the data model. There should be only one location to record info.
If the problem can be summarized as: > 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. Wouldn't the best solution be to distinguish between "product" bugs and "library" bugs?
They could then be linked together (ie. product bug "is caused by" library bug). Jeff - here's my use case. We have opened up JIRA to our customers for use as a helpdesk. They have access to one (support) project only. Most of the issues can be resolved by fixing data, doing training etc. However, sometimes, they find a real bug that needs to be fixed. So we close the support issue and create a new issue in our internal development project, linking the two together. I've actually created a workflow action called "Close for Development to Fix" which
The customer doesn't see the link (except in change history, if they poke around), but internally we do. So we can track support issues to development issues (and fix versions) and vice versa. Think about how you link support requests on support.atlassian.com to bugs on jira.atlassian.com. It's a different instance (which people which only one license can't do, by the way). But what's more there's no internal link between the 2 issues. Not the best model. However, the summary of this issue states:
Now that is not something I need (or want), and I think that's the part that you are commenting on. So if that's the crux of this issue, I may change my vote. I'm looking for a clone/move operation - both as part of a workflow operation and standard operation. By the way - I've tried Mei's plug-in, but it doesn't work for me because:
> maintain changes across Cloned issues
Now that is not something I need (or want), and I think that's the part that you are commenting on. Yes. It's fairly clear that a support case is distinct from a bug, and shouldn't be kept synchronised. I am suggesting that a similar distinction could be made between product bugs (end-user-oriented) and library bugs (programmer-oriented). If such a distinction cannot be made, then there shouldn't be two separate projects. > So if that's the crux of this issue, I may change my vote. I'm looking for a clone/move operation - both as part of a workflow operation and standard operation. Clone-and-move would be handy. I think it should be its own issue. We actually have a separate project called CORE to handle the common library issues. No need to duplicate across products.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Ability to Create issues and automatically Clone/Move to multiple projects and maintain changes across Cloned issues
The workflow transition could be called 'Copy this issue to project' or 'Assign to X Project' (for example) and the issue could then automatically be copied to the relevant project and an issue created and the status could be 'Assigned to X Project' (for example).
It would be nice to be able to configure the workflow post function to allow the user to configure the 'move' field mapping aspects (as seen in the move issue wizard) for the overall functionality of the transition so that this occurs automatically every time the workflow is transitioned.
Perhaps, to allow the post-function to potentially copy it to multiple projects the 'move wizard' field mapping process can be performed for each project. Then if more than one project exists the transition can display a project mulit-select drop down option in the transtion screen liisting the projects or display no project drop down if only a single project is targeted for the transition.