HESK version 2.6.0 BETA (test version)

[snifty]

Thanks for your fast reply!

I think your right, some points are not really bugs and more small improvements.


1. ok, as it is not hard to change I can easily fix it meanwhile with "if (strlen(hesk_POST('subject')) > 8){..."
But it would be helpful to be integrated.

2. I mean if there is a "please select" option in a custom Dropdown menu it must be a required field, otherwise the value of this field keeps empty (or please select) when not changed. Otherwise I could write "please select" as the first value on my own and it has the same effect. But there is not option to set this field reqired.

3. ok

4. yes, thats what I mean.

Thank you!
PS: so I should put all these points to the suggestions page as they are only very small improvents? Would it help to put the code in there if I already found a solution to implement it?

[Klemen]

2. That's actually the purpose of the "please select" - even if the field is not required, it is there to provide an empty value instead of the first option (so you can have a non-required field empty instead of selected automatically).

This is a per-field setting, so you can have all the possible combinations you may need and everyone can choose the option that best fits their requirements:
- required with "please select"
- required without "please select"
- optional with "please select"
- optional without "please select"

4. I've added this and will be included in final 2.6.0


You are welcome to put *any* suggestions there as well as code samples

[snifty]

2.
I know what you mean, but if you check the "required" box in the custom field settings and you predefine the values than one of them (with or without "please select") is predefinied. That means that the user can ignore this setting, because it is not tested if required or not. But required means that the user has to choose something.
I thought if the value is still "please select" than the user should get a message that he has to choose a setting. Do you know what I mean?

4.
Thank you, I really appreciate that!

5. On new point:
when adding notes to a ticket (eg. while phoning with the user) the time worked counter is set back to 00:00:00.

[Klemen]

2. I'm not sure we are on the same page here.

" -- Click to Select -- " will be the default selection. If the field is required and customer does not change it, HESK will show an error:

Make sure you test this from CUSTOMER interface, in admin interface required custom fields are not enforced as staff may not always have all the customer info.

If you have something else selected by default it's there because it is remembered from previous session, try closing all browser windows then try again.


5. Good point. This may be a bit more complicated to fix though so I don't promise a solution for 2.6.0

[snifty]

2.
Damn, you're absolutely right!!! I didn't notice that there is a difference for admins und customers. Sorry for wasting your time on that point!

5.
I'm glad I can help!

[Klemen]

Version 2.6.0 has been released:
http://www.hesk.com/download.php

Big thanks to everyone who helped test the beta!