How do I implement a template for Jira integration

[HHH]

Hi

Just calling on the collected expertize of the community to help me get Atlassian Integration working.

What i'm trying to do is use the Business Process and integration bridge to create a form/template that contains information that will be pushed to Jira. Something like this.

• Hornbill Request ID: (Taken from Flowcode variable)
• Steps to reproduce: (Here the Analyst fills in the steps necessary)
• Expected Result: (Here the Analyst fills in the info)
• Actual Result: (Here the Analyst fills in the info)

The contents of the form would then be added to the Description Field in the Integration Parameters (see attached screenshot)

First I just used the Description Flowcode Information but R&D blocked it since the quality of the created Jira was too low and they wanted something along the lines above.

Any help is appreciated.

 

[Dan Munns]

You could have the required fields on a PC form and then do this in the description with an update request details node: 

• Hornbill Request ID: (Request_ID_Variable)
• Steps to reproduce: (PC_Question_1_Variable)
• Expected Result: (PC_Question_2_Variable)
• Actual Result: (PC_Question_3_Variable)

[HHH]

17 minutes ago, Dan Munns said:

You could have the required fields on a PC form and then do this in the description with an update request details node: 

Can I open a new PC from within a Request or would I need to make a linked request?

[Dan Munns]

It would need to be a linked request to use a new PC. 

Or you could use tasks and use the reason variable to add text to the description.

[HHH]

1 hour ago, Dan Munns said:

Or you could use tasks and use the reason variable to add text to the description.

This worked as intended. Do you know if it's possible to inject some template text into the reason field?

[Dan Munns]

Not that I know of unfortunately.

You could add the template text into the task description with the instructions to copy and paste it into the reason field. 

Or have 1 task per field and use the reason for each as a separate variable.

• Hornbill Request ID: (Request_ID_Variable)
• Steps to reproduce: (Task_1_Reason_Variable)
• Expected Result: (Task_2_Reason_Variable)
• Actual Result: (Task_3_Reason_Variable)