• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Board configuration
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Please implement a MERGE feature for JIRA, so that separate related tickets can be merged into one parent (ie: RT can do this).   This will help cut down on the noise level where an issue crops up and, for example, several users open tickets about the same issue.    As it stands now, I can "link" but that's just not useful for us, as I still must answer each individual ticket.   The Merge feature might also have an option to set the destination to where alerts go (which is usually the owner of the parent ticket, but flexibility can be useful).

            [JSWSERVER-16267] JIRA ticket MERGE

            Atlassian Update – 27 September 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 September 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

              Unassigned Unassigned
              83d156b662c5 Forrest Aldrich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: