Automation

Use RequestOps in Jira Automation

Add RequestOps actions to your Jira Automation rules.

ForPeople who can configure Jira Automation rules

Before you startChoose a test request, and make sure the rule runs as a user who can open and change that request.

  1. Open Jira Automation and create or edit a rule.
  2. Add an action and search for RequestOps.
  3. Use "Check RequestOps checklist" to learn what is missing and who the request waits on.
  4. The action tells the rest of the rule who the request waits on (for example the customer, another team or a vendor) and which team or vendor that is. In later steps of the rule these are named waitingOnKind and waitingOnKey.
  5. Other actions start a journey ("Start RequestOps journey") or ask the customer for what is missing ("Ask customer for missing items").
  6. Test the rule on one request before you turn it on.
Settings, then Jira fields and Automation: use requestops in automation. Example data.
RequestOps: Settings, then Jira fields and Automation: use requestops in automation

What you should see

The rule’s audit log shows the RequestOps action and its result.

If something is not right

The rule fails. Open the rule’s audit log and check what the action received and who the rule runs as. If you cannot tell whether a message went out, look at the request before running the rule again, so the customer is not asked twice.

Still stuck? See Troubleshooting, or write to support@unitlane.net.