SiT! Bugs - Issues

0001719: Backslashes are removed from path names under Windows

Sat, 04 Feb 2012 12:20:20 +0000

Under windows, in the Config, Backslashes are removed, and the path's are displayed without any backslashes; If you click "Save" after making changes, the new (bad) path is saved to the DB without slashes.

0001768: report_incidents_by_skill.php does not take into account the last day of the month

Sat, 04 Feb 2012 12:13:20 +0000

This report use the date picker and then strtotime() to create the unix timestamp for the date range.

The issue is that for example:

Incidents by skill between 01 Jan 2011 and 31 Jan 2011 gives the following:
the code: strtotime($_REQUEST['enddate']);
strtotime(2011-01-31) gives 1296428400 which is "Sun, 30 Jan 2011 23:00:00 GMT"

But we should do strtotime(2011-01-31 23:59:59) which gives 1296514799 which is "Mon, 31 Jan 2011 22:59:59 GMT"
This will ensure that we do not lose the last day of the month. The date picker does not pass the hours :-)

0000827: Translation page should be paginated

Fri, 03 Feb 2012 18:01:48 +0000

the translation page is growing quite large, and FF3.50 is quite slow when working with this page.

It should be paginated

0001766: Add plugin_do() hook into "suggest_reassign_userid()" for alternative assignment plugin

Fri, 27 Jan 2012 08:44:59 +0000

As discussed before please can we add a plugin hook into the function suggest_reassign_userid() in incident.inc.php to enable us to create an alternative incident assignment plugin as discussed on IRC and in mantis.

I suggest to add it just before the return statement, but we have to keep in mind that the variable $userid is not a global in that function, and we may have to set it globally so that the plugin may access it.

I suggest 'incident_suggest_user_assign' as a context name

Thanks

0001767: Trigger (Notification/Email) when user requests ticket closure

Fri, 27 Jan 2012 08:42:56 +0000

Trigger (Notification/Email) when user requests ticket closure

0001212: Configurable weights for auto-assign lottery

Wed, 25 Jan 2012 12:29:21 +0000

The auto-assign lottery uses fixed values to assign a number of tickets for certain things. We should allow a administrator to configure 0, 1, 2; or 3 tickets for each condition.

0001246: Plugin utility functions to add to scheduler and triggers table

Tue, 24 Jan 2012 21:42:16 +0000

Create some functions that Plugin utility functions to add records to the scheduler and triggers tables. This would make it easier to create plugins that add scheduled tasks and plugins that extend triggers.

0001586: Redundant i18n strings

Tue, 24 Jan 2012 21:37:22 +0000

We have quite a few language strings that say effectively the same thing.

e.g. $strActivityMarkedCompleteSuccessfully

This is used in the redirect that happens after marking an activity complete and is really no more informative than the default "Success" message, the fact that we pass a message however causes the redirect delay to be longer.

0001369: Long dates are not always correctly translated

Tue, 24 Jan 2012 21:33:41 +0000

Danish dates in the long date format can appear like this "Satu.ay 17. Juli 2010" instead of "Lørdag 17. Juli 2010".

0001703: Setup min php version message is hardcoded to php 5.1 even though we now have a constant

Tue, 24 Jan 2012 21:32:45 +0000

Setup min php version message is hardcoded to php 5.1 even though we now have a constant

0001245: Make Sites & Contacts a single interface

Tue, 24 Jan 2012 21:29:48 +0000

It's confusing and redundant to have two separate menu items and browse pages for sites and for contacts, contacts are already subordinate to sites. That is a contact *must* have a site, so it makes sense that we treat them in that manner and display contacts under the site they belong to.

There's nothing stopping us having the search page search by contact name or anything, but the whole 'Browse contacts' concept has been flagged up often as confusing.

0001706: Setup stores max filesize config in config file

Tue, 24 Jan 2012 21:29:17 +0000

For some reason the 3.90 setup script stores the max file size in the config file, this has been set from the PHP.INI previously.

# config.inc.php - SiT! Config file generated automatically by setup.php on Sat, 03 Sep 2011 13:18:48 +0100

[snip]

# The maximum file upload size (in bytes)
$CONFIG['upload_max_filesize'] = 2097152;

0001278: Less confusing terminology

Tue, 24 Jan 2012 21:23:46 +0000

There's been plenty of discussion over the last twelve months about a lot of the terms we currently use in SiT! being confusing.

For example we use the word 'Users' to refer to people who provide support and not people who receive support. This is contrary to just about every other support system out there.

We've got this wiki page to try and decide which terms are best, use the talk page to place your vote:

http://sitracker.org/wiki/Development/Rewording [^]

0001538: Single language disclaimer

Tue, 24 Jan 2012 21:22:03 +0000

The KB disclaimer is currently set via a config setting. This means there can only be one version in one language.

Perhaps we should have a file in a similar way to the help files?

0001708: Ability to delete feedback forms

Tue, 24 Jan 2012 21:18:27 +0000

Once created, feedback forms cannot be removed, even if there are no responses relating to them and they are not configured to be used.

0001707: Ability to delete feedback questions

Tue, 24 Jan 2012 21:18:07 +0000

Once created, feedback questions cannot be removed, even if there are no answers relating to them.

0001709: Ability to delete KB Articles

Tue, 24 Jan 2012 21:17:42 +0000

Once created, KB articles cannot be removed.

0001764: Add an Incident Title

Tue, 24 Jan 2012 13:57:57 +0000

The "title" of the incident is just Title. It shoudl probably be "Incident Title"

0001765: Contact Details Edit

Tue, 24 Jan 2012 13:57:45 +0000

If we are using LDAP the contact should not be able to edit their information.

See Diff in additional information for contactdetails.php

0001763: en-US.inc.php

Tue, 24 Jan 2012 13:57:33 +0000

Changes for First Name and Last Name

0001739: "LDAP Customer default site" must be the required field if the "LDAP Customer Group" is specified

Tue, 24 Jan 2012 13:30:29 +0000

"LDAP Customer default site" must be the required field if the "LDAP Customer Group" is specified, because of the function check_valid in classes.inc.php (line 315). If the default site is not specified while Customer contacts are on the LDAP server, the ldapSync action will fail and no error message will be displayed.

0001762: Initial Search options

Tue, 24 Jan 2012 13:28:49 +0000

When going to a few of the Pages from the menus an additional click or 2 is needed to get to the information.

Customers -> Browse Sites
shows the full list of All active sites instead of "Sorry, your search wielded no results"

Customers -> Browse Customers
shows the list of all customers instead of just the Customers who's last name starts with an A

Customers -> Maintenance -> Browse Contracts
shows all contracts instead of instead of just the contracts starting with an A

Diff for strings.inc.php is listed in Additional Information

0001760: Refresh list of users

Tue, 24 Jan 2012 13:23:30 +0000

Ran into an issue when 2 administrators were adding the same user at the same time (honest), one did not have the user list refreshed before adding the user.

I added a string
$strRefreshList = 'Refresh List';

and used it on the manage_user.php page with a {$_SERVER['PHP_SELF']} link.

See Diff in additional information
(I actually have used this on contacts.php, contracts.php, and sites.php)

0000694: directed context text in the portal

Tue, 24 Jan 2012 13:13:41 +0000

Would be good if admins/people with appropriate permission are able to add additional text/HTML (directed content) into the portal so this could be used for either user facing notices (say opening times, tips etc) or adverts e.g. special price on toner etc this would have a multitude of uses which can direct relevant content to users (such as tips/tricks about the skill they log calls on), events which may be relevant to them e.g. PHP user groups training etc

It would be good to be able to direct these messages say the user is logging a call on RedHat 4 you could direct messages about upgrading to redhat 5 or have a notice informing people redhat 4 goes out of support on X

0001043: Consider changing how search works

Tue, 24 Jan 2012 13:11:28 +0000

We should consider changing how the search functionality in SiT works, currently we use full text searches which are fine in relatively small systems though in larger systems can cause quite a performance overhead on the database server, are limited to MyISAM tables and requirements for a lock can mean that other users are unable to use SiT whilst the search takes place.

We should investigate the use of something like Lucene or Sphinx which are separate search engines which should remove/reduce the problems we experience with full text indexes, I've not used these previous so may not be suitable due to platforms or how they work though this should be investigated to prevent performance issues.

A 'hack' would be to use a slave server for searches which would prevent other users from being impacted this could be done quite easily in SiT though would require additional servers and MySQL skills.