![]() The rule will run when a HTTP POST is sent to a specified webhook URL.Ī webhook is a way for a third-party to trigger an automation rule. The webhook can specify issues to act on, or even provide real-time data you can use to update an issue. When configuring this trigger, you’ll receive a unique URL 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 issue keys and other data. The rule will run when an issue transitions from one status to another. ![]() You can configure this trigger so it listens to the status of your choice, or simply any transition in your workflow. Learn more about transitioning an issue with automation. The rule will run when the details on an issue are updated.Įxceptions on this trigger include changes made by the Link issue, Assign issue and Log work actions. The rule will run when it is manually triggered by a user. You can refine which groups can manually trigger a rule. This trigger is useful for automating common tasks, or testing or debugging a rule. The rule will run when one or more selected issue events occur. For example, send a Slack message when an issue is updated, transitioned or assigned. Using this trigger may be easier and more efficient than creating several different rules. You can run the rule 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 rule will execute on the issues included in the query. Scheduled rules that reach a Failure status for 10 consecutive executions will disable automatically. This rule will run when a work log is created, updated and/or deleted. The following triggers are only available for Jira Software. The rule 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 issues branch Issue fixed in version to loop through all issues fixed in this version. The rule will run when a version is created, updated or released. You can restrict which versions will trigger this rule using a regular expression. The Version updated trigger listens for versions being created and released, as well as being amended. Use this trigger if you need to listen for all events around a version. You can use the Version released trigger together with the related issues branch Issue fixed in version to loop through all issues fixed in this version. The following tools can be used with these triggers: These triggers are only available for Jira Software Cloud integrated with a source code management tool. The following tools can't be used with these triggers, though they can still be integrated with Jira Software Cloud and you'll still get the benefits of integrating in other parts of your software project:Ĭonnect 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 rule will run when a branch is created. For example, when a branch is created that includes an issue key, transition that issue to In progress. ![]() Related smart values: Smart values - developmentĬonnect your source code management tool to use this trigger. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |