Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-20352

automatic linking between multiple Jira instances

XMLWordPrintable

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

      Our problem is, that we can't set our main Jira instance to the outside world (security breach). So we want to run 2 Jira Instances.

      One only accessible from the intranet for adjusting the development team and another (integrated into our Website) to get (anonymous/registered) feedback/bugs from external users of our Software.

      The problem is the synchronization of these two instances.
      It would be great, if there could be an automatic way to sync this two instances. Otherwise every developer had to watch and work on 2 different instances.

      One way would be: If internal is A and external B, the internal should show A+B and the external only B.

      I think, the main feature lies inside the automatic push/pull creation of new tickets from one instance to another. A more complex feature might be the complete automatic linking of issues across multiple instances so that you can make changes at both sides witch will be synchronized across the instances.

            [JRASERVER-20352] automatic linking between multiple Jira instances

            Roy Krishna (Inactive) added a comment -

            Hi Tim,

            At this time we do not anticipate adding this into JIRA in the foreseeable future.

            I'll close this in the mean time to keep things tidy on our end.
            If we ever look into your request again I'll be sure to reopen this issue.
            Thanks for your suggestion.

            Cheers,
            Roy

            Roy Krishna (Inactive) added a comment - Hi Tim, At this time we do not anticipate adding this into JIRA in the foreseeable future. I'll close this in the mean time to keep things tidy on our end. If we ever look into your request again I'll be sure to reopen this issue. Thanks for your suggestion. Cheers, Roy

            stephane oberlechner added a comment -

            Hello ,

            We have exactly the same target.

            We have différent solution to link theses diferents JIRA instances :
            Using Jelly Script
            Using A ESB (Mule) to catch events from A and writing task into B (also B-> A), with XML transformation

            Anyway, you have already a solution (very low cost) to help your developer not to Watch 2 differents Instances : On your Dashbord from A, you can Watch inside a Text Portlet what happen on B : On these text portlet (A) , you can copy/pasted url from stat portlet (B)

            Regards

            stephane oberlechner added a comment - Hello , We have exactly the same target. We have différent solution to link theses diferents JIRA instances : Using Jelly Script Using A ESB (Mule) to catch events from A and writing task into B (also B-> A), with XML transformation Anyway, you have already a solution (very low cost) to help your developer not to Watch 2 differents Instances : On your Dashbord from A, you can Watch inside a Text Portlet what happen on B : On these text portlet (A) , you can copy/pasted url from stat portlet (B) Regards

              Unassigned Unassigned
              e344fc75dcd2 timmjd
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: