Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-1527

Uncommitted changes indicator shows changes, but none are visible in commit dialog

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Highest
    • None
    • 2.0.0, 2.0.3, 2.2.2, 2.12.0
    • None

    Description

      NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.

      Description

      In some rare situations it is possible for a plan to accumulate "phantom" changes. The uncommitted changes indicator shows 1 or more changes, but on opening the commit dialog, none are visible.

      Workaround

      Cloud:

      Contact support

      Server:

      Workaround 1

      WARNING: This will remove ALL uncommitted changes for the plan. Make sure you commit/revert all your changes prior to attempting this.
      There is a hidden plan configuration screen that allows for resetting all pending changes (including but not limited to the phantom ones). This will make the phantom changes go away. This configuration screen can be accessed as follows:

      1. Login as an administrator and go to [BASE-URL]/secure/SiteDarkFeatures!default.jspa
      2. Enable the com.atlassian.portfolio.plan.ExtendedAdministration dark feature on the JIRA instance.
      3. Visit the plan configuration screen (open the plan, click the three-dot menu next to the plan name, then choose Configure).
      4. Click on the new Extended Administration section in the column on the left (the dark feature makes this visible).
      5. Confirm that you want to reset uncommitted changes.

      Workaround 2

      The steps below are applicable as the dark feature defined in the Workaround 1 is not applicable in the newer versions of ARM:

      1. Navigate to the plan
      2. Click on ( ... ) > Configure > Scenario (If it's not enabled, please enable it)
      3. Create a new scenario (If there's already one, please proceed to the next step)
      4. Create another scenario > Create from Copy of Initial Scenario for backup purposes.
      5. Create another Scenario but this time, create with blank scenario
      6. There should be now a scenario without "ghost changes" (the blank scenario)
      7. Delete the other scenario and use the blank scenario that has no "Ghost changes"

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jrussell@atlassian.com James Russell
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

              Dates

                Created:
                Updated:
                Resolved:
                Archived: