Is there an existing issue for this?
Current Behavior
When you have a list of categories with staff roles selected for example:
- General support (staff, admin)
Everything works fine, the staff role can use /move
If you now add another category like:
Then staff loses access to the /move command, until i go back and remove staff from the "General Support" category, save then reapply them to it and resave. (This causes them to get access to /move again)
Expected Behavior
I would expect /move to be accessible to any staff from any category not just the last saved one.
Steps To Reproduce
- Make one category and give staff to role1 and role2
- Verify both roles have access to /move in a ticket
- Make another category and give access to only role2
-- role1 has now lost access to /move inside a ticket from the first category
Environment
- OS: Ubuntu 24.04.2 LTS
- Node: PTDL_v2 - Official egg
- NPM: PTDL_v2 - Official egg
- Bot: PTDL_v2 - Official egg
Anything else?
No response
Is there an existing issue for this?
Current Behavior
When you have a list of categories with staff roles selected for example:
Everything works fine, the staff role can use /move
If you now add another category like:
Then staff loses access to the /move command, until i go back and remove staff from the "General Support" category, save then reapply them to it and resave. (This causes them to get access to /move again)
Expected Behavior
I would expect /move to be accessible to any staff from any category not just the last saved one.
Steps To Reproduce
-- role1 has now lost access to /move inside a ticket from the first category
Environment
Anything else?
No response