Setting a defualt value when value not exists

Originally asked by Sagi Gueta on 02 April 2023 (original question)


Hello,

We want to know if it’s possible setting a default value when a single select field value is not exists on the opposite instance.

For example if we have a custom field name: Example Choice on both instances (both on JSM and Jira products).

On JSM Example Choice field has 3 values: A,B,C

On Jira “Example Choice” field has 3 values: A,B,D

If a user chooses a value that doesn’t exists on the other side we want that A value will be the default value.

Therefore if a Jira user select D value, it will update JSM ticket with A value instead.

Is it possible to implement it?


Answer by Sonal Otwani on 03 April 2023

Hi Sagi Gueta ,

Yes, this is possible but here is my main question:

Do you have fixed values in remote side? Means, on Jira side there will be always A,B and D.

Or

do you want to fetch this single select field values through API during sync and then see if the value exist or not?

Based on the above requirement clarification we need to make a script.

Thanks,

Sonal


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.