Problem

Since AP-2450, decisions in Activity show the channel they were made through. The "Started" action shows no channel, so an admin cannot tell whether an approval was started manually, by an Automation rule, by a workflow transition, through the Web API or by a page update.

For approvals started by an event, the admin sees only the start time. When an approval appears late, there is no way to tell whether the event reached Approval Path late or took long to process. Today this needs a support request and a log check.

Change

• The "Started" action in Activity shows how the approval was started, under the action, the same way decisions show their channel:

  • "manually": started or rerun from the panel, including the Confluence "Rerun approval based on the current definition" button and JSM customers starting from the portal;

  • "via workflow post function";

  • "via Automation";

  • "via Web API";

  • "via page update": rerun automatically after a Confluence page update;

  • "after validity expired": relaunched because the approval's validity expired;

  • "via Rovo" and "via Rovo (another agent)": unchanged.

• For approvals started by an event (workflow post function, Automation, page update), Activity shows "event received" with the time Approval Path received that event, under the channel.

• The time uses the same format and time zone as other dates in Activity.

• The "Started" row in the approval panel shows the same channel, without the event time.

• Activity CSV export: the Channel column uses the same words as Activity ("Manually", "Workflow post function", "Automation", "Web API", "Page update", "After validity expired"), and a new last column "Event received" holds the event time.

• JSM customers see the channel under "Started" in the portal Activity, but not the event received time.

• Decisions made in the panel stay unlabeled, as today.

Acceptance criteria

• An approval started manually from the panel shows "manually" on "Started" and no event time.

• An approval started by a Jira Automation rule shows "via Automation" and the event received time.

• An approval started by a workflow post function shows "via workflow post function" and the event received time.

• An approval started through the Web API shows "via Web API" and no event time.

• An approval rerun automatically after a Confluence page update shows "via page update" and the event received time.

• An approval rerun with the Confluence "Rerun approval based on the current definition" button shows "manually".

• An approval relaunched after its validity expired shows "after validity expired".

• If the start waited to be processed, the event received time is earlier than the start time and both are visible.

• The Activity CSV export shows the same channel in the Channel column and the event time in the "Event received" column.

• A JSM customer sees the channel under "Started" in the portal Activity, but no event received time.

• Approvals started before this change display in Activity as they do today.

Manual tester notes

• Jira, work item panel: start an approval. In Activity, its "Started" row shows "manually" and no event time.

• Jira, workflow: add the Approval Path post function that starts an approval to a transition, then make the transition. In Activity, "Started" shows "via workflow post function" and "event received" with a time no later than the Date column.

• Jira, Automation: create a rule with the Approval Path action that starts an approval and run it. In Activity, "Started" shows "via Automation" and the event received time.

• Confluence: use a definition with "Approve the current version of the page" on and "Re-approval statuses" that include Approved. Approve the page, edit it, and check that the new approval's "Started" row shows "via page update" and the event received time. On an outdated approval, use "Rerun approval based on the current definition" in the panel: the new approval shows "manually".

• Validity: use a definition with a short validity period and "Relaunch approval (same definition version)" on expiry. After it expires, the relaunched approval shows "after validity expired".

• Export Activity to CSV: the Channel column shows the same words as Activity and the "Event received" column holds the event time for event-started approvals only.

• The approval panel's "Started" row shows the same channel as Activity, without the event time.

• JSM portal: start an approval as a customer. The customer's Activity shows "manually" under "Started". For an approval started by a workflow or Automation rule, the customer sees the channel but no "event received" line, while an agent in Jira sees both.

• An approval started before the deploy shows no label under "Started", in Activity and in the panel.