• 9
    • 23
    • We collect Jira Service Desk 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.

      NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      I have the use case that we use one server instance for Jira Service Management and have several other instances in our organization. Now there is the great feature to create linked issues - unfortunately just on the same server. I would love to choose from the servers as well.

      Also when a linked issue is translated then, a notification is given as a comment (if set so). But this does not work with linked issues from another server.

      I guess there would be a huge interest in this new feature.

      Cheers,
      Christoph

            [JSDSERVER-3746] Create linked issue in another Jira instance and automated notifications

            Vote +1

            Andrey Khessin added a comment - Vote +1

            Chris Self added a comment -

            Totally agree with the comments - i also have the need to take a ticket from service desk, and replicate (create linked issue) in an agile/software instance to have developers complete the work.

            Chris Self added a comment - Totally agree with the comments - i also have the need to take a ticket from service desk, and replicate (create linked issue) in an agile/software instance to have developers complete the work.

            Pavel added a comment -

            Hi, 

            Are there any updates on implementing the feature of creating linked issue on remote Jira site from Jira Service Management? This would be very valuble feature to save time and efforts of Jira SM agents to create issues to Developers on Jira Software projects and link them to related service requests or incidents.

            Pavel added a comment - Hi,  Are there any updates on implementing the feature of creating linked issue on remote Jira site from Jira Service Management? This would be very valuble feature to save time and efforts of Jira SM agents to create issues to Developers on Jira Software projects and link them to related service requests or incidents.

            Hi,

            Even some kind of automation tool that makes it easier to create an issue in one Jira instance that links to another would be very useful, can we have some indication in here as to if this is even being considered? It's 4 years now since this issue was first raised.

            Robert Field added a comment - Hi, Even some kind of automation tool that makes it easier to create an issue in one Jira instance that links to another would be very useful, can we have some indication in here as to if this is even being considered? It's 4 years now since this issue was first raised.

            Since it is highly feasible for a company to have separate instances of Jira for Service Desk and Software (specifically for hosting them in DMZ and internal networks, respectively), it seems far-fetched that Create linked issue remains unable to work across Jira instances for three years now, even with healthy Application Links in place.  I mean, the functionality already exists within the Link capability.  Personally, I would expect the Create linked issue to work the same as Link but create a new issue in the remote server's project, and that would just need to copy over the Summary and maybe the Description, before linking them.  Again, this doesn't seem unreasonable or impossible given what Jira can already do.

            Midwest Laboratories added a comment - Since it is highly feasible for a company to have separate instances of Jira for Service Desk and Software (specifically for hosting them in DMZ and internal networks, respectively), it seems far-fetched that Create linked issue remains unable to work across Jira instances for three years now, even with healthy Application Links in place.  I mean, the functionality already exists within the Link capability.  Personally, I would expect the Create linked issue to work the same as Link but create a new issue in the remote server's project, and that would just need to copy over the Summary and maybe the Description , before linking them.  Again, this doesn't seem unreasonable or impossible given what Jira can already do.

            Ken Logan added a comment -

            This would be a high-value feature to add, was really surprised to find out this isn't possible already.

            Ken Logan added a comment - This would be a high-value feature to add, was really surprised to find out this isn't possible already.

            This feature would be more than valuable for us and save a lot of time creating issues by hand and linking them afterwards manually.

            Norman Mähler added a comment - This feature would be more than valuable for us and save a lot of time creating issues by hand and linking them afterwards manually.

            David added a comment - - edited

            Actually there is a Atlassian built component that almost do what we need, but doesn't work for 7.3 and up. "JIRA to JIRA issue copy"

            https://marketplace.atlassian.com/plugins/com.atlassian.cpji.cpji-jira-plugin/server/support

            If we start nagging for updates it might be a solution.

            David added a comment - - edited Actually there is a Atlassian built component that almost do what we need, but doesn't work for 7.3 and up. "JIRA to JIRA issue copy" https://marketplace.atlassian.com/plugins/com.atlassian.cpji.cpji-jira-plugin/server/support If we start nagging for updates it might be a solution.

            David added a comment -

            Any news on this issue?

            David added a comment - Any news on this issue?

            This would be extremely valuable.  I believe it is a common scenario to have separate instances for public facing interaction and development.

            Aaron Kitchens added a comment - This would be extremely valuable.  I believe it is a common scenario to have separate instances for public facing interaction and development.

              Unassigned Unassigned
              740899006c4e Christoph Benedikt
              Votes:
              102 Vote for this issue
              Watchers:
              48 Start watching this issue

                Created:
                Updated: