...
In this example above "mf" is the file type field in ConfiForms.
Update
Most often when an issue is created you want to know it's KEY and probably saved it back to ConfiForms record
Which is totally possible. The same concept is used as described here: Creating links in original ConfiForms entry to just created page
The KEY is held in the result variable of IFTTT macro execution and it's name totally depends on how many IFTTT's you have on this event
Let's say you have just one IFTTT handler which creates a JIRA issue - then the variable holding the result will be ${iftttResult_0} (indexing starts from 0)
So it is a matter of configuring another IFTTT which will take this result and set it back to some field on your ConfiForms record. See the above mentioned tutorial (Creating links in original ConfiForms entry to just created page) on how to update the record back with data from IFTTT macro execution
| Warning |
|---|
Integration between JIRA and ConfiForms is in experimental mode. We are open to feedback and feature requests: vertuna(at)vertuna.com Also, important to note that the operation in NOT TRANSACTIONAL, this means that the ConfiForms record save operation and creation of JIRA issue is not run in the same transaction and if JIRA issue creation fails the ConfiForms record could still be created. In general all the IFTTT integration operations are not transactional and executed in own scope, independently from ConfiForms internal operations |
...