Jira Automation のトリガー

Every flow starts with a trigger. They kick off the execution of your flows. Triggers will listen for events in Jira, such as when a work item is created or when a field value is changed.

Apply conditions directly to the trigger to add criteria to the entire flow. This will filter which triggers continue your automation.

Triggers can be set to run on a schedule, and can be customized before being applied to a flow.

一般的なトリガー

これらのトリガーは、すべての Jira Cloud 製品で使用できます。

変更されたフィールド値

• 関連するスマート値: {{fieldChange}}

The flow will run when a field value is changed. All system and custom fields are supported by this trigger.

You can use this trigger together with conditions to check the value of fields before performing actions. For example, send an SMS when a work item’s priority changes to greater than high.

When configuring this flow, you can select the fields to monitor for change, or use a regex to match the field names. You can narrow down the fields to monitor by specifying a change type: Value added, value deleted or any changes to the field value. You can also narrow down the work item operations that will trigger this flow – create, edit, transition or assign – or leave it blank to listen to all operations.

フォームを添付

The flow will run whenever a form is manually attached to an existing work item, but also when a form is attached using the Add form API or a form is copied to another work item using the Copy form API.

編集用にフォームを開いた時

The flow will run whenever a form is opened for customer edits on existing work items. For example, there may be times when an agent selects Open for edits on an already submitted form on a work item. This could be the trigger that sends a notification to a customer that they need to resubmit a form. This trigger will run whenever a form is manually opened for edits, but also when a form is opened using the Reopen form API.

フォームの送信時

The flow will run when forms attached to a work item are submitted. When configuring the trigger, you can select any number of forms, which will change how the trigger will act:

• If no forms are selected: the flow will run when any form is submitted.

• If one form is selected: the flow will run when that form is submitted.

• If multiple forms are selected: the flow will only run when all of the selected forms on a work item are submitted.

フォームのステータスに関する詳細をご確認ください

受信 Webhook

• 関連するスマート値: {{webhookData}}

The flow will run when a HTTP POST is sent to a specified webhook URL.

A webhook is a way for a third-party to trigger an automation flow. The webhook can specify work items to act on, or even provide real-time data you can use to update a work item.

When configuring this trigger, you’ll receive a unique URL and secret that you can either add to the third-party application’s outgoing webhook configuration, or make a HTTP POST request from your custom scripts. The trigger also provides details on how to provide work item keys and other data.

You can use the {{webhookData}} smart value to reference the custom XML data provided by the webhook in your flow.

作業項目が割り当てられました

• 関連するスマート値: {{assignee}}

The flow will run when the Assignee of a work item is changed. For example, when a work item is assigned to a specific user, change the work item’s status to In progress and send an email to the reporter to let them know it’s being investigated.

作業項目にコメントが追加されました

• 関連するスマート値: {{comment}}

The flow will run when a new comment is added. For example, change the status to In progress when a new comment is added on a work item.

Choosing a comment type allows you to distinguish if a comment was added stand-alone, or as part of a transition. For example, you may want to set an automation flow where a comment added to a closed work item re-opens, or a comment added transitions the status of the work item. The available comment types are:

• All Comments (default): All comments that are added to a work item.

• コメントが主なアクション: 新しいコメントはコメント セクション内でメッセージとして追加されます。

• Comment added during status transition: Comment is added when you change the status of a work item.

• Comment added while editing work item fields: Comment added while editing one or more work item fields.

Editing a comment will not trigger this flow.

作業項目のコメントが編集されました

• 関連するスマート値: {{comment}}

This flow will run when a comment is edited. Can be used with the Edit comment action.

作業項目が作成されました

• 関連するスマート値: {{issue}}

The flow will run when an work item is created.

You can use this trigger with actions to customize the new work item, including populating fields, assigning to users, and adding sub-tasks.

作業項目が削除されました

• 関連するスマート値: {{issue}}

The flow will run when a work item is deleted. For example, send an email notification that a work item has been deleted.

You can use conditions to refine exactly the work item you are monitoring.

Work item linked

