Automation rule for IF ELSE not working properly

[dwike_aprilia]

Hi guys, So I have a problem with the automation rule. There's no error actually but the rule is not working properly and I'm wondering why.

Here is my case. So whenever the user creates the ticket from the Jira Service Desk, am cloning the ticket into another board (Let's say MIB board.)

So whenever the dev updates the priority field (through MIB board), I would like this is gonna happen in the Jira service desk ticket as well. So, I create the rule like below :

Then voila! When the dev update the field priority from their board (MIB) it only reflects in one side (MIB only) and does not update the Jira service desk ticket priority field.

Additional info: For tickets in MIB the linked type to Jira Service desk ticket is -> "Blocks" meanwhile for tickets in Jira Service desk linked type is -> "is blocked by"

I already tried to put "for linked issues" types "blocks, is blocked by"
but still the same result. nothing error. but this is the result :

[Aditya Sastry · Accepted solution]

Hi @dwike_aprilia 

Can you check if the values in the priority field match between BSM and MIB?

Thanks,
Aditya

[dwike_aprilia]

Hi again @Aditya Sastry :)

yep. They are exactly the same.

MIB :

BSM :

any idea? :(

[Aditya Sastry]

Hi @dwike_aprilia 

I believe the edit priority option is not set correctly in your rule. I tried in my server instance and the similar rule worked perfectly fine. 

Can you check the edit priority option and send a screenshot? Attached are the screenshot from my instance.

Thanks,

Aditya

[dwike_aprilia]

Hi @Aditya Sastry here is my screenshot from edit issue rule :

I thing we did the same way right? am I missing something here?

[Yanty Ghani [ServiceRocket]]

@Aditya Sastryis correct, it's the setting for edit issue. You should select "Copy from Trigger issue" because you want to copy "Priority" from MIB to BMS.

[dwike_aprilia]

hi guys @Aditya Sastry @Yanty Ghani [ServiceRocket] I've changed to trigger issue . But still facing the same issue here :'(

[Yanty Ghani [ServiceRocket]]

I noticed that "For linked issues" type "is blocked by". Shouldn't it be "blocks"? To be safe, just adds both.

[dwike_aprilia]

Oh My God! @Yanty Ghani [ServiceRocket] now it works!!!!!!!!!! Glad that you guys helping me out!!!

thankssss! @Aditya Sastry 

[Yanty Ghani [ServiceRocket]]

Thanks to @Aditya Sastry  for pointing it out. I was thinking of that too, but forgot to ask :D Anyway, glad to help.

[Aditya Sastry]

Glad that it worked out for you :)

[Yanty Ghani [ServiceRocket] · Accepted solution]

Hi @dwike_aprilia ,

Can you check if "Priority" field is in "Edit issue screen" in the JSM project? Also, check if there's any security level set in that JSM issue.

[dwike_aprilia]

@Yanty Ghani [ServiceRocket] yes, the priority field exists in every screen I used (View, create and edit). 

the security level is not set as I attach below pic :( 

[Yanty Ghani [ServiceRocket]]

According to the Audit Log, it shows that BSM-21 was edited successfully after you updated issue in MIB, but you're saying the Priority fields are not the same for both issues, right? Can you take a full screenshot that includes this part:

[dwike_aprilia]

yes sure, here is the screenshot :

[Yanty Ghani [ServiceRocket]]

Ok, it shows success and issue BSM-21 was edited successfully. So doesn't seem like there's any issue. Can you take screenshots of issue history for both MIB-2552 and BSM-21? Make sure that it's sorted newest first.

[dwike_aprilia]

hi @Yanty Ghani [ServiceRocket] yes. the due date was updated for both tickets but not with the priority.
here is the screenshot from both history of the ticket.

BSM:

MIB :

PS : Please ignore update from (me)