Forge webhook `avi:jira:created:worklog` not firing when "Manage Access" restriction is enabled on issue

Forge
, , , ,
1

Hi team,

I have a Forge app with this trigger:

trigger:

  • key: worklog-created
    endpoint: worklog-created-event
    events:
    • avi:jira:created:worklog

Problem:
When the “Manage Access” restriction feature is ENABLED on an issue,
the webhook avi:jira:created:worklog does NOT fire after creating
a worklog via REST API POST /rest/api/3/issue/{issueIdOrKey}/worklog.

When “Manage Access” is OFF → webhook fires correctly, BUT there is
a delay issue: if you log work immediately after turning OFF the feature,
the webhook still does NOT fire. You need to wait ~4-5 minutes,
reload the app, then log work again for the webhook to fire.

Expected behavior:
Webhook should fire regardless of whether “Manage Access” restriction
is enabled or not, as long as the app has sufficient permissions.

App permissions (manifest.yml):

  • read:jira-work (allowImpersonation: true)
  • write:jira-work (allowImpersonation: true)
  • read:issue-details:jira (allowImpersonation: true)
  • (and other relevant scopes)

Question:

  1. Does “Manage Access” restriction filter/block Forge event dispatching?
  2. Is this a known limitation or a bug?
  3. Is there a workaround to receive worklog events on restricted issues?

Thanks!