• 関連するスマート値: {{destinationIssue}}、{{linkType}}

The flow will run when a work item is linked to another work item.

このトリガーはどのリンク タイプがベースでも構成できます。

Work item link deleted

• 関連するスマート値: {{destinationIssue}}、{{linkType}}

The flow will run when a work item is unlinked from another work item.

You can configure the trigger to only execute for specified link types, or for all work item links.

作業項目が移動されました

• 関連するスマート値: {{issue}}

The flow will run when a work item is moved from one space to another.

You can use this trigger together with conditions and actions to ensure all values, fields and settings are copied across to the new space.

Work item transitioned

• 関連するスマート値: {{issue}}、{{changelog}}

The flow will run when a work item transitions from one status to another.

このトリガーは、選択したステータス、あるいは単純にワークフローのトランジションすべてをリッスンするように構成できます。

Learn more about transitioning a work item with automation

作業項目が更新されました

• 関連するスマート値: {{issue}}

The flow will run when the details on a work item are updated.

Exceptions on this trigger include changes made by the Link work item, Assign work item and Log work actions.

To trigger a flow when a work item’s status is updated, please use the Work item transitioned trigger instead.

Manual trigger from work item

• 関連するスマート値: {{issue}}

The flow will run when it is manually triggered by a user. This trigger is useful for automating common tasks, or testing or debugging a flow. Learn more about using the Manual trigger to test flows

You can refine which users can manually trigger a flow by selecting a permissions group in the Groups that can run trigger dropdown. Learn more about permission groups

You can also request input before a flow is run by selecting Get input from users. This allows you to set up some fields that will display to users when they trigger the flow. You can choose to make each field mandatory by selecting Required field. If a user chooses not to enter any information and selects Cancel, this won’t count as an execution towards your monthly limits.

Once a flow is created with a Manual trigger, anyone with access will be able to trigger it by going to a work item and selecting Actions.

Multiple work item events

• 関連するスマート値: {{issue}}

The flow will run when one or more selected work item events occur. For example, send a Slack message when a work item is updated, transitioned or assigned.

Using this trigger may be easier and more efficient than creating several different flows.

作成されたスペース

• Related smart values: Automation smart values – spaces

Flow will run when a space is created. For example, this could be useful if you want to create a set of default work items that should be included in all Jira spaces.

スケジュール済み

• 関連するスマート値: {{issue}}

This flow runs on a specified schedule. You can run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules.

You can also choose to enter a JQL query. If you do, actions in this flow will execute on the work items included in the query.

Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically.

作業のログ記録

• 関連するスマート値: {{worklog}}

This flow will run when a work log is created, updated and/or deleted.

ソフトウェア トリガー

次のトリガーは、Jira でのみ使用できます。

作成済み、開始済み、または完了済みのスプリント

• 関連するスマート値: {{sprint}}

The flow will run when a sprint is created, started or completed on the selected scrum board.

This trigger will either run for every sprint on that board, or you can narrow this down using a regular expression.

You can use this trigger together with the related work items branch Work item fixed in version to loop through all work items fixed in this version.

バージョンの作成、更新、リリース

• 関連するスマート値: {{version}}

The flow will run when a version is created, updated or released.

You can restrict which versions will trigger this flow using a regular expression.

[バージョンを更新] トリガーはバージョンの作成やリリース、および変更をリッスンします。このトリガーは、バージョンがかかわるすべてのイベントをリッスンする必要がある場合に使用してください。

You can use the Version released trigger together with the related work items branch Work item fixed in version to loop through all work items fixed in this version.

DevOps トリガー

These triggers are only available for Jira Cloud when integrated with a source code management tool. Check out the list of compatible tools

Self-hosted or On-Premise tools (e.g. Bitbucket Server, Gitlab On-Premise, Github Enterprise) aren't supported. Though they can still be integrated with Jira Cloud and you'll still get the benefits of integrating in other parts of your software space.

作成されたブランチ

• 関連するスマート値: {{branch}}

• Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

