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

Bug - [Problem handling errors in the owner field in the activity dialog] #627

Open
dayltonr opened this issue Jan 10, 2025 · 2 comments
Open
Labels
1 - 🐞 bug 🐞 An issue with the system. 4 - internal Issue/MR 4 - verified This issue or pull request was verified.

Comments

@dayltonr
Copy link

Environment

  • Server OS: Linux Ubuntu
  • Browser: [ Chrome, Firefox, Safari]
  • Znuny version: 7.0.19

Expected behavior

When creating a ticket via process, if there is a mandatory Owner field, it is expected that validation will be performed to determine whether the field is empty or not.

Actual behavior

In this version, when sending to create the ticket without filling in the owner, it submits but returns to the activation screen without displaying the error that the owner field was not filled in.

How to reproduce

Steps to reproduce the behavior:

  1. Create a process, with an activity that has the owner field as mandatory.
  2. Create a call via process, without informing the owner field.
  3. Form does not validate the field and does not signal an error.

Additional information

This commit added what is causing the error.
The correction made is changing the ServerError validation key.
The correct thing would be to change only the UserLookup key.

Suggested solution:

 # set server errors
    my $ServerError = '';
    if ( IsHashRefWithData( $Param{Error} ) && $Param{Error}->{'OwnerID'} ) {
        $ServerError = 'ServerError';
    }

    if ( $Self->{LinkTicketData} ) {
        $SelectedValue = $Self->{LinkTicketData}->{Owner};
    }

Screenshots

Form does not validate the field and does not signal an error.
image

@rkaldung rkaldung added 1 - 🐞 bug 🐞 An issue with the system. 4 - verified This issue or pull request was verified. labels Jan 11, 2025
@rkaldung
Copy link
Member

@dayltonr Thank you for reporting. I verified this issue with Znuny LTS 6.5.11 and Znuny 7.1.3. A fix won't be provided for your reported version 7.0.19.

@rkaldung
Copy link
Member

Internal issue 1015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - 🐞 bug 🐞 An issue with the system. 4 - internal Issue/MR 4 - verified This issue or pull request was verified.
Development

No branches or pull requests

2 participants