JSM Compare two values (by JWT)

[Benjamin Zhou]

My idea is: In JSM, I have a request type that need user to input "affected user" and "Approver", I would like to restrict that the "affected user" can not be the same as  "Approver".  In workflow I use JWT compare two values validator.  The issue is when I enable this rule, I can not submit this request, if the "affected user" = "Approver", it will show the error message, it is OK.  But if the "affected user" != "Approver", it also can not submit this request, it will also show the error message.

Does anyone know how to fix this issue?

[Sergio García-Consuegra _Decadis AG_]

Hi @Benjamin Zhou ,

My name is Sergio, and I'm a member of the support team from Decadis. I’d also like to let you know that we offer a customer portal where users can contact us with any technical questions related to our apps. You can access it through this link

Otherwise, if you prefer it, we can just maintain the contact through this post.

Could you please let me know the following information?

• What is the type of your Affected User/s custom field? Is it a single-user field or a multi-user custom field?
• Could you please attach a screenshot showing where it's placed this specific transition in your workflow? Would be the first transition which is in the "Create" step?
• Does it appear any specific error in our Audit Log?

Once we have this additional information, we will be able to take a deeper look into this issue.

Thank you!

Best regards,
Sergio

[Benjamin Zhou]

Hi @Sergio García-Consuegra _Decadis AG_ 

At first thank you so much for your help on this topic.  I do appreciate.

FYI...

• What is the type of your Affected User/s custom field? Is it a single-user field or a multi-user custom field?     Ben: the field type of Affected user is assets objects.  the field type of approvers is user picker(multiple user)
• Could you please attach a screenshot showing where it's placed this specific transition in your workflow? Would be the first transition which is in the "Create" step?    Ben:  yes, you are right.  It is the first transition which is the "create" step.
• 

• Does it appear any specific error in our Audit Log?   Ben: Please see the Audit log.

[Sergio García-Consuegra _Decadis AG_]

Hi @Benjamin Zhou ,

Due to the architecture of Asset Objects, they cannot be correctly evaluated in validators like the "Compare two field values" or our "Jira expression" validators. 

Our suggestion would be using another user custom field instead of an Asset Object. Then, you could use our "Jira expression" validator which allows you to compare both custom fields in order to check they have selected the same users.


issue?.customfield_AAAAA?.map(u => u.accountId) == issue?.customfield_BBBBB?.map(u => u.accountId)

You would only have to replace AAAAA and BBBBB for your custom field codes. This way, you would be able to validate those values selected.

Also, in case you need to use Asset objects for a specific reason, if you give us a more detailed information regarding what is your current requirement, then we could also study the possibility of updating that Asset custom field in a post-function so it's correctly filled.

Thank you.

Best regards.
Sergio

[Benjamin Zhou]

Hi @Sergio García-Consuegra _Decadis AG_  ,

Thank you so much again for your help!

I am sorry I can not change any user custom field.  The reason we are using asset object is all the affected users are saved in assets.

Except for changing user custom field, is there no way to use "Compare two field values"?

Look forward to your feedback.

Thanks,

Ben