1) It would be great if we can set up a categories of requester. For example - CEO and other "Chiefs" are "VIP"s, their assistants are "HighImportant" and others are just "SimpleUsers". And when selecting requester when making "incedent" request something like pop-up appears "Hey! It is VIP!" or "It is chief's assistant!". For now we have a paper sheets with "chiefs" and their assistants in front of first line technicians

2) When selecting Category and Subcategory it would be great if list of knowledge base articles of this Category/Subcategory appears under the request form to simplify solving the incident by the First Line technicians. It would be event better that "a typical roadmap to diagnose and solve" appears: for example: We select category "Printer problems" -> subcategory  "Not printing" and such kind of text appears in form: "1) check if printer is correctly installed 2) ping printer 3) ask user if he can print on another printer..." and so on.

3) Color highlight of incidents with specific state ("red" - request overdue) - to simplify visual request selection. Same as "Filter" but shows all request and only highlight filtered.

4) Subsequent tasks: We have a "process" of installing new working place in office: one technician must set up a computer and phone, other - program PBX and third - change phone number in AD. All the technicians (in common case - GROUPS) must be notified after previous "task" completed. For example - first subtask is assigned to technician - he installs all the equipment and writes "New computer installed, phone connected to socket number ZZZ" and closes his subtask, PBX technicians group receives a notification that new task arrived - someone from PBX administrators picks up this task - (he must see solution from previous technician!), program PBX and writes "PBX programmed. Phone number is NNNN" and closes this subtask. AD administrators, then receives notification and do  thier work. After AD administrator closes his task (last in "chain") BIG task ("to setu up new working place") closes automatically, or notification to responsible person arrives to close this task. It is just example - we have some "processes" which are not subsequent but parallel, but it is ONE process.

And about assets:

1) As i understand after scanning desktops are automatically assigned to the department which last user logged on belongs. Is it possible to "lock" some fieilds for automatic change. We have computers in presentation rooms which "belongs" to IT, but any user form any department can log on those computers.

2) Is it possible to generate an incident if hardware "profile" of asset changed? Computer had 4 Gb of RAM and now has only 2 Gb - we need to investigate WHY, at least. So if it is "approved change" such an automatically generated incedent will be just merged with proper incedent or change.

3) any way to change SSH port for scanning?