ConfiForms: Remove blank fields in Jira issue?

[Ian Taylor]

Hi there,

I have a ConfiForm for my communications team that takes intakes and sends them to Jira as issues. 

There are quite a few fields on this form, and several of them are conditional on the team being engaged (eg. The "Event Type" field only appears when selecting "Events" as the team engaged). 

However, ConfiForms currently sends every single field to Jira whenever it creates an issue. The result is that, say, a Communications request will show up with several blank fields pertaining to Events.

Is there a way to hide unused fields (text, checkbox, and date) so that my team will only see relevant information in Jira? 

Here is my code:

{    "fields": {       "project":       {           "key": "WAC"       },

      "issuetype"         : { "name": "Request" },
           
"components"	:	[[entry.TeamEngaged.asArrayOfKVPairs(name)]],						
"customfield_11413":				"[entry.duedate.jiraDateTime]",	
"customfield_18601"	:	"[entry.email]",
"customfield_18600"	:	"[entry.enteredby]",
"customfield_18606"	:	"[entry.LOB]",
"summary"			:	"[entry.InitiativeName.escapeJSON]",




"description": "*Subject Matter Expert:* [entry.SME.escapeJSON] \n *Approved By:* [entry.Approver.escapeJSON] \n \n *Communications: Project* \n *Target Audience:* [entry.TargetAudience.escapeJSON] \n *Communication / Project Overview:* [entry.Communication.escapeJSON] \n *Which strategic priority does this communication align to?:* [entry.StrategicPriority.asArray(_)] \n  \n \n *Communications : Dispatch*  \n *Which weekly communication do you want this featured in? Click all that apply.:* [entry.WeeklyCommunication.asArray(_)] \n *Category:* [entry.Category.asArray(_)] \n *Title:* [entry.Title.escapeJSON] \n *Summary:* [entry.Summary.escapeJSON] \n *Action:* [entry.Action.escapeJSON] \n *Contact:* [entry.Contact.escapeJSON] \n \n *Communications : Bi-weekly Marketing Dispatch* \n *Which weekly communication do you want this featured in? Click all that apply.:* [entry.BiweeklyCommunication.asArray(_)] \n *Title (Marketing):* [entry.MarketingTitle.escapeJSON] \n *Summary (Marketing):* [entry.MarketingSummary.escapeJSON] \n *Action (Marketing):* [entry.MarketingAction.escapeJSON] \n *Publication Date (Marketing):* [entry.MarketingPublicationDate.jiraDate] \n *Contact (Marketing):* [entry.MarketingContact.escapeJSON] \n \n *Event*  \n *Event Type:* [entry.EventType.asArray(_)] \n *Estimated Budget:* [entry.Budget.escapeJSON] \n \n *Colleague Experience / R&R* \n *Initiative Type:* [entry.InitiativeType.asArray(_)] \n *Initiative Pillar:* [entry.InitiativePillar.asArray(_)] \n \n *Additional Information:* [entry.AdditionalInfo.escapeJSON]"
}
}

Thank you.

[Alex Medved _ConfiForms_]

Hi @Ian Taylor 

Welcome to Atlassian community!

You can see here how to check for "values" in fields when constructing your JSON

https://wiki.vertuna.com/display/CONFIFORMS/Configuring+ConfiForms+IFTTT+actions+and+rules#ConfiguringConfiFormsIFTTTactionsandrules-CreateJiraIssue

A more direct link https://wiki.vertuna.com/display/CONFIFORMS/IFTTT+macro+body+evaluates+as+Velocity+template

Alex

[Confi User]

Is there a way to make complex logic in the JSON? Like I have a ton of optional fields that depend on other criteria to be met first.

[Alex Medved _ConfiForms_]

Hi

This is exactly what my previous comment answers... Really hard to add anything

Please see the links mentioned there

Alex