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

Documentation request - supported platform page for all Atlassian products

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • 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.

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

      The differences between supported platform across Atlassian products can cause major confusion on the customer side.

      For example, for latest JIRA 6.1.5 and Confluence 5.4 , the differences is tolerate-able. However, we are to compare JIRA 6.1.5 and Bamboo 5.3 (both latest) we can see huge differences. Eg:

      • JIRA supporting only OracleJDK 1.7, Bamboo does support OpenJDK 1.7 and OracleJDK 1.6 and 1.7
      • JIRA only support Tomcat 7 , Bamboo does support Tomcat 5,6,7
      • JIRA support Postgresql 8.3, 8.4 and 9.0 , meanwhile Bamboo supporting only 8.2+ (can't be sure if this mean PostgreSQL version 8.2 and above)

      If we are to add FishEye 3.2 to this equation:

      • FishEye support Postgresql 8.2 , 8.3 and 8.4 .

      Even though, some of the versions does match for the applications , it does not allow the customer to have a consistent versions of platform that they should use. Upgrading platforms like database is a challenge as we do not have a specific page for users with multiple product running. We should at least has a central page to recommend customer what environment is the best for every major release as this is when we evaluate the Supported Platform.

            [JRASERVER-36307] Documentation request - supported platform page for all Atlassian products

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3061652 ] New: JAC Suggestion Workflow 3 [ 3688341 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2617891 ] New: JAC Suggestion Workflow [ 3061652 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2587297 ] New: Confluence Workflow - Public Facing v4 [ 2617891 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2362407 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2587297 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2130095 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2362407 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093547 ] New: JIRA Bug Workflow w Kanban v6 [ 2130095 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 888409 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093547 ]
            jonah (Inactive) made changes -
            Description Original: The differences between supported platform across Atlassian products can cause major confusion on the customer side.

            For example, for latest JIRA 6.1.5 and Confluence 5.4 , the differences is tolerate-able. However, we are to compare JIRA 6.1.5 and Bamboo 5.3 (both latest) we can see huge differences. Eg:
            * JIRA supporting only OracleJDK 1.7, Bamboo does support OpenJDK 1.7 and OracleJDK 1.6 and 1.7
            * JIRA only support Tomcat 7 , Bamboo does support Tomcat 5,6,7
            * JIRA support Postgresql 8.3, 8.4 and 9.0 , meanwhile Bamboo supporting only 8.2+ (can't be sure if this mean PostgreSQL version 8.2 and above)

            If we are to add FishEye 3.2 to this equation:

            * FishEye support Postgresql 8.2 , 8.3 and 8.4 .

            Even though, some of the versions does match for the applications , it does not allow the customer to have a consistent versions of platform that they should use. Upgrading platforms like database is a challenge as we do not have a specific page for users with multiple product running. We should at least has a central page to recommend customer what environment is the best for every major release as this is when we evaluate the Supported Platform.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-36307].
              {panel}

            The differences between supported platform across Atlassian products can cause major confusion on the customer side.

            For example, for latest JIRA 6.1.5 and Confluence 5.4 , the differences is tolerate-able. However, we are to compare JIRA 6.1.5 and Bamboo 5.3 (both latest) we can see huge differences. Eg:
            * JIRA supporting only OracleJDK 1.7, Bamboo does support OpenJDK 1.7 and OracleJDK 1.6 and 1.7
            * JIRA only support Tomcat 7 , Bamboo does support Tomcat 5,6,7
            * JIRA support Postgresql 8.3, 8.4 and 9.0 , meanwhile Bamboo supporting only 8.2+ (can't be sure if this mean PostgreSQL version 8.2 and above)

            If we are to add FishEye 3.2 to this equation:

            * FishEye support Postgresql 8.2 , 8.3 and 8.4 .

            Even though, some of the versions does match for the applications , it does not allow the customer to have a consistent versions of platform that they should use. Upgrading platforms like database is a challenge as we do not have a specific page for users with multiple product running. We should at least has a central page to recommend customer what environment is the best for every major release as this is when we evaluate the Supported Platform.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-36307 [ JRACLOUD-36307 ]

              Unassigned Unassigned
              vkharisma vkharisma
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: