Problem Definition

Due to the roles and permissions structure by DVCS Providers e.g., GitHub, we recommend having owner/admin level authorization for the integration account in our documentation in order for Jira to be able to create the two webhooks per repository for each linked repository:

• Linking GitHub accounts

You need to be logged in as a user with administrative rights to the account in GitHub.

However, we currently don't have any indication in the UI that those two webhooks were indeed created and if they were not created, this is the reason why the Webhook security status in the list of repository is showing up as FAILED

Our documentation Troubleshooting webhook security issues doesn't mention this use case where it's not possible for the Jira Admin to know the reason webhook security status is FAILED is because the repository possibly doesn't even have the webhooks to begin with.

Suggested Solution

• Improve the UI to let admins identify the repos where hook creation failed
• improve the Webhook security status lozenges to signify such repositories (without hooks) differently

Workaround

Make sure the authorizing/integration account on GitHub has the admin level permissions on all linked repositories with DVCS.