Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Can I use confiforms to create issues in 2 different Jira Projects at the same time?

Bill Mills September 6, 2024

I have 1 confluence form, with 2 workflows built in.  If question 1 is "Yes" it creates a Jira issue in "Project A", and if question 2 is "Yes" it also creates a Jira issue in "Project B".  

Is this possible, or can only one IFTTT to create a Jira issue be triggered for each form submission?

 

Thanks!

2 answers

Suggest an answer

Log in or Sign up to answer
0 votes
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 11, 2024

Not sure what you mean by billing info - we don’t require any

Please open a support ticket so we can unblock you. Hard to fo it with a pseudocode and screenshots

0 votes
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 6, 2024

Hi @Bill Mills 

Absolutely! You can create as many Jira issues as you like

Just put more ConfiForms IFTTT macros, and define conditions when these should run

Bill Mills September 6, 2024

Thanks @Alex Medved _ConfiForms_ .   

I was just able to get it to work, however there is another issue. 

If the answers to both of the form questions is Yes, and 2 issues are created, can I feed both issue IDs back into separate fields?   I have 1 field that is for IssueTypeA and 1 field for IssueTypeB.  

To do this, I have 2 separate IFTTTs:

 

IFTTT 1:

Event: onCreated

Choose Action to perform: Create/Update ConfiForms Entry

Fire IFTTT action only when this condition/filter is met:  Q1:Yes

Parameters to set on the entry: entryid=[entry.id]&fldIntake1=${iftttResult_JIRAJSON}

 

IFTTT 2:

Event: onCreated

Choose Action to perform: Create/Update ConfiForms Entry

Fire IFTTT action only when this condition/filter is met:  Q2:Yes

Parameters to set on the entry: entryid=[entry.id]&fldIntake2=${iftttResult_JIRAJSON}

 

When I submit a form with question 1 set to Yes, it feeds the Intake1 key back to both of my intake fields.

 

When I submit a form with both questions set to Yes, if feeds Intake 1 key back to the Intake1 field, but I get this error for feeding Intake2 key back:

  • Status: 404 with message: and response: '{"errorMessages":["Issue Does Not Exist"],"errors":{}}'

 

I confirmed that the issue did create in Jira. 

 

Bill Mills September 6, 2024

I tried another test where only question 2 is yes, and I still get the error that the issue doesn't exist, but confirmed that the issue did generate in Jira. 

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 6, 2024

Do you actually have rules that create Jira issues? 

Also, you seems to use the SAME result (JIRAJSON) in both rules you have pasted here... 

Bill Mills September 6, 2024

I do.  And the issues are creating without issue.   It's just feeding the 2nd one back to the confiform that is causing the issue.  

 

There is a slight difference in the rules.  the first one has [entry.id]&fldIntake1 and the other has [entry.id]&fldIntake2.  

Does the start and end parts of the rule (in bold) have to be different as well?

 entryid=[entry.id]&fldIntake2=${iftttResult_JIRAJSON}

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 6, 2024

Do you understand what 

iftttResult_JIRAJSON

this is?

You set the SAME result into BOTH fields - fldIntake1 and fldIntake2

why?

Bill Mills September 6, 2024

I'm self taught, and I guess I don't fully understand the parameters.  I don't fully understand JSON.    Are you able to help me understand how they should be set differently?   Thanks! 

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 6, 2024

This is not about JSON really…

So, it is a reference to some result

Most probably your IFTTT that creates an issue in Jira has been named JIRAJSON

give the second IFTTT which creates an issue in Jira a different name

For example JIRAJSON2

and then have

entryid=[entry.id]&fldIntake2=${iftttResult_JIRAJSON2}

 

Like Bill Mills likes this
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2024

Feel free to open a support ticket with us, Bill, and we can walkthrough the whole configuration, so you understand it better

Like Bill Mills likes this
Bill Mills September 10, 2024

Thanks @Alex Medved _ConfiForms_  for your help with this.  Both of my IFTTT's to create the issues and feed the JIra ID back to the form work, but only for the IFTTT's that are first.  I've created a mock-up to demonstrate the set-up I've used.   Are things in the correct order and placement?Intake Form Design Outline for Atlassian Support Ticket.png

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2024

What do you mean by this?

Both of my IFTTT's to create the issues and feed the JIra ID back to the form work, but only for the IFTTT's that are first. 

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 11, 2024
TAGS
AUG Leaders

Atlassian Community Events