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

Add priority/sorting for AgentTicketZoom MenuModules #646

Open
itweserems opened this issue Feb 26, 2025 · 1 comment
Open

Add priority/sorting for AgentTicketZoom MenuModules #646

itweserems opened this issue Feb 26, 2025 · 1 comment
Labels
1 - 🚀 feature New feature or request 4 - verified This issue or pull request was verified.

Comments

@itweserems
Copy link
Contributor

itweserems commented Feb 26, 2025

In the current (and probably all previous) Znuny version, the MenuModule entries for AgentTicketZoom are sorted by key-numbers of their SysConfig entries, e.g. "000-Back", "210-Print".
In current dev code-branch this sorting happens in Kernel/Modules/AgentTicketZoom.pm, starting on:

for my $Item ( sort keys %ZoomMenuItems ) {

This should instead be done by a priority config, as it is done for other menus within Znuny.

For example, admins should be able to change a "priority" value, e.g. for "Ticket::Frontend::MenuModule###000-Back" that defines it's menu position, compared to the priorities of other MenuModule items.

I am currently preparing an additional option per MenuModule where sorting of MenuModule items in AgentTicketZoom is not based on the SysConfig-key but a new "Priority" parameter instead.

@rkaldung rkaldung added 1 - 🚀 feature New feature or request 4 - verified This issue or pull request was verified. labels Mar 11, 2025
@rkaldung
Copy link
Member

@itweserems I labeled the issue/MR as verified to have it merged. It is be possible that one of the developers requests some changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - 🚀 feature New feature or request 4 - verified This issue or pull request was verified.
Development

No branches or pull requests

2 participants