Application Role intermittently sends false-negative notifications on Smart Commit actions

Issue Summary

Application Role intermittently sends false-negative notifications on Smart Commit actions.

Steps to Reproduce

1. Connect Jira to a Bitbucket server instance.
2. Create a user with WORK_ON_ISSUES permission in a project. Grant this permission using the Application role (Any logged-in user). (You can user Permission Helper to make sure that the user is getting the permission by Application role only.)
3. Create commit(s) with smart commit commands such as the time command which lets you log time to a Jira Issue.. (See this for more info.)
4. Push the commit(s) to the bitbucket server instance.
5. You will see that on very rare occasions commands fail. You will receive an email saying that “<user-name>, you do not have permission to associate worklog to this issue.”

Expected Results

The false-negative notifications won't be sent.

Actual Results

You will receive an email saying that “<user-name>, you do not have permission to associate worklog to this issue.”

Workaround

This issue can be mitigated through group-specific permissions. However, this shall yet affect site-admins as these users will still be considered on using an Application Role.