Confiform creates Jira issue - trying to display the issue key back to the user

[Nat Grauman]

Confluence Cloud.  I have a confiform that creates a new jira issue.  I can't get it to display the issue key in the Success message.  Rovo has been helping me and appears to be stumped.  S/he keeps saying "I understand what's happening clearly now" and offers me the same solution we tried 5 attempts ago.   I know this is surely a basic thing and I must be overlooking something simple. Here's my entire config (courtesy of Rovo of course):

Here's the full config summary ready to copy/paste for Alex Medved:

ConfiForms Setup — Banking COE Engagement Form
Confluence Page: Banking COE Engagement Form (Space: CONB, Page ID: <page-id>)

FORM DEFINITION MACRO (confiform)

• formName: <key>
• registrationFormTitle: Banking COE Engagement Request
• saveButtonLabel: Submit
• additionalFormAdmins: <username>
• formSuperUsers: <username>
• bypassAttachmentCreatePermission: true

Fields:

- Requestor (user, required)
- Products (multi, required) — extras: label;false
- Workstream (select, required) — extras: label;false
- Summary (text, required)
- Priority (select, required)
- ORE (select, required)
- OREetcID (text, optional) — shown/hidden via field-definition-rules
- DueDate (date, required) — extras: d/MMM/yy
- Requirements (textarea, required)
- IssueKey (text, hidden) — stores returned Jira key

IFTTT MACRO #1 — Create Jira Issue

• formName: <name>
• action: Create JIRA Issue
• event: onCreated
• resultName: IssueKey
• extras (Jira server ID): <server-id>
• Body (JSON payload):

{
  "fields": {
    "project": { "key": "<key>" },
    "summary": "[entry.Summary.label]",
    "labels": [[entry.Products.asArray]],
    "components": [{"name":"[entry.Workstream.label]"}],
    "priority": { "name": "[entry.Priority.escapeJSON]" },
    "duedate": "[entry.DueDate.jiraDate]",
    "customfield_10408": "[entry.ORE.label]",
    "customfield_10424": "[entry.OREetcID]",
    "description": "Ticket created from Banking COE intake form for [entry.Requestor.escapeJSON] \n Requirements: \n[entry.Requirements.escapeJSON]",
    "issuetype": { "name": "Action" }
  }
}

REGISTRATION CONTROL MACRO (confiform-entry-register)

• formName: <name>
• type: Embedded
• autoenroll: false
• redirectMode: View
• overrideSaveButtonLabel: Submit
• showMessageAs: Below the form
• successMessage: Intake ticket [iftttResult_IssueKey.key] submitted. ← THIS IS THE PROBLEM AREA
• debugMode: false

IFTTT MACRO #2 — Update ConfiForms Entry

• formName: <name>
• action: Update ConfiForms entries by filter
• event: onCreated
• title (update value): IssueKey=[iftttResult_IssueKey.key]
• extras2 (filter): id=[entry.id]

The Problem:
The success message uses [iftttResult_IssueKey.key] — the same variable that works in IFTTT Macro #2's title field. However, the success message renders as "Intake ticket submitted." — the variable is recognized (no literal brackets shown) but resolves to empty. This suggests the IFTTT result is not yet available in the Registration Control's success message context at render time, even though resultName is set to IssueKey in IFTTT Macro #1. The Jira issue is being created successfully.

Rovo's question: is [iftttResult_IssueKey.key] a valid variable in the successMessage parameter of confiform-entry-register, and if so, what is the correct timing/scope for it to resolve?

[Alex Medved _ConfiForms_ · Accepted solution]

Why not to use the [entry.IssueKey] in the "successMessage" parameter instead?

[Nat Grauman]

@Alex Medved _ConfiForms_  - I did that and the success message skipped over the [entry.IssueKey] as if it was empty (which I guess means it was).

[Nat Grauman]

I have a second IFTTT where I set IssueKey=[iftttResult_IssueKey.key] -- is that correct?

[Alex Medved _ConfiForms_]

In the second IFTTT you have an incorrect syntax for the filtering expression

Instead of 

id=[entry.id]

put

id:[entry.id] 

https://wiki.vertuna.com/spaces/CONFIFORMS/pages/1212436/ConfiForms+Filters

[Nat Grauman]

That worked Alex, thanks so much as always - BUT, the success message only appears for a brief moment, then it disappears.   

Behaviour after form submit is set to Form Reload, otherwise the form retains the same values the user just submitted.  

How can the form fields be cleared and the Success Message remain in place until the user submits a new entry or closes?

[Alex Medved _ConfiForms_]

This is how the form behaves when it is set like that. There are no additional options to change this behaviour

[Tomislav Tobijas]

Hi @Nat Grauman ,

As this is a Marketplace app-related question, I’d suggest reaching out to the vendor directly.

For ConfiForms, you can find the available support channels on its Marketplace page. 👈

Alex from the Vertuna team is also active on the Community and may chime in, but it might be quicker to contact their team through the official service desk or request form. 👀

Cheers,
Tobi