How to spot Jira Service Management changes made after approval
I run Bounded Signal Technologies, the Marketplace Partner that publishes Change Decision Evidence for Jira Service Management.
A change request can be approved and then edited later. Jira’s activity history records the individual events, but it can still take a careful manual review to answer a simple question: do the important details still match what was approved?
Compare selected change-request details with the latest completed approval.
Before relying on an earlier approval, a reviewer should identify the latest completed approval, decide which fields define the intended change, reconstruct their values at that
point, and compare them with the current request. A later approval may establish a new comparison point, while incomplete or ambiguous history should prevent a clean conclusion.
Change Decision Evidence is a read-only Jira Service Management app that makes that comparison directly on the request:
1. Open a Jira Service Management change request.
2. Choose the fields that describe the approved work.
3. Compare their approval-time values with their current values.
A changed result shows the approval-time and current values side by sides.
The result shows whether a selected field changed after the latest completed approval that the app can clearly connect to the request’s history. It also shows the approval-time and current values side by side.
If a later completed approval covered the revised value, that later approval becomes the comparison point. If the available Jira history is incomplete or unclear, the result is Cannot
determine rather than a false clean answer.
A later completed approval becomes the new comparison point.
The app runs on Atlassian Forge, uses read-only Jira permissions, and does not send issue data to an external service.
View Change Decision Evidence on Atlassian Marketplace here: