webhook の管理

Viewing webhooks in JIRA

To view webhooks in JIRA,

1. 「JIRA 管理者」 グローバル権限 を持つユーザーとしてログインします。
2. Choose Administration at the top right of your screen. Then choose Advanced > Webhooks to open the 'Webhooks' page, which shows a list of all existing webhooks.
   Keyboard shortcut: g + g + start typing webhooks
3. Click the summary of the webhook in the left 'Webhooks' column to display the details of the webhook.

スクリーンショット：JIRA 管理コンソールに表示された Webhook

Managing webhooks via the JIRA administration console

Webhooks can be registered (created), edited and deleted via the JIRA administration console, REST calls or the installation of a "Remote App". The instructions on this page describe how to manage webhooks via the JIRA administration console. Please see the JIRA Webhooks Overview page for information on the other methods.

To manage webhooks in JIRA,

1. Log in as a user with the JIRA Administrators global permission.
2. Choose Administration at the top right of your screen. Then choose Advanced > Webhooks to open the 'Webhooks' page, which shows a list of all existing webhooks.
   Keyboard shortcut: g + g + start typing webhooks
3. Create/register, edit or delete webhooks as desired.
   
   • Create — Click Add a Webhook, enter the webhook details and click Create.
   • Edit — Select the desired webhook in the summary list on the left, click Edit, update the webhook details and click Save.
   • Delete — Select the desired webhook in the summary list on the left, and click Delete in the webhook details.
   • Disable — Select the desired webhook in the summary list on the left, and click Disable in the webhook details. Disabling a webhook prevents the webhook from firing. 
   • Enable (disabled webhooks only) — Select the desired disabled webhook in the summary list on the left, and click Enable in the webhook details.

Screenshot: Adding a webhook

Tips for managing a webhook

• Constraining the webhook to a set of issues/issue events — By default, a webhook will fire for all events of all issues in a JIRA installation. You can constrain this to a set of issues and a set of issue events (or no issue events). To do this, specify the desired set of issues (via a JQL statement) and the set of issue events, when you create or edit a webhook. For example, the webhook in the screenshot above will only fire when bugs with an affected version of "1.0" are updated.
• Omitting the JSON from the POST — If you are integrating with a system where only a POST URL is required to trigger the action, and having a body with data breaks the integration, you can configure the webhook so that it does not send the JSON with the POST. To do this, select the Exclude details checkbox when editing your webhook. 
• Determining the changes in an 'Issue Updated' event — A changelog is sent with the 'Issue Updated' event (excepting the issue_generic_event). You can listen for this event and check the changelog for the changes.

Extending your webhook

Trigger your webhook from a workflow post function

 See Configuring Workflows.

Please note, if a webhook is associated with a post-function, you cannot be delete the webhook. You must disassociate it from the post-function first.

Add an issue key variable to your webhook

You can add an issue key variable to your webhook by inserting ${issue.key} in your webhook URL. When the webhook fires for an issue, the issue key will be substituted for the variable in the URL.

For example, say you have the following web hook URL with the ${issue.key} variable:

http://example.com/bamboo/rest/api/latest/queue/BAMBOO/${issue.key}

If the web hook is fired for a JIRA issue with the key JRA-1234, the URL that the web hooked is posted to will be:

http://example.com/bamboo/rest/api/latest/queue/BAMBOO/JRA-1234

既知の問題

• Post function web hooks will not fire if added to the Create Issue workflow transition. We recommend that you configure your web hook to fire from the issue_created event instead.
• If you are using webhooks in JIRA OnDemand, there is a known issue that restricts the port numbers that can be specified in the webhook URL. If you do not follow the guidelines below, then the webhook will not trigger.
  
  • If you are using HTTP and specify a port number in the webhook URL, the port number must be 80. Note, if you do not specify a port number, the webhook will work.
  • If you are using HTTPS and specify a port number in the webhook URL, the port number must be 443. Note, if you do not specify a port number, the webhook will work.
• If you are using JIRA 5.2.1 or earlier, there are two known issues/limitations when using JQL with webhooks:
  • currentUser() function does not work as expected.
  • A JQL query may not return the desired results, if it is filtering for a field that changes frequently (see the 5.2 Upgrade Notesfor a description of this issue). This means that you should not write a webhook which uses the JQL expression to look for a specific state change.

    For example, if you wanted to POST a webhook anytime an issue was changed to have a Priority of Blocker, you should not include "Priority = Blocker" in the JQL clause, but leave out priority, and filter for those events where Priority was changed to Blocker on the receiving side of the webhook.

• If you are using JIRA 5.2.2 or earlier, there is a known issues when using JQL with webhooks:
  
  • The ${issue.key} variable replacement does not work in a webhook, when the webhook is used in a workflow post function. Note, the ${issue.key} variable replacement does work when an issue event triggers the webhook.