Feature Requests
Feature requests for Hoduma - You have 15 votes and can give up to 5 votes per item. If you create an item you vote for it with 1 vote automatically. After a request has been implemented, it will be deleted and all persons voted for it will get back their votes.
AkeebaSubs Integration
ITIL terminology
Show names in all forms,not usernames
Top-level menu on every page (list and details form):
Example menu for Admin or rep
Assigned to me; Assigned to my department; All not closed "cases"; Find "case"; Find in knowledge base
Example menu for users
My "cases"; All "cases" of my department; Find "case"; Find in knowledge base
Example menu for Admin or rep
Assigned to me; Assigned to my department; All not closed "cases"; Find "case"; Find in knowledge base
Example menu for users
My "cases"; All "cases" of my department; Find "case"; Find in knowledge base
option to define more than one rep to a department or a category. if one rep is busy or on leave the other is also aware that a case is waiting.
I would love to be able to have an option to edit the department and category. In my case, i would replace department by customers and Category by products. today i do it in the code, but having the option would be much nicer.
On list form add mass operations (for example: all cases paused)
Function for join two or more "cases":
Some "cases" has similar problem and similar solutions.
We are will create single "case" from all similar "cases", and mass sending e-mail
notifications for all creators about all "case"-events.
Some "cases" has similar problem and similar solutions.
We are will create single "case" from all similar "cases", and mass sending e-mail
notifications for all creators about all "case"-events.
add more options for menu "Show all cases from last xxx days"
Need select
- "rep" - department (administrators or developers)
- initiator 's - department
- interesting statuses - closed, created, has any events
Need select
- "rep" - department (administrators or developers)
- initiator 's - department
- interesting statuses - closed, created, has any events
add field "desired date and time of execution" (deadline)+ datetime picker
add user-button, what set "case" on status "approved initiator"
- this status must to be settled before status "closed"
- this status must to be settled before status "closed"
Users don't like view empty form after saving new "case".
Need show question:
You want continue edit your new "case" or go to your "cases" list ?
Need show question:
You want continue edit your new "case" or go to your "cases" list ?
custom fields in case form
Link the department to categories. Not all categories should be available to all Departments
Add descriptions for the priorities.
Form editor to adjust the positions of the fields
Ability to set customer/company and a billing rate to that customer. Allowing you to report on the cost for the time spent on an issue. All viewable only to reps & admins.
Optional disable users ability to update their contact details (a patch was developed for HURU):
HURU PATCH DETAILS:
Find the file: components/com_huruhelpdesk/views/cpanel/tmpl/default.php
Near line 177, you should see the following:
if($userlvl==USER_LEVEL_ADMIN || $userlvl==USER_LEVEL_REP || $userlvl==USER_LEVEL_USER)
{
?>
php
}
This code has to be commented out
HURU PATCH DETAILS:
Find the file: components/com_huruhelpdesk/views/cpanel/tmpl/default.php
Near line 177, you should see the following:
if($userlvl==USER_LEVEL_ADMIN || $userlvl==USER_LEVEL_REP || $userlvl==USER_LEVEL_USER)
{
?>
php
}
This code has to be commented out
Can you make an option to make users unable to change their usernames on creating a ticket. (The default username is their username, could you make it so they couldn't change from that default?)
The reason I ask this is because I don't want users to be able to impersonate other users (or administrators)
The reason I ask this is because I don't want users to be able to impersonate other users (or administrators)
Change field "Department" from user details to-or create on "Classification". In many cases users have no need to be on a department (they are just users) but very important to assign the ID to a specific support department (networking, suport, accounting...)
New:
You have no permission to vote! Log in or create an account.
If you like Hoduma, please 
Follow us on Twitter to stay up to date with updates and other news. Click