Uninstalling Portfolio should uninstall all dependencies that were Installed with the Bundle

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 28
    • Severity 3 - Minor
    • 198
    • Hide

      After careful analysis and assessing potential solutions for this bug, and although we appreciate that having to remove each Portfolio add-on separately can be cumbersome, we have decided to close this bug as "Won't Fix".

      Since the universal plugin manager does not allow to specify which plugins belong together, the way Portfolio is packaged would have to be reengineered. We believe that the time and effort required to do it would be better invested in other priorities.

      Thank you for your understanding.

      Quentin Feyaerts
      Software Engineer | Portfolio for Jira Server

      Show
      After careful analysis and assessing potential solutions for this bug, and although we appreciate that having to remove each Portfolio add-on separately can be cumbersome, we have decided to close this bug as "Won't Fix". Since the universal plugin manager does not allow to specify which plugins belong together, the way Portfolio is packaged would have to be reengineered. We believe that the time and effort required to do it would be better invested in other priorities. Thank you for your understanding. Quentin Feyaerts Software Engineer | Portfolio for Jira Server

      Update 28/Apr/2020

      28/Apr/2020

      After careful analysis and assessing potential solutions for this bug, and although we appreciate that having to remove each Portfolio add-on separately can be cumbersome, we have decided to close this bug as "Won't Fix".

      Since the universal plugin manager does not allow to specify which plugins belong together, the way Portfolio is packaged would have to be reengineered. We believe that the time and effort required to do it would be better invested in other priorities.

       

      Issue summary

      Currently when JIRA Portfolio is installed, this actually installs 3 add-ons:

      • Portfolio for JIRA
      • Portfolio Live Plans
      • Portfolio Team Management

      If a customer wants to uninstall/disable JIRA Portfolio, they'd have to actually go through each add-on to uninstall. If only one of the items are uninstalled, but not others, it can result in odd behaviours in the system.

      In one case, the logs were spammed with:

      2016-10-25 12:59:34,607 http-nio-8080-exec-88 WARN admin 779x1513687x3 1tk8azs 10.34.155.42,10.33.48.156 /secure/AjaxIssueAction!default.jspa [c.a.r.j.p.w.children.condition.ChildIssuesPanelVisibilityCondition] Exception when evaluating if child issues panel should be displayed.
      • There were 10s of thousands of these messages: 
        grep -c 'c.a.r.j.p.w.children.condition.ChildIssuesPanelVisibilityCondition' atlassian-jira.log*
atlassian-jira.log:19858
atlassian-jira.log.1:24540

      Expectation

      There should be some sort of indication to inform the admin of plugin dependencies, or the removing one add-on should also remove the others.

            Assignee:
            Unassigned
            Reporter:
            David Chan
            Archiver:
            Aakrity Tibrewal

              Created:
              Updated:
              Resolved:
              Archived: