Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assignee choice invalidates tag/status/priority order #8

Open
altafarus-arch opened this issue May 20, 2020 · 0 comments
Open

Assignee choice invalidates tag/status/priority order #8

altafarus-arch opened this issue May 20, 2020 · 0 comments

Comments

@altafarus-arch
Copy link

Brief description:
Tickets listed on ticket board cannot be ordered by tags, status, priority or reason value when an assignee is already chosen.

Reproducible: always

Steps to repro:

  • Connect to /admin/tickets
  • Select an assignee with textbox
  • Click Apply
  • Click on Tags (or Status/ Priority/ Reason)

Expected behavior:
Ticket list ordered by Tags (or Status/ Priority/ Reason).

Observed behavior:

  • Page is reloaded
  • Image of an arrowhead pointing at the bottom of the page is displayed on the right of the Tags column title to inform user tickets list is supposed to be ordered by Tags value.
  • URL contains “order=tags” parameter
  • Order of the tickets in the list hasn’t changed

Environment:

  1. TOR Browser 9.5a11 (based on Mozilla Firefox 68.7.0esr) (32-bit)

  2. Firefox Quantum 68.6.0esr (32 bits)
    with OS: 4.19.0-8-686-pae Add table #1 SMP Debian 4.19.98-1 (2020-01-26) i686 GNU/Linux

  3. TOR Browser 9.0.9 (based on Mozilla Firefox 68.7.0esr) (64-bit)
    with macOS Catalina version 10.15.3
    and also with Windows 10 Professional

@altafarus-arch altafarus-arch changed the title Discourse ticket plugin: assignee choice invalidates tag/status/priority order Assignee choice invalidates tag/status/priority order May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant