Summary

Review changes don't show the list of changes done in the Advanced roadmap plan and the Review Changes show "1"

Environment

• Jira Software DC/Server 8.15. or later
  
  

Diagnosis

• In the HAR file, look for the rest endpoint - rest/jpo/1.0/scenarios/commit

• Open the HTTP Response and we will see the issue details: 

  {
    "metaData": {
      "abilities": {},
      "skills": {},
      "themes": {},
      "persons": {},
      "teams": {},
      "versions": {},
      "plannedcapacity": {},
      "issueLinks": {},
      "stages": {},
      "resources": {},
      "issues": {
        "14766889": {
          "lastChangeTimestamp": 1684130276138,
          "lastChangeUser": "admin",
          "scenarioType": "UPDATED"
        }
      },
      "crossProjectVersions": {}
    },
    "issues": [
      {
        "id": "14766889",
        "issueKey": 5915,
        "issueSources": [
          3979
        ],
        "values": {
          "type": 2,
          "project": 98580,
          "status": "1",
          "summary": "Technical Debt",
          "lexoRank": "2|hp8noo:1m9ch2oe903w9",
          "labels": [
            "trx_planned"
          ],
          "created": 1683890394000,
          "assignee": "admin",
          "priority": "3"
        },
        "originals": {},
        "assignments": [],
        "annotations": []
      }
    ],
    "issueLinks": []
  }

Cause

• The issue is related to the bug here - JRACLOUD-88282 - Advanced Roadmaps Showing "1" Change to Review but No Changes and JPOSERVER-1527 - Uncommitted changes indicator shows changes, but none are visible in commit dialog
  
  

Solution

Option 1 (recommended): follow the workaround 2 in JPOSERVER-1527 - Uncommitted changes indicator shows changes, but none are visible in commit dialog

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"

Option 2: delete the scenario entry from the database

Please backup Jira data before proceeding with the fix in a production environment. We strongly recommend cloning production data in a test environment to do the experiment.

1. In the rest/jpo/1.0/scenarios/commit response, look for the issue id. In the response, we should find the issue id = 14766889

   "issues": {
         "14766889": {
           "lastChangeTimestamp": 1684130276138,
           "lastChangeUser": "admin",
           "scenarioType": "UPDATED"
         }

2. Run the following SQL query to find the scenario that contains the issue id: 

   select * from "AO_D9132D_SCENARIO_ISSUES" where "ITEM_KEY" like '%14766889%';

3. If you found the results, stop Jira and we remove the entry to discard the review changes.

   delete from "AO_D9132D_SCENARIO_ISSUES" where "ITEM_KEY" like '%14766889%';

4. Start Jira and check again the plan if you still see the blank review changes.