Rendering dynamic Jira issues macro using IFTTT in Confiform

Peter Baschan

Hi,

I am trying to create a JIRA issues macro on a page created by the 'Create page' IFTTT following a form submit. I can create a Jira search URL that contains field references, something like:

https://servername/jira/issues/?jql=labels%20%3D%20[entry.label]%20ORDER%20BY%20key%20ASC

If I add this link to the body of the Create Page IFTTT, the system recognises it and turns it into a Jira issues macro, which will be replaced correctly when the page is created. Great stuff.

However, I cannot set the list of columns to be displayed as the standard editor gets disabled (when I open the Jira macro) due to the JQL query being not a valid one.

Is there a way to set the list of columns (=Jira fields) to be displayed alongside the dynamic URL?

I don't have access to the source code editor view, so I can't add the parameters manually, I am restricted to what I can do on the standard UI.

I am aware of an IFTTT called Render (execute) macro, but I don't know how to use it, or it would help me in the first place.

I am using Server edition.

Thank you!

Peter

Anwesha Pan

Hi @Peter Baschan

Since you do not have access to the Confluence Source Editor plugin, here are the few standard UI methods to define the columns alongside your dynamic query:

• Method 1: Use native "Insert Markup": Confluence Server includes a native Wiki Markup converter in the editor toolbar. It constructs the macro parameters directly without triggering the live JQL validator check.
  • In the Create page IFTTT action body editor, position your cursor where you want the macro.
  • In the editor toolbar, click the + (Insert more content) dropdown and select Markup.
  • Set the dropdown to Confluence Wiki.
  • Paste the macro syntax with your query and comma-separated column list:
    {jira:jqlQuery=labels = [entry.label] ORDER BY key ASC|columns=key,summary,type,status,assignee,priority,created}
  • Click Insert.

Note: Use standard lowercase identifiers for column names

• Method 2: Embed the columns in the URL: When Confluence auto-converts a pasted Jira URL into a macro, it parses the query string parameters. You can supply the columns parameter directly in your URL before pasting:
  https://servername/jira/issues/?jql=labels%20%3D%20[entry.label]%20ORDER%20BY%20key%20ASC&columns=key,summary,status,assignee,priority
  • Construct the URL with &columns=column1,column2,column3.
  • Paste it into the IFTTT body editor.
  • Confluence will convert it to a Jira macro with the column configuration pre-populated.
    
• Method 3: The "Valid Query First" UI workaround: If you prefer to configure columns using the graphical picker:
  • Insert a standard Jira Issues Macro using a valid dummy query (e.g., labels = test ORDER BY key ASC).
  • Because the query is valid, click —> Display options at the bottom of the dialog.
  • Select your columns, adjust ordering, and set the issue display count.
  • Click Insert to place the macro on the page.
  • In some versions of Confluence Server, you can edit the macro, update the query to labels = [entry.label] ORDER BY key ASC, and click Insert/Save immediately without clicking the "Search/Validate" button so the previously saved columns remain intact. (Note: If the "Insert" button becomes disabled immediately upon typing, use Method 1 or 2 instead).

The ConfiForms Render (execute) macro IFTTT action is designed to evaluate and run a macro on the server during the event lifecycle and return the static HTML output. It runs a macro dynamically (evaluating tokens like [entry.label]), captures the resulting HTML table, and saves it into a ConfiForms field or sends it in an email notification.

If you use "Render (execute) macro", the created page will receive a static HTML snapshot of the Jira issues at the exact moment of form submission. It will not update when Jira issues change. Embedding the Jira Issues macro using Method 1 or Method 2 creates a live, dynamic macro on the generated page that refreshes automatically as issues update in Jira.

I hope this answers your question. 🙂

Thanks,
Anwesha