Skip to content

[BUG] Staff losing access to /move when creating a new category #609

@kentbakk

Description

@kentbakk

Is there an existing issue for this?

  • I have searched the existing issues

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:

  • Admin Support (admin)

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

  1. Make one category and give staff to role1 and role2
  2. Verify both roles have access to /move in a ticket
  3. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions