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

Sector Nord AG: Agent Dashboard mandatory columns fix #547

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

ZTrotter
Copy link
Contributor

Proposed change

For all dashboard widgets, the TicketNumber field is mandatory. Addtionally, for process widgets, the Activity and Process fields are mandatory. These fields can be removed from the configuration and the state can be saved. After removal, the columns will still be displayed in the table. However, when returning to the configuration, the fields are not present in the Available Fields column.

image image

To resolve this issue, an alert box has been added to inform the user that a mandatory field has been removed and to prevent the user from saving this configuration.

Type of change

1 - 🐞 bug 🐞

Additional information

Steps to replicate:

  • Navigate to the AgentDashboard.
  • Select a ticket widget, click to open the action menu in the top right hand corner and then click the settings cog.
  • Remove a mandatory field (Ticket Number/Activity/Process) from the Visible Columns and add it to the Available Columns.
  • Save the changes.
  • Note that the removed field is still a visible column in the table.
  • Return to the settings to see that the field remains in Available Columns where it was previously saved

Checklist

  • The code change is tested and works locally.(❗)
  • There is no commented out code in this PR.(❕)
  • You improved or added new unit tests.(❕)
  • Local ZnunyCodePolicy passed.(❕)
  • Local UnitTests / Selenium passed.(❕)
  • GitHub workflow CI (UnitTests / Selenium) passed.(❗)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant