-
Suggestion
-
Resolution: Won't Do
-
None
-
None
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.
- incorporates
-
- Closed
- relates to
-
- Closed
[JRASERVER-36307] Documentation request - supported platform page for all Atlassian products
Jóhann B. Guðmundsson
added a comment - It would be good to get firm back porting policy on security related patches from Atlassian on products that it recommends and or puts under "supported platform" for example postgresql 8.3 got EOL in February 2013.
And it would be good to know why Atlassian cant support latest stable upstream releases in all cases?
Jóhann B. Guðmundsson
added a comment - It would be good to get firm back porting policy on security related patches from Atlassian on products that it recommends and or puts under "supported platform" for example postgresql 8.3 got EOL in February 2013.
And it would be good to know why Atlassian cant support latest stable upstream releases in all cases?
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.
Thanks again.
Regards,
Jira Product Management