Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • summary - of text type
  • details - of textarea type


Warning

If you want to setup a similar thing to accept entries and create JIRA issues from anonymous users then take a look at a demo Create Jira issue with webservice connection (available with complete storage format for you to import)


Add default "ConfiForms Registration Control"

...

If using NoFormat macro gives rendering exception in ConfiForms then please remove NoFormat macro and place your JSON directly into the IFTTT macro body. If you have troubles with Confluence editor you can try to work in raw storage format using this plugin https://marketplace.atlassian.com/plugins/com.atlassian.confluence.plugins.editor.confluence-source-editor (by Atlassian). Provided JSON should not include any styling information - this is very important for this integration to work.

 


Warning

Important!

For the fields, which may accept line brakes (new lines), like textarea, wysiwyg editor, you will nee to use a Virtual functions escapeJSON in order to make this mappings between JIRA and ConfiForms to work

Code Block
...
"description" : "[entry.details.escapeJSON]"
...

...

 



Update

Since version 1.15 of ConfiForms you are now able to send attachments to JIRA from ConfiForms when creating a JIRA issue

...

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

Important note: 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

 

...