nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ConfiForms IFTTT won't link issues with copy/paste code from confiForm IFTTTthat does

Brian Karst

I am attempting to link two issues in a parent/child relationship, in the troubleshooting of why none of the IFTTTs on my form will link any issues. Yet when another form is used, issues are created and linked with no problems. the IFTTTs on the form won't even link to an already created hardcoded issue. Example JSON below.

"update": { "issuelinks":[{"add": {"type":{"name":"Parent to Child relations", "inward":"is parent of", "outward":"is child of"}, "outwardIssue": {"key":"PLAYSPC-2424"}}}] }

is there something that I am missing?

Accepted answers

All comments

Alex Medved _ConfiForms_

You can enable debug for IFTTTs execution and see if they are executed at all https://wiki.vertuna.com/display/CONFIFORMS/How+to+troubleshoot+and+debug+ConfiForms+IFTTT+rules+execution

Most often we see customers set previous IFTTTs to fail silently (without a report to user) and then scratch their heads to understand why it does not work the way it should

Brian Karst

New Question!

Through trial and error, I found what was preventing the link from happening and I think I know why. We have a Select List (Cascading) custom field that contains the Divisions and Subdivisions that employees could work for. A while ago I got the input for the field working but I think the barbaric way I did it is breaking the ability for it to "upfate"

Searching how to input the ID's in JSON i found the syntax

{"id":"11111", "child":{"id":"22222"}}

So I set up a form with the ID's and set up a smart classifier and enter the code

"customfield_13062": {"id":"[entry.smartdepart.ParentID]", "child":{"id":"[entry.smartdepart.ChildID]"}}

Then I get an error because Jira doesn't like that the child ID is blank. (edited error message below)

com.atlassian.sal.api.net.ResponseException: Error communicating with Jira, {"errorMessages":[],"errors":{"customfield_13062":"Child Option id '' is not valid"}}

Used JSON: "customfield_13062": {"id":"32410", "child":{"id":""}} }} }'

I tried null and I can't remember what else instead of a blank in the form, nothing worked. Eventually I put the code for the child input into the ID in the form and used the code

"customfield_13062": {"id":"[entry.smartdepart.ParentID]"[entry.smartdepart.ChildID]}

where

Parent ID = 11111

and

Child ID = , "child":{"id": "22222"

In my frustrations with the IFTTT not linking issues I started picking it apart and if I hard code an ID or remove the "customfield_13062" line the IFTTT links issues just fine. Is there a better syntax to allow Jira to accept there sometimes being a ChildID and sometimes not?

Alex Medved _ConfiForms_

This is more a Jira REST API specific question that something related to ConfiForms itself.

Or even the documentation for the "Select List (Cascading) custom field" ... is this something standard in Jira or is a 3rd party plugin provided feature?

Brian Karst

Yes and no. the Rest API is fine without the ConfiForm input, if there is no ChildID it seems to just want you to not try to set it, instead of allowing it to be blank/null. But I will definitely seek other assistance. Select List (Cascading) is not 3rd party. There is other documentation I have found on it but

https://developer.atlassian.com/server/jira/platform/rest-apis/

Cascading select custom field: A custom field that allows you to select a single parent value and then a related child value. You can address them by value or by ID.

"customfield_11447" : { "value": "parent_option1", "child": { "value" : "p1_child1"} }

"customfield_11447" : { "id": 10112, "child": { "id" : 10115 } }

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

confiforms