Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3746

Create linked issue in another JIRA Instance and automated notifications

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Forge and Connect
    • None
    • 14
    • 5

    • 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 Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      I have the use case that we use one instance for JIRA Service Desk and have several other instances in our organization. Now there is the great feature to create linked issues - unfortunately just on the same site. 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

          Form Name

            [JSDCLOUD-3746] Create linked issue in another JIRA Instance and automated notifications

            Chris added a comment -

            Our teams use the linked issue feature across instances on a daily basis now. It creates a lot of extra communication and work to make an issue to link to, rather than simply create a linked issue in the 2nd instance. This is a big part of our operation now and will likely become even more important in the coming months and years.

            Chris added a comment - Our teams use the linked issue feature across instances on a daily basis now. It creates a lot of extra communication and work to make an issue to link to, rather than simply create a linked issue in the 2nd instance. This is a big part of our operation now and will likely become even more important in the coming months and years.

            Asim K added a comment -

            https://confluence.atlassian.com/jirakb/how-to-create-and-link-remote-jira-issues-using-automation-1085209850.html

            Asim K added a comment - https://confluence.atlassian.com/jirakb/how-to-create-and-link-remote-jira-issues-using-automation-1085209850.html

            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.

            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.

            Bernd Konrad added a comment -

            Thumbs up for this one.

            The ability to link existing issues in another JIRA instance is already there if both instances are correctly linked, so I'd imaging it wouldn't be a massive undertaking to implement this.

            Currently we manually have to jump into the other JIRA instance and create the issue, just to jump back into the Service Desk instance to link it. Seems completely unnecessary.

            Bernd Konrad added a comment - Thumbs up for this one. The ability to link existing issues in another JIRA instance is already there if both instances are correctly linked, so I'd imaging it wouldn't be a massive undertaking to implement this. Currently we manually have to jump into the other JIRA instance and create the issue, just to jump back into the Service Desk instance to link it. Seems completely unnecessary.

              Unassigned Unassigned
              740899006c4e Christoph Benedikt
              Votes:
              58 Vote for this issue
              Watchers:
              37 Start watching this issue

                Created:
                Updated: