---- Reported by nengard@gmail.com 2010-04-27 20:12:14 ----

When a patron attribute is required it should be in red like other required fields



---- Additional Comments From oleonard@myacpl.org 2010-04-30 18:25:28 ----

Does this bug refer to Patron Attribute Types?



---- Additional Comments From nengard@gmail.com 2010-05-01 01:24:00 ----

Yes it does :)



---- Additional Comments From oleonard@myacpl.org 2010-05-10 19:32:14 ----

Under what circumstances are patron attributes required?



---- Additional Comments From nengard@gmail.com 2010-05-10 19:34:29 ----

When you create a patron attribute you can say whether it's required or not.  So some libraries have things like student ID or license number that is required. In the example I saw the library had a special identifier they had to use for stats that is required. 



---- Additional Comments From oleonard@myacpl.org 2010-05-19 14:00:21 ----

The current method for making a patron attribute is a hack, and each possible solution I can think of for this bug is also a hack. I'm changing this to an enhancement request so that we can tackle the issue from the right direction: If we can set a "required" parameter for patron attributes, the interface can directly access that information.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:26 UTC  ---

This bug was previously known as _bug_ 4418 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4418

Actual time not defined. Setting to 0.0
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.