-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
8.15.0, 8.16.0, 8.16.1
-
8.15
-
19
-
Severity 3 - Minor
-
66
-
Issue Summary
In upgraded instances of Jira Server 8.15 and 8.16, it is possible to uninstall or disable Advanced Roadmaps. If we do this, however, Jira Software is automatically disabled, and must be re-enabled in the pluginstate table of the database.
Steps to Reproduce
- Upgrade an instance of Jira Software from an earlier version (e.g., 8.5) to Jira 8.15 or 8.16
- Disable or uninstall Advanced Roadmaps
Expected Results
Advanced Roadmaps will be disabled or uninstalled without any impact on other applications.
Actual Results
Jira Software is disabled, and cannot be re-enabled via the UI. It must be re-enabled with the following query:
update pluginstate set pluginenabled = 'true' where pluginkey LIKE 'com.atlassian.jira.jira-software-application';
Attempts to re-enable Jira Software via the UI do not throw any error messages in the logs, but only give the message 'An unexpected error occurred. Refer to the logs for more information.'
If we re-enable Jira Software, Advanced Roadmaps will also be re-enabled automatically.
Workaround
If we want to hide the app from users, t is possible to remove users' permissions in Advanced Roadmaps, or to remove the license without impacting Jira Software.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-20920] Disabling or Uninstalling Advanced Roadmaps Disables Jira Software
We have suffered a bit from this since Advanced Roadmaps (Team Management) comes with predifined custom field Team that collide with our own custom field Team, which is heavily used by users in filters.
The reason we now got Advanced Roadmaps at all seams to be that we had a trial licence for it back in 2015-2016. This made the permission solution in Workaround unavailable since our license is expired To remove the license had no effect on the built in custom field, still available in Searches and Filters.
We found a third workaround, at last, which at least make our specific bug go away. In Advanced Roadmaps Team Management I was able to disable the module Team. This was possible without Jira Software Application getting Disabled automatically.
Maybe other modules can be disabled as well, worth an attempt for those of you having similar problems with Advanced Roadmaps.
It's just a SHAME introducing a new custom field with a very common name and locking it! You know this will give conflicts at customer side, but this seems to be none of your concerns...