[Bug] Can't snap app to secondary monitor on launch

[bitrage]

Description

On version 3.0 and before I was able to assign a specific app to a zone on my secondary monitor. Since version 3.1 I can't assign a monitor as an action.

I tried selecting the secondary monitor as condition via "Monitor is XXX" but the rule is simply not evaluated. This might be a bug or intended feature. I can select both monitors but only the primary monitor triggers the rule.

Expected Behavior

Selecting the condition "monitor" with the secondary monitor as choice should trigger when the monitor is present (even if not primary).

There should be an action where you can snap to a zone on a specific monitor. (e.g. Window -> Snap to monitor)

Steps to Reproduce

1. Connect monitor1 (primary) and monitor2 (secondary)
2. Add rule
3. with conditions: Monitor is monitor1 AND Application is chromium (for example)
4. with action: Snap to zone(s) 2
5. Save rule, save settings
6. Open chromium, move to monitor2 zone 1.
7. Close chromium
8. Open chromium

Expected: chromium on monitor2 zone 2
Actual: chromium on monitor2 zone 1 (because of last known location independent of rule)

PlasmaZones Version

3.1.0

Display Server

Wayland

Desktop Environment

Plasma 6.7.1

Distribution

CachyOS

Support Report

No response

Checklist

• I searched existing discussions and issues
• I can reproduce this with default settings

[fuddlesworth]

Can you run the plasmazones-report and paste the tar.gz file in here?

[bitrage]

plasmazones-report-20260624-204257.tar.gz
Sure thing

[fuddlesworth]

Thanks. I'm releasing a bug fix update today and should have this fixed.

[bitrage]

Your work is very much appreciated. Thank you!

[fuddlesworth]

Should be fixed now. You might have to recreate the rules though.