Summary

The `Work Logged` automation trigger fails to fire when time is logged via the "Also log time against" dialog during the Test Session completion flow.

Environment

• Jira Instance: Atlassian Jira Project Management Software (v9.12.12#9120012-sha1:9afad32)
• App Name: Deliver quality working software with Agile testing powered by Capture for JIRA (9.1.2.0)
• Automation Engine: Jira Automation

—

Description

When a user completes a test session and utilizes the native "Test Session" dialog to log time to a Jira issue, the work log is successfully created on the issue. However, the Jira Automation Trigger "Work Logged (Created)" does not detect the event.

This suggests that the app may be using an internal API call or a system-level update that bypasses the standard Jira Webhook events used by Automation for Jira.

Steps to Reproduce

1. Initiate a Test Session from an existing Jira issue.
2. Click Start and allow the timer to run for >1 minute.
3. Click Complete Session.
4. In the post-session dialog, select a Jira issue in the "Also log time against:" field and click Complete.
5. Observe that the work log appears in the Jira issue's "Work Log" tab.
6. Check the Automation Audit Log for any rule using the `Work Logged` trigger.

Expected Results

The `Work Logged` trigger should fire, and any associated automation rules (e.g., syncing to an external system like ServiceNow) should execute.

Actual Results

The work log is created, but the automation rule is not triggered. No entry appears in the Audit Log (not even a "Success" or "Error").

—

Technical Observations

• Audit Log Status: No logs generated for the specific timestamp of session completion.
• Manual Entry Comparison: If a work log is added manually via the "Log Work" button on the same issue, the automation fires successfully. This confirms the issue is specific to the Test Session app's integration.