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

IPv6 Support for JIRA

XMLWordPrintable

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

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

      Problem

      The currently widely used IPv4 address pool is close to exhaustion: https://en.wikipedia.org/wiki/IPv4_address_exhaustion. IPv6 is around already for a while, however parts of our products may (and do) break.

      Requirement

      • Add IPv6 tests for products and clarify it being supported for all parts of the products (external system connectivity, applinks, self-naming, reverse-proxying, etc).
      • Update the supported platforms documentation and explicitly specify IPv6 to be supported to avoid confusion and give support a reference point.

            [JRASERVER-36676] IPv6 Support for JIRA

            williamdavidedwards added a comment - - edited

            That's a positive development, but as long as the product isn't IPv6-ready, there's work to be done. And it can't be done quickly enough.

            So my question still stands.

            williamdavidedwards added a comment - - edited That's a positive development, but as long as the product isn't IPv6-ready, there's work to be done. And it can't be done quickly enough. So my question still stands.

            Vickey Palzor Lepcha added a comment - - edited

            I guess IPv6 for MySQL databases is supported atleast - that's what I read on the 7.9 Jira Core Release Note.

            Vickey Palzor Lepcha added a comment - - edited I guess  IPv6 for MySQL databases  is supported atleast - that's what I read on the 7.9 Jira Core Release Note.

            williamdavidedwards added a comment -

            What is the status?

            williamdavidedwards added a comment - What is the status?

            Jonas Andersson added a comment -

            Why do i see ::1 localhost entries in Jira application links added by Jira default, if not supported anyway?

            Jonas Andersson added a comment - Why do i see ::1 localhost entries in Jira application links added by Jira default, if not supported anyway?

            license management added a comment - - edited

            ..

            license management added a comment - - edited ..

            Stefan Schwarz added a comment -

            This is not a question. Its a must.

            Stefan Schwarz added a comment - This is not a question. Its a must.

            benjamin.cristinziani@wellsfargo.com added a comment -

            We will need JIRA to be compatible with IPv6 most likely by 3Q of 2017 as we are transitioning over to a IPv6 network with all of our servers.

            benjamin.cristinziani@wellsfargo.com added a comment - We will need JIRA to be compatible with IPv6 most likely by 3Q of 2017 as we are transitioning over to a IPv6 network with all of our servers.

            Sander Steffann added a comment -

            IPv6 support is also a requirement for projects with the US Government.

            Sander Steffann added a comment - IPv6 support is also a requirement for projects with the US Government.

            Dieter Greiner added a comment -

            I'd like to point out that our internal IPv4 addresses are exhausting as well and this is why we would need at least a commitment to IPv6 soon.

            Dieter Greiner added a comment - I'd like to point out that our internal IPv4 addresses are exhausting as well and this is why we would need at least a commitment to IPv6 soon.

              lvysochyn@atlassian.com Leo
              yen@atlassian.com TeckEn (Inactive)
              Votes:
              77 Vote for this issue
              Watchers:
              69 Start watching this issue

                Created:
                Updated:
                Resolved: