Create Jira Issue with Confiforms with the project Key as an input field for the IFTTT

[Michael L]

I want to create a Jira ticket using Confiforms. I want the Project Key not to be defined in the IFTTT. Instead, I hope to have the user input the key and create the issue in their Jira Project. 

Is this achievable? 

[Alex Medved _ConfiForms_ · Accepted solution]

Hi @Michael L and welcome this community

Every project in Jira is unique, and has different fields and issue types

That is why ConfiForms has a Jira issue mapper that can help you to define the mappings for different projects/issue types.. and you will need to do that for every project/issue type you want to support in your ConfiForms form to create a Jira issue

Alex

[Michael L]

Is there a way to capture the Jira key in one form in confluence and then use that in another form to create a Jira Issue? 

[Alex Medved _ConfiForms_]

Not sure I understand what you want to do. You can obviously ask for the Jira issue key in the form's input fields... but what do you want to do with it and how the "other form" should know what has been captured in the first form?

[Michael L]

I would like to use confiforms to create a Jira Issue, however that Jira Issue/ticket can be in multiple projects. I would like the user to indicate which project they will be creating the jira issue in. 

I'm following this guide: https://wiki.vertuna.com/display/CONFIFORMS/Creating+Jira+issue+from+Confluence+with+ConfiForms 

The only problem is the Jira issue can be created in different projects, so I can't define the project key in the IFTTT

[Alex Medved _ConfiForms_]

OK, then ask the project key in the form

and set up the mapping to read the project key from that field via [entry.field_name] reference

But as noted before, you cannot have one unified mapping to create issues in different projects, as usually projects in Jira have unique configurations, issue types and custom fields...

Alex

[Michael L]

Thanks!  When I try mapping the field to the project key, I get an error message. 

{ "fields":{ 
"project": 
{ "key": "[entry.key]" 
}, "summary": "[entry.summary]",      
"description": "[entry.details]", 
"issuetype": { "name": "[entry.issuetype]" 
}, 
"priority": { "name": "Minor" } 
} 
}

Error communicating with Jira, Bad Request 

[Alex Medved _ConfiForms_]

What error message do you get?

[Michael L]

Error communicating with Jira, Bad Request 

• com.atlassian.sal.api.net.ResponseException: Error communicating with Jira, Bad Request {"errorMessages":[],"errors":{"summary":"You must specify a summary of the issue.","description":"Description is required."}}

[Michael L]

im missing a field. I think I got it thanks!

[Nic Brough -Adaptavist-]

You cannot impose an issue key on Jira, the only way it can work is for Jira to generate a new one when a new issue is created.