Why when I trigger off a work item created in Jira, the available conditions are for Confluence?

[Liz Borrelli]

See attached image, here is my example:

I would like to edit/create a page or a database line item in Confluence based on a Jira work item being created. The end to end flow would be: User submits form, form creates work item with form label on it, confluence takes action based on the condition that the form label exists on the work item. 

I.e. I would like the conditions on a Work Item Created in Jira trigger (and all Jira triggers) to allow conditions on work fields or JQL conditions, I can't even think of a use case for the conditions to be confluence related on a Jira trigger. Thank you for considering this idea, and would love to hear of anyone else's creative solutions to such a workflow.

[Bill Sheboy]

Hi @Liz Borrelli -- Welcome to the Atlassian Community!

The conditions shown when adding to the trigger are for the product where the rule is defined, not the trigger.  You are trying to create the rule in Confluence and so Confluence conditions are shown.

Your options are:

• Do not add conditions to the trigger, and instead try adding them later
  • If you just want to test the work item fields, use the Smart Values Condition after the trigger (please see the "please note well" below)
  • There is no JQL Condition in Confluence rules, you could simulate that by calling the REST API with the Send Web Request action to gather the work items, and then use the Smart Values Condition to test the web response
• Create the rule in Jira rather than in Confluence

Please note well: I recommend not using the feature to add conditions to the trigger at this time.  There are known racetrack timing problems with both that specific trigger and the conditions on trigger feature.  The impact is the condition may not work as expected because the work item data may not be available to the rule yet.

For Jira rules, the mitigation is adding the Re-fetch Work Item Data action immediately after the trigger, followed by your needed conditions.

For Confluence rules, there is no mitigation because the re-fetch action does not exist.  Theoretically, one could simulate it by calling the REST API to load the data with the Send Web Request action.

Kind regards,
Bill

[Jayesh Raghuvanshi]

@Liz Borrelli 

You can’t yet filter Confluence automation rules on Jira fields, because Confluence’s “When work item created” trigger only lets you choose Confluence-side conditions (CQL, page-related tests, etc.). The easiest way today is to do the label check in Jira Automation, then call Confluence’s REST API to create or update the page. Here’s an end-to-end pattern:

• In Jira (Project- or global-level) go to Project settings → Automation → Create rule
• Trigger: When: Work item created
• Condition: Advanced compare condition
• {{issue.fields.labels.includes("yourFormLabel")}} = true
• Action: Send web request
• URL: https://your-domain.atlassian.net/wiki/rest/api/content
• Method: POST (or PUT to update an existing page)
• Publish the rule.

Whenever an issue with yourFormLabel is created, Jira Automation will call Confluence’s REST API and create (or update) the page. You can customize the JSON payload to write into a database-style page or append a line to an existing table using Confluence’s storage format.

Thanks
Jayesh R