Why am I getting this message: "Update Jira Issue: missing Jira issue key"

[Bill Mills]

Hi have a Confiform with a total of 14 IFTTT macros to either create or update jira issues. Which ones fire depend on the values of the form fields.   When submitting a new form, it will fire at least 1, at most 2.  I also have 2 IFTTT macros to feed the created ticket IDs back to the confiform. When I'm trying to create a new form entry, I keep getting the error listed in my question:

"Update Jira Issue: missing Jira issue key"

Why would this happen when I'm not trying to update an existing form, but submit a new one?

I've confirmed that all 7 of the create IFTTTs have:

event = onCreated

action = Create JIRA Issue

Jira Issue key = [entry.fldJiraIssue]  (where fldJiraIssue is the form field where the Jira issue key is fed back to)

And I've confirmed that all 7 of the update IFTTTs have:

event = onModified

action = Update JIRA issue

Jira Issue Key = [entry.fldJiraIssue]

In a test version of the form, it seems to work when I have zero existing records.  But as soon as I successfully submit one record, I get the error again. 

I've gone over all of these macros and field names repeatedly, and can't figure out why i'm getting the error.  

Appreciate any insights!

Thanks, 

[Alex Medved _ConfiForms_]

Hi @Bill Mills 

Most probably you have rules that UPDATE record, something like this

And if not configured otherwise the update will trigger an onModified event

You can see what rules are executed and in which order by enabling "debug" mode parameter in your ConfiForms Form Definition macro

Alex

[Liz Tanner]

Hey there, Bill! Hope to help you out with Jira throwing the error message:

"Update Jira Issue: missing Jira issue key". The key evidence is:

• From the info: "have a Confiform with a total of 14 IFTTT macros to either create or update jira issues" and
• You did NOT experience this error when there were zero records, it sounds like a Jira quirk where, if you import a renamed project, the old project key is NOT retained

From this Jira Data Center 10.1 documentation, section Notes for change management:

When you were uploading an exported, renamed the project with existing records, Jira updated your project to the new project key. When you would delete everything out and upload it fresh, there was no new project key for Jira to switch everything to. The old key was retained and your form submission was a success! 

This is a longstanding, 10 yr old issue it looks like too. A couple Atlassian Teammate's also explain the issue's cause, offer some advice, and have a solution for you.

Keeping an eye on this one, this is opposite of what systems usually do!!