You can use conditions to refine the branches you are monitoring with this trigger. The flow will run when a branch is created. For example, when a branch is created that includes a work item key, transition that work item to In progress.

build failed

• Related smart values: Smart values - development

• Connect your source code management tool to use this trigger. Visit the marketplace to integrate your build tool with Jira Cloud.

Flow executes when a build fails. You can configure this flow to only trigger on certain build names, or builds associated with certain branches or tags.

ビルド ステータスの変更

• Related smart values: Smart values - development

• Connect your source code management tool to use this trigger. Visit the marketplace to integrate your build tool with Jira Cloud.

Flow executes when the status of a build changes. You can configure this flow to only trigger on certain build names or builds associated with certain branches or tags.

ビルドの成功

• Related smart values: Smart values - development

• Connect your source code management tool to use this trigger. Visit the marketplace to integrate your build tool with Jira Cloud.

Flow executes when a build succeeds. You can configure this flow to only trigger on certain build names or builds associated with certain branches or tags.

作成されたコミット

• 関連するスマート値: {{commit}}

• Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The flow executes when a commit is created. You can use conditions to refine the commits you are monitoring with this trigger.

Compass で作成されたコンポーネント

• 関連するスマート値: {{component}}

  • 開発スマート値の詳細についてはこちらをご確認ください。

The Component created in Compass trigger will cause your flow to run when a component is created in Compass.

You must already have access to a Compass site in order to use this trigger. Discover Compass

You’ll be prompted to set up a connection to Compass the first time you use this component. Read more about connections

Compass でのスコアカード ステータスの変更

• 関連するスマート値: {{scorecard}} {{component}}

The Scorecard status change in Compass trigger will cause your flow to run when a scorecard changes status in Compass.

You must already have access to a Compass site in order to use this trigger. Discover Compass

You’ll be prompted to set up a connection to Compass the first time you use this component. Read more about connections

デプロイの失敗

• Related smart values: Smart values - development

• Connect your source code management tool to use this trigger. Visit the marketplace to integrate your deployment tool with Jira Cloud.

Flow executes when a deployment fails.

デプロイメント ステータスの変更

• Related smart values: Smart values - development

• Connect your source code management tool to use this trigger. Visit the marketplace to integrate your deployment tool with Jira Cloud.

Flow executes when the status of a deployment changes.

デプロイの成功

• Related smart values: Smart values - development

• Connect your source code management tool to use this trigger. Visit the marketplace to integrate your deployment tool with Jira Cloud.

Flow executes when a deployment succeeds.

プルリクエスト作成

• 関連するスマート値: {{pullRequest}}

• Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The flow executes when a pull request is created. You can use conditions to refine the pull requests you are monitoring with this trigger. For example, when a pull request is created that includes a work item key, transition that work item to In review.

pull request declined

• 関連するスマート値: {{pullRequest}}

• Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The flow executes when a pull request is declined. You can use conditions to refine the pull requests you are monitoring with this trigger.

プルリクエストのマージ

• 関連するスマート値: {{pullRequest}}

• Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The flow executes when a pull request is merged. You can use conditions to refine the pull requests you are monitoring with this trigger.

セキュリティ トリガー

脆弱性の検出

• 関連するスマート値: {{vulnerability}}

• Connect a security tool to your space to use this trigger. Learn more about integrating security tools

Flow is run when a vulnerability in one of your connected security containers is found by your security tool and sent to Jira.

Only vulnerabilities that match a severity you choose will activate the flow, you can choose one one or more severities in the trigger.

Jira Service Management トリガー

アラートが作成されました。

• 関連するスマート値: {{alert}}

The flow will run when an alert is created. You can use this trigger to perform actions on Jira Service Management when an alert is created.

たとえば、アラートが作成されたときに Jira Service Management でインシデントを作成したり、アラートを進行中のインシデントに関連付けたりします。

アラートからの手動トリガー

• 関連するスマート値: {{alert}}

The flow is run when it is manually triggered by the user from Actions on an alert. For example, run an SSM document if the alert description contains certain keywords when the user manually triggers the flow.

