Getting Text of ProForma Multiple Choice Values via Jira Automation

[Andrew K_]

Hello Community,

We are using ProForma to create forms. I am attempting to use Jira Automation to populate the description field of a Jira issue with a number of ProForma form field values. I can get the text values for everything other than multiple choice. 

In referencing the documentation here, https://docs.thinktilt.com/proforma/automation-for-jira-server, it says the text is stored as 

issue.properties."proforma.forms.i1".questions.choices

However, try as I might, I cannot figure out the proper structure to access the text values that were selected.

For example, I've tried this where 2 is the confirmed question ID: {{issue.properties."proforma.forms.i1".questions.choices.2.choices.get(0)}}

and 

{{issue.properties."proforma.forms.i1".state.answers.2.questions.choices.get(0)}}

and many others. 

Any tips?

[Radu Dumitriu]

I believe that kind of behaviour is kinda' normal. You should understand that calculated CFs will always reflect the last indexing of the issue. If the issue is not modified, even if the CF value is changed, it is not reflected in the index.

What's abnormal is the behaviour you describe here "new calculated date field was created the same time as the rest of the fields and the issue itself". IMHO, that is an observational problem. Alter an issue and see if the behaviour is still the same.

[Larry M Conroy]

Thanks for the reply Radu. I modified the date field of an old issue that is not being found in the search. The new calculated date field was updated but trying the search again does not find that old issue. Any more thoughts?

[Radu Dumitriu]

What kind of CF is it? I mean, developed in-house, bought, .... ?

[Larry M Conroy]

I'm assuming CF stands for Custom Field and I created it myself.

[Radu Dumitriu]

well, in that case, you need to debug the searcher. I suppose you defined a DateRangeSearcher, right ? <customfield-searcher key="datesearcher" name="Date Searcher" class="com.foo.MyDateRangeSearcher"> ... etc ...

[Alex Corsun]

In my case that was a re-index problem: all the issues got included in the search results after re-index or a bulk change.