| Key: |
JRA-14743
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Eric Bloch
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Part
|
|
|
|
This issue is incorporated by:
|
|
|
JRA-7948 Ability to Create issues and automatically Clone/Move to multiple projects and maintain changes across Cloned issues
|
|
|
|
|
|
|
Use case: When ever an issue is resovled for a certain fix-for version, I need to create a clone for the porting work in another fix-for version.
Is there a better way?
|
|
Description
|
Use case: When ever an issue is resovled for a certain fix-for version, I need to create a clone for the porting work in another fix-for version.
Is there a better way?
|
Show » |
|
Add workflow post function for cloning an issue 
Having a separate issue for a seperate piece of work, such that it can be assigned by a different individual and have a separate fix for version is a good idea. Out of the box, JIRA does not provide a way to clone issues automatically, it has to be done manually. I believe a larger feature request for this is JRA-7948.
For more information on the way new feature and improvement requests are scheduled please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements
Workflow post functions are plugins in JIRA, so an extension to JIRA can be developed. For more information on writing custom post functions please see:
http://confluence.atlassian.com/display/JIRA/How+to+create+Custom+Workflow+Elements+for+JIRA+3
It appears that some of the leg work for this has been done by another JIRA user:
. As far as I can tell to make the contributed code work as part of a worklow, more code needs to be written to leverage what's there as a post function.
http://confluence.atlassian.com/display/JIRAEXT/JIRA+Clone+and+Move+Plugin
and released to the community. However, I believe it currently does not work for JIRA 3.12.x
Cheers,
Anton