Skip to main content

Listeners

A listener is a script that runs when something happens in Jira or Confluence, for example when someone creates a work item. Script Master has no listeners. To run your script on an event, use a Jira Automation flow that calls a Script Master web trigger.

Applies to: Script Master for Jira and Script Master for Confluence Β· Cloud

Why Script Master has no listeners​

Script Master once had listeners, and we removed them. On a busy site, events start a very large number of Forge invocations, and Forge limits how many an app may use.

Jira Automation already reacts to these events. It has JQL conditions, branches and an audit log, and it comes with Jira. So Script Master leaves events to Automation and gives your flows a place to run a script.

Use Jira Automation with a web trigger​

  1. A Jira Automation flow reacts to the event, for example Work item created.
  2. Its Send web request action calls the URL of a Script Master web trigger, with the work item's data.
  3. The web trigger's script does the work Automation can't, and answers the flow.

Call a web trigger from Jira Automation walks through a complete flow and script.

In Confluence, Confluence Automation can call a web trigger of Script Master for Confluence the same way.

When the flow alone is enough​

Many listener tasks need no script at all. Setting a field, adding a comment, transitioning a work item and sending a notification are all Automation actions. Add a web trigger only for what the flow can't do on its own. For example, a calculation across many work items, or a call to a system that needs custom logic.