Change the order of update when manually resolving and closing a problem

[simon25111]

Hello,

I noticed that when I post an update message and manually resolve a problem in one step, the update message is published after the recovery event. This makes the event log a bit confusing because the update message appears after the recovery, while logically, it should be the other way around.

Would it be possible to change the order so that the update message is published before the recovery event? Or perhaps provide an option to control this behavior?

Thanks!

[simon25111]

Here the action log details : as you can see the update is sent after the recovery

[simon25111]

Hello, I still have this issue. I tried different ways I hope we could have native macro like {EVENT.UPDATE.MESSAGE}

[cyber]

Why would you need to acknowledge it at all if you are closing it? In my mind ack is something to notify others that someone picked it up and is dealing with this... Closing does not need ack any more...

[simon25111]

I'm working with Adaptive Cards in Teams. When an alert is triggered, it gets published in Teams. I would like to add a message to the recovery Adaptive Card (for example, a ticket number).

[cyber]

But that message is added anyway.. so why ack it? If you just close it, your "recovery operations" will be executed and "update operations" as for ack-ing will not be executed...
Maybe I just don't get the exact workflow ..

[simon25111]

### Issue with Event Order When Handling Problems

Our standard process for handling issues follows these steps:

1. **Problem detected**
2. **Update problem:** Check the **"Acknowledge"** checkbox
3. **Create Jira ticket**
4. **Update problem:** Send message + check the **"Close problem"** checkbox

With this workflow, the **update** and **close** actions are executed in the correct order:
first, the acknowledgment message is sent, followed by the close message.


### Issue with Early Jira Ticket Creation

However, some users create the Jira ticket **before** acknowledging the issue. Then, they acknowledge and close the issue in the same update. This modifies the process as follows:

1. **Problem detected**
2. **Create Jira ticket**
3. **Update problem:** Send message with the ticket number + check **"Acknowledge"** + check **"Close problem"**

As a result, the **update event is sent after the closing event**, which is not the intended behavior.

Additionally, the Zabbix update form allows both checkboxes (**"Acknowledge"** and **"Close problem"**) to be checked in a single update, further contributing to the issue.