Users that can flow this flow: By default, your flow can be run by all logged-in users, but you can allow only specific users and members of a team to run your flow.

Filter alerts to show this flow: You can make your flow available to be run only for certain alerts by choosing alert fields to filter by.

Optionally, you can select Prompt for input when the flow is triggered if you want the user, who triggers the flow from an alert, to input any information before the flow is run.

アラートの更新

• 関連するスマート値: {{alert}}

The flow is run when an alert’s priority, summary, or description is updated. For example, create an incident of P3 priority in a service space when an alert’s priority changes to P1.

アラート ステータスの変更

• 関連するスマート値: {{alert.status}}

The flow will run when an alert’s status changes. For example, send a message to a Slack channel when an alert’s status changes to OPEN.

アラート メモが追加

• 関連するスマート値: {{alert.note}}

The flow will run when a new note is added to an alert. For example, send an email when a note is added to an alert.

オブジェクト トリガー

For Jira Service Management only. Flow is run when an object from a specific Assets schema is created, updated, or deleted. This can only be used for global automation flows.

Jira Service Management のアセットに関する詳細をご確認ください。

Attribute value changed

• 関連するスマート値:

  • {{attributeChangelog.(attribute name).from}}

  • {{attributeChangelog.(attribute name).to}}

  • {{attributeChangelog.(attribute name).changeType}} 

  • {{containerObject.(attribute name)}}

For Jira Service Management only. Flow is run when the selected attribute changes on any object of this type. This can only be used for global automation flows.

Jira Service Management のアセットに関する詳細をご確認ください。

サービス上限の超過

• 関連するスマート値: {{breachedSummary}}, {{breachedRules}}

The flow will run when the daily or hourly processing time service limit is about to be breached (note that it doesn’t monitor other types of services limits, such as the “Items queued globally” limit). Read more about automation service limits

SLA しきい値の違反

• 関連するスマート値: {{issue}}

The flow will run when a Jira Service Management SLA has breached or is about to breach.

このトリガーを使用すると、カスタマーへのタイミングの良いフィードバックの提供、エージェントへの警告、リクエストの適切な優先付けの自動化が可能になります。監視する SLA と、違反したときにトリガーするタイミング (違反の前後) を選択できます。

承認が必要

For Jira Service Management only. Flow is run when a work item that requires approval is created or updated, or when new approvers are added to a work item. Learn more about approvals in Jira Service Management. 

承認完了

For Jira Service Management only. Flow is run when an approval step on a work item is accepted or declined. Learn more about approvals in Jira Service Management.

Slack メッセージへの絵文字リアクション

Flow is run when a user reacts with an emoji to the work item created by Assist in Slack.

Currently, the trigger works only with work item messages created by the Atlassian Assist app in Slack channels. Learn more about chat

Since this trigger uses the Slack workspace and channels you set up in chat settings, it won’t work unless you connect this service space to a Slack workspace and channel. Learn how to set up chat in Slack

デザイン トリガー

Design linked to work item

The flow will run when a new Figma design is linked to a work item. Learn how to integrate Figma with Jira

You can use this trigger to add a DESIGN-LINKED label to the work item, and notify the assignee that a design has been added.

リンクされたデザインが更新されました

The flow will run when a design already linked to a work item is updated.

このトリガーを使用して、デザインが更新されたことを担当者に通知できます。

リンクされたデザインのステータスが変更されます

The flow will run when the status of a design that’s already linked to a work item changes.

You can use this trigger to notify the assignee when a design status has changed, automatically add a status label, or transition the work item to the next status.

Atlassian Guard トリガー

Loom トリガー

Loom がフォルダーに移動された

• 関連するスマート値: {{loomVideo}}

This trigger runs your flow when a Loom video is moved to a Loom folder.

Loom がスペースに移動された

• 関連するスマート値: {{loomVideo}}

This trigger runs your flow when a Loom video is moved to a Loom space.

Loom によってミーティングが録画された

• 関連するスマート値: {{loomVideo}}

This trigger runs your flow when a meeting(s) is recorded by Loom.