• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      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?

          Form Name

            [JRACLOUD-14743] Add workflow post function for cloning an issue

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Eric Bloch added a comment -

            Thanks, Anton. I searched and couldn't find that issue. One thing I didn't see specifically captured in JRA-7948 is that , for my use case, I don't want to clone to a new project. I want to clone to the same project but with a different fix-for version. Feel free to resolve/dup if you think it's all captured there. I think, as you said though, since this is smaller and still fulfills several use cases, you might want to consider leaving it stand-alone.

            I did see http://confluence.atlassian.com/display/JIRAEXT/JIRA+Clone+and+Move+Plugin but couldn't really figure out what it would take to get what I need

            -Eric

            Eric Bloch added a comment - Thanks, Anton. I searched and couldn't find that issue. One thing I didn't see specifically captured in JRA-7948 is that , for my use case, I don't want to clone to a new project. I want to clone to the same project but with a different fix-for version. Feel free to resolve/dup if you think it's all captured there. I think, as you said though, since this is smaller and still fulfills several use cases, you might want to consider leaving it stand-alone. I did see http://confluence.atlassian.com/display/JIRAEXT/JIRA+Clone+and+Move+Plugin but couldn't really figure out what it would take to get what I need -Eric

            AntonA added a comment -

            Hi Eric,

            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:
            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. 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.

            Cheers,
            Anton

            AntonA added a comment - Hi Eric, 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: 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 . 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. Cheers, Anton

              Unassigned Unassigned
              1e373dbd7c3e Eric Bloch
              Votes:
              14 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: