Flattening a Confiforms Record for IFTTT Export to JIRA

Question

I use a Confluence form as the data source for a smart multi-select field on my main form. IFTTT macros then create a Jira story and several predefined subtasks. When the ticket is complete, a checkbox on a dashboard is selected and saved. At that point, I want the system to create one Jira task under the existing story for each value selected in the smart multi-select field. For example, if the story is called “Cars” and the selected values are “Ford,” “Honda,” and “Mazda,” saving the checked box should create three tasks; one for each value; under the “Cars” story. Is this possible using the setup described?

Suppose the source table includes a second column called “Defects,” which is a Jira multi-select field that captures defects associated with each car make in the first column. Can the same checkbox logic also create links from the Story to an issue for each unique defect selected in the source table?

Or do I need to buy Confiforms a few drinks first? 😊

Josh · Answer

Confiforms multi-select / smart multi-select values need an explicit “for each entry” step before you can create one Jira issue per value under an existing story.

Approaches that work:

* IFTTT “Create Jira issue” inside a Confiforms formula / Integration that iterates the multi-select field (Confiforms has “each” / list processing helpers depending on version — often people use a ConfiForms IFTTT with a body that maps [entry.field_name] after splitting, or a separate IFTTT triggered by a helper form row).
* Flatten first: on checkbox save, run an IFTTT that creates one Confiforms record (or storage row) per selected value, then a second IFTTT on those child records that creates the Jira sub-task / task with Parent = the existing story key you already stored.
* Pass the parent story key in a hidden Confiforms field when the story is first created so each later task IFTTT can set Parent reliably.

Native Jira Automation alone usually cannot see Confiforms field internals — keep the loop on the Confiforms side, then create issues via the Confiforms→Jira IFTTT. If you share whether this is Cloud Confiforms and the field type (smart multi-select vs multi-select), someone who’s built the “one task per selected value” pattern can point at the exact IFTTT type name.

Tomislav Tobijas · Answer

Hi @Jason Walsh,

Since this is quite specific to ConfiForms and its IFTTT functionality, I’d recommend reaching out directly to the ConfiForms (Vertuna) support team. 🎟️

They should be able to confirm whether the selected Smart Multi-select values can be iterated over to create individual Jira work items and whether the same approach can be used for linking the unique Defect values. 👀

Hope you manage to get it working - although a few drinks for ConfiForms might still help 😄

Cheers,

Tobi