-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
We have a new JIRA release quite regularly. Also, we encourage users to stay up to date with the used JIRA version.
Taking the above into account users may find themselves in a need of migrating SSL keys between their systems rather often. Moreover, it can cause someone system to become inaccessible, if on upgrade the SSL migration step isn't performed.
It seems unnecessary and could be easily avoided by allowing users to retain their currently used JVM. Alternatively, we could consider importing the 'old' JIRA's keystore to the one provided with the installer.
- relates to
-
JRACLOUD-25475 Installer (specifically its upgrade feature) should import SSL KeyStore or allow reuse of a custom, existing JVM
- Closed
Thanks for taking the time to raise this issue.
Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.
I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.
Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com