| ConfiForms TableView |
|---|
| plain jiraKeyMaster key jiraKeyMaster.asJSON.key key.asJSON.key jiraKeyMaster.asJSON.key.asJSON.key |
form is set to allow anonymous submissions form has it's own fields as usual, plus a Jira issue field (that the user doesn't / shouldn't see, i.e. don't include it in the registration macro) form has 3 IFTTTs which run when the form is submitted and the record is created - the first one runs when the record is created and creates a Jira issue using a web service action (web services are configured in admin area of confluence and should use a service account as credentials, i.e. don't not use the 'create Jira issue' action); the json within the IFTTT is what creates the ticket in the right place in Jira with the right info; the ticket is created and the new Jira ticket ref is sent back to this form as the IFTTT result (which you ideally should give a var name to in the IFTTT config)
- the second IFTTT - of type text - also runs when the record is created but after the first IFTTT because of their placement, updates the 'jiraMasterAsText' issue field in the newly created record when it gets the Jira ticket json response back from the first IFTTT (which you can reference using the var name from the first IFTTT result, prepended with iftttResult_); it must have 'Bypass field restrictions and record ownership status' ticked since the person using the form is anonymous and isn't allowed to update fields in an existing record
- the third IFTTT - of type Jira - which also runs on create and after the first two due to placement, is similar - it reads the json text value from the newly populated jiraMasterAsText field and extracts just the json from it and saves it
For info, it is not possible to combine steps 2 and 3 (like you can if using the IFTTT create Jira action); this has been confirmed by the developer. |