As a support manager, I want to allow users the ability to submit a form using Forms for Confluence which will be sent to ScriptRunner on a JIRA instance. Once received, ScriptRunner creates a new issue with the information submitted. The form submission must also be recorded locally in Confluence in the internal database.
This scenario describes the situation where a submitted form can be handled in the usual way and then submitted to ScripRunner for Jira where some processing can be done on the submitted form and an issue created.
Please note the following instructions are for demonstration. Each Confluence and Jira instance can have their own security policies and custom configurations that should be taken into consideration. This is just a small demonstration of what steps would be required to get basic functionality working. The powerful combination of ScriptRunner for Jira and Forms for Confluence is capable of much more.
In this step we set up an application link that will link Confluence and Jira.
A success message should be displayed, and the application link will appear.
Our custom endpoint is below with imports omitted. It captures the submitted form which contain the following fields: project, summary and description. The issue is then created and a message sent back to Confluence which the user who submitted the form will see as an info message.
Note that all responses from ScriptRunner as above in the info message, will be saved in the internal database for Confluence through the associated Form Id. This can be accessed by navigating to Confluence Administration > General configuration > Forms for Confluence > ScriptRunner Responses.