How can we add a reporter to the custom user picker field when a field's default value is "none"?

[Shah Baloch]

Hi Community,

I am trying to create an automation rule to add a specific user or a reporter into a custom user picker field based on a custom radio button field choice selection. The radio button field (budgeted) has two options, yes and no. I created a rule: if the user selects no,  it adds a user (testaccount) into the custom user picker field; otherwise, the reporter is added to the custom user field. It is working fine with these two options; for No, I added a user, and for Yes, I used smart value {{reporter}}; however, the issue is if neither option is selected, it won't add a reporter into the field; it leave it blank. I am using the condition in the Issue update state. The custom Budgeted field gets updated when the user adds a Proforma Form. Initially, I didn't add the field in the screen; it was only on the Proforma form; since I wasn't able to add automation with the form so, I created a custom field and linked it with the form, and custom Jira field is only in the edit screen. 

I added another if else condition, such as if the value "is not one of," and selected yes and no; I also tried the empty option, but neither worked. How can we add a reporter to the custom user picker field when the budget's default value is "none"? 

Appreciate your help!

[Fernando Eugênio da Silva · Accepted solution]

@Shah Baloch 

'None' for Radio Button fields it's same than "empty". So you can use your rule to validate if the field Radio Button IS EMPTY > Then make this action.

Have you tried this?

If yes, could you share some screenshot about how your automation rule is builded?

Regards,

Fernando

[Shah Baloch]

@Fernando Eugênio da Silva I tried the empty and "is not one of" options, but it's still not assigning the value to the custom user field. I am attaching rules screenshots. Thanks

[Fernando Eugênio da Silva]

@Shah Baloch 

This is a weird behaviour. For these cases, the none value it's really considered as 'empty'.

This may be associated with a slightly more complex 'database' problem.

Have you tried reindexing just this specific issue?

Another suggestion would be to open a ticket directly so support can evaluate any discrepancies in this field value: https://support.atlassian.com/contact/#/

[Shah Baloch]

@Fernando Eugênio da Silva, you are right. It can be a database issue. I changed my logic from an edit issue to a transition issue, and it worked. I fully re-indexed with the previous logic, but it didn't work. Another workaround was to create two automation jobs; one was to add a reporter into the custom user picker field whenever an issue is created; that way, it has a reporter as a value regardless of selecting an option from the custom radio button field, and then second one was the initial one where if user change the value of radio button field then update the custom user picker filed. I wanted to mention this in case someone else has a similar issue. I appreciate your help!