...
then when you disable Portfolio, the Child issues section disappears, and you are where you want to be.
Addendum: post-uninstall log errors
After uninstalling Portfolio, you might find your atlassian-jira.log file being filled with errors on each page load:
| Code Block |
|---|
2019-11-11 00:59:59,234 ajp-nio-127.0.0.100-8009-exec-4059 WARN jturner 59x3059696x3 56p7sr 10.36.2.100 /browse/CC-5353 [c.a.r.j.p.w.children.condition.ChildIssuesPanelVisibilityCondition] Exception when evaluating if child issues panel should be displayed.
com.atlassian.rm.common.env.EnvironmentPortfolio1NotAvailableException: com.atlassian.rm.common.bridges.api.plugins.PluginNotAvailableException
at com.atlassian.rm.common.env.license.JiraLicenseService.getLicenseInformation(JiraLicenseService.java:36)
at com.atlassian.rm.common.env.license.JiraLicenseService.isLicensed(JiraLicenseService.java:45)
at com.atlassian.rm.jpo.plugin.webpanels.children.condition.ChildIssuesPanelVisibilityCondition.isLicensed(ChildIssuesPanelVisibilityCondition.java:81)
at com.atlassian.rm.jpo.plugin.webpanels.children.condition.ChildIssuesPanelVisibilityCondition.shouldChildrenBeVisible(ChildIssuesPanelVisibilityCondition.java:68) at com.atlassian.rm.jpo.plugin.webpanels.children.condition.ChildIssuesPanelVisibilityCondition.shouldDisplay(ChildIssuesPanelVisibilityCondition.java:54)
at com.atlassian.plugin.web.DefaultWebInterfaceManager.filterFragmentsByCondition(DefaultWebInterfaceManager.java:154)
at com.atlassian.plugin.web.DefaultWebInterfaceManager.getDisplayableWebPanelDescriptors(DefaultWebInterfaceManager.java:117)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498) ... |
In Jira's Manage apps admin page you will find these two vestigial plugins:
Uninstall them and your Jira should be back to normal. Jira's plugin system lets plugin authors package reusable parts as separate plugins, but isn't smart enough to uninstall them when the parent plugin is uninstalled.