https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36763

            Bug ID: 36763
           Summary: Changing a patron category doesn't update form
                    accordingly
 Change sponsored?: ---
           Product: Koha
           Version: Main
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Patrons
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected]

Patron editor needs to re-evaluate form when the patron category is changed.

For example, let's say you have an adult category that requires both a surname
and a first name, and an institution category that requires only the surname.

You edit an existing adult category and change it into an institution. 
Realistically, it should clear the first name field, remove the field, and not
require it to save.  However, as is, none of this happens, and it is impossible
to save without putting some value in the first name field.

Changing the patron category should clear fields that hidden for the chosen
category, and hide those hidden fields, removing the required class.  And if
the category is changed to something that has more fields, those fields should
be shown, and if they are required, the required class added.

I know, in typical workflows, this is not necessarily an issue.  You generally
create a new patron with the category first.  But on occasion, as we clean up
accounts, sometimes an account changes categories, and this should be a common
check.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to