jmwe condition checking cutsom field value for transition workflow

[Gabriel Grabka]

Hello dear community,

Can someone help me?

as in the screenshot i need to check the issue type status (in this case pass would be true). But since its's a custom field i cannot find ot which syntax I should apply to test it. I've tried various combinations that would work on string and other data types but none is working.

[David Fischer]

Hi Gabriel,

The field is not just a custom field, it looks like a non-standard custom field. What is the type of this field (from the custom field screen)?

[David Fischer]

Also, did you notice that you can access the full API of the field value by clicking on the link in the subfields section?

[Gabriel Grabka]

Hello,

thank you for helping out, yes if i click on "issue.get("customfield_10017")?.statuses"

i recieve [Lcom.xpandit.raven.customfield.bean.StatusResultBundle;@2b20bb9a

as a result value and the value after @ changes when I try out a different status. Probbably i should use that one for verification, but what kind of syntax do I have to use?

[David Fischer]

No, you actually need to ask xpandit for the Java API of that field. 

[David Fischer]

And you can also see the API of the statuses subfield when you hover over the subfields and click on the type, which is a link. 

[Gabriel Grabka]

Is it on this screen?

[Gabriel Grabka]

sorry, wrong Picture:

[David Fischer]

It really depends on what you’re looking for. I have no idea what this field is, what data it represents and how you’d access it. Again, you need to ask the app vendor for details. 

Initially, you seemed to be interested in the statuses sub-field. If that is the case, then it appears to contain an array of objects described in your first screenshot, not second. But what they mean is beyond me. 

[Jira Admin]

Thank you, I will ask the support for additional info, I only want to verify the status of the custom field. 

[Brian McCallister]

Hello, I would like to provide a solution that worked for me:

[David Fischer]

Hi @Brian,

You forgot to include the solution...