Can issuetype in JIRA be auto-populated from Confiforms without hardcoding the value?

[Tanmay Gadkari]

I've designed a form in Confluence using Confiforms that allows users to create a service ticket in a specific JIRA project. The Confiform-JIRA integration works fine when I set the 'issuetype' value to be hardcoded to something like 'Bug' or 'Task'. 

My question is this: 

My form now has a field that allows users to define the issue type. Is there any way I can populate this in the actual 'issuetype' on the JIRA side? I tried the standard [entry.fieldname] option and it doesn't seem to work. Keep getting an error. 

Tried this with the 'Priority' field as well. Doesn't seem to work there too. 

Here's the one that did work: 

{
  "fields": {
    "project": {
      "key": "APCT"
    },
    "issuetype": {
      "name": "Task"
    },
    "labels": ["Requests"],
    "summary": "Request for [entry.Type.label] - [entry.Title]",
    "description": "*Requestor's Name:* [entry.Requestor] \n\n   *Description:* [entry.Description]"
}
}

Any help here will be appreciated. To summarize, I need to populate issuetype and priority values from my Confiform entry and not have them hard-coded. 

[Alex Medved _ConfiForms_ · Accepted solution]

Yes, you can do this, have a look at https://wiki.vertuna.com/display/TEST/Building+a+dropdown+field+in+ConfiForms+backed+by+webservice+call+to+Jira+Rest+API+-+createmeta

[Tanmay Gadkari]

Hi Alex,

Thanks for the input but it doesn't actually answer the question. This link helps me populate a field in my form.  

What I have is a field on my registration form that is already defined and populated using the Confiform Form Field Definition. On my registration form, I see all the values that I defined (these correspond to actual 'issue type' or 'priority' field values in JIRA). I need these values (Issue Type and Priority) to reflect onto the JIRA ticket that is created. 

So what I need to know is if :

"issuetype": {
      "name": "Task"

can be replaced with something like:

"issuetype": {
      "name": "[entry.Type]"

I tried the second example above and it gave me an error saying Issue Type needs to be defined (first one works just fine since the value is hard-coded to Task) .

Same thing when defining the Priority field in the IFTTT Integration rule.

[Alex Medved _ConfiForms_]

Yes, absolutely

"issuetype": {
      "name": "[entry.Type]"

This is possible, as long as [entry.Type] results into a "Task"

What type of field this is in your form?

[Tanmay Gadkari]

Hi Alex,

The field is defined as a dropdown field. I am not quite sure what you mean when you say the field results into a 'Task'. 

I've attached two screenshots to show what the field is defined as and how it appears. 

I know I'm probably doing something wrong since 

"issuetype": {
      "name": "[entry.Type]"

doesn't give me the required result in JIRA. I get an error on the form page itself saying Issuetype needs to be defined. 

Any help here would be greatly appreciated! 

Thank you.

[Alex Medved _ConfiForms_]

Well, you have the type field as a dropdown, and choices have values 1, 2 and 3

When you do the

[entry.Type]

you reference ID of the field, not a label... if you need to have a label then 

[entry.Type.label]

See more on https://wiki.vertuna.com/display/CONFIFORMS/Accessing+field+values+and+properties

[Tanmay Gadkari]

Hi Alex, 

Thanks a lot! The solution worked for both issue type and priority. I think I was very close earlier on but perhaps there was a mismatch between the entries in our dropdown vs the actual JIRA field values. 

All good now... thanks again for all your help!

Cheers!