Add the ability in the front end issue creation so that a file may be uploaded with details. i.e. A dump or something similar.

In release 1.3.0

If you have a a process tree of projects and you search for text using the filter search box, for some text that occurs in a sub-project name, the search returns no values.

The problem occurs because the ProcessTree code in the view.html file doesn't find the parent project, since they are not in the results returned from the search.

I have put in a cludge for the situation where there is a single result, but this will not work if there is more than one record returned.

This is a problem in the component I used as a model as well.

Restructured it_projects table to be a nested table. Reworked controllers, models & views.

Code also to convert 'old' structure to new format.

It would be advantageous for a user, once they have raised an issue to be able to edit and potentially supply additional information on the problem in the issue itself.

Coding & testing complete. In release 1.2.0.

There are a lot of warning (error) messages when the Joomla reporting is set to Developer.

I think that all cases have been identified and rectified so am closing the issue.

It would be nice if thes in the list view get the status assigned as class. That would be an easy way to set up highlighting
mechanisms via CSS.

Implemented the ability to override the supplied stylesheets in the site template directory. This permits a site to create (or edit) their own table stylesheet which is then loaded instead of the file from the release zip file. Supply two possible alternatives - a blue and a grey (or gray) theme and added to documentation.

Will be present in release 1.3.0

Please color the issues based on the criticalness of them for example low priority as green and goes warmer to critical as red. both inside the control panel and inside the front end pages.

Use priority ranking. Divide it into 20 separate colours from blue (low) up to red (high). Base colour on the ranking (1-99).

Will be in release 1.3.0.

Noticed that the time values seem random on the issues. Investigate.

Added a small routine to check whether the time element is set. It also checks that the day and month are set as well before proceeding. It will use the current time elements if they are blank.

Joomla 2.5.4 changed the creation of the Super User (admin) account such that a random id is now assigned. This could cause conflict with the sample data provided with the Issue Tracker component, specifically the people data which uses a rangle from 2 to 18.

Reworked dbtasks model to resolve the possible presence of the super user id in our desired range.

The #__it_emails table is not removed from the database when the component is un-installed.

Add line to uninstall.mysql.utf8.sql file in sql directory.

DROP TABLE IF EXISTS `#__it_emails`;

It would be nice to be able to choose which columns are displayed in the back end issue list displays. The current choice is fine, but what if I desired an extra one?

Probably only required for issue list due to the number of fields available.

Added an option to config the assigned_to, identified_by, created_by, created_on, modified_by and modified_on fields in the admin issue list list displays.

Will be in the next release (1.2.1 or 1.3.0 which ever comes first).

I can't save an issue and get the error below. "Save failed with the following error: IssueTrackerTableItissues: :store failed. Cannot add or update a child row: a foreign key constraint fails (`omnipote_jos1`.`jos_it_issues`, CONSTRAINT `jos_it_issues_identified_by_fk` FOREIGN KEY (`identified_by_person_id`) REFERENCES `jos_it_people` (`id`)) SQL=INSERT INTO `jos_it_issues` (`id`, `alias`, `issue_summary`, `issue_description`, `identified_by_person_id`, `identified_date`, `related_project_id`, `assigned_to_person_id`, `issue_type`, `status`, `state`, `ordering`, `priority`, `target_resolution_date`, `progress`, `actual_resolution_date`, `resolution_summary`, `created_on`, `created_by`, `modified_on`, `modified_by`) VALUES ('0', 'AS9CLATYUQ', 'test', 'test', '42', '2012-09-03 17:36:57', '1', '1', '1', '4', '0', '1', '2', '', '', '', '', '2012-09-03 07:37:11', 'jr@omnipotent.com.au', '', '')"

Following changes made.

On the back end:

In config.xml:
Change line 28 to:
query="SELECT user_id AS value, person_name AS person FROM #__it_people WHERE user_id IS NOT NULL"/>

In helpers/issuetracker.php:
After line 173 add:
/*
* Given a real user->id get the associated it_people id.
*
*/
function get_itpeople_id ( $user_id )
{
$db = JFactory::getDBO();
$query = 'SELECT a.id FROM #__it_people AS a WHERE user_id = '.$user_id;
$db->setQuery( $query );
$id = $db->loadResult();

return $id;
}

In models/itissues.php
Replace line 238 with:
if (empty($data['identified_by_person_id']) || $data['identified_by_person_id'] == 1) {
$data['identified_by_person_id'] = IssueTrackerHelper::get_itpeople_id($user->id);
}

On the front end:

In models/itissues.php
After line 320 add:
$def_identby = $this->_params->get('def_identifiedby','0');

Replace line 345 with:
if (empty($data['identified_by_person_id']) || $data['identified_by_person_id'] == 1) {
if ( $user->guest ) {
$data['identified_by_person_id'] = $def_identby;
} else {
$data['identified_by_person_id'] = IssueTrackerHelper::get_itpeople_id($user->id);
}
}

Might also need to go into the component options and set the correct default assignee before attempting to save the first issue.

Pre-release 1.2.1 zip file send to identifier for testing and feedback.

User has confirmed it fixes their problem 11th Sept 2012

Handle the situation where a person uses the 'Create an Issue' link and they do not have permission to use it.

So instead of a 500 message or a condensed issue creation screen they get an informative message and a redirection.

Re-implement the redirection is an attempt is made to raise an issue and there is no authorisation. This changed at release 1.2.0. This change returns it back to how it was in release 1.1.0

From forum entry.

Anyway. When i try to install Issue Tracker i get now error messages, however, when i click the link to the administrator interface, it seems like the interface cannot find the English translation file. Every line is the name of the translation-string.

I have tried looking at my server at the location where all translation are stored and the Issue Tracker translation is there.

I am using a relatively fresh install of latest Joomla and latest Issue Tracker.

Error on line 591 of administrators com_issuetracker.ini file, where there are two sets of double quotes where there should be a single double quote.

Resolved in 1.2.1

After submitting a ticket the ticket number is displayed along with the message "You must provide at least one recipient email address". I have tried this with various created users who all have emails (that I have access to) they are all shown under people along with their email. When I first created the users I received the emails that Joomla sends out to a newly created user. I am assuming that Issue tracker uses the same mechanism.

Fixed query string. I release 1.2.1

Also require Issue Administrators to be defined. Will now provide an informative message to that effect in the back end.

When I create a new menu item and select "Single Project" under "Issue Tracker",
I get the following error:

Unknown column 'published' in 'where clause' SQL=SELECT id AS id, project_name AS name FROM jos_it_projects WHERE published=1

Query should have state=1 and not published=1.

I am not using any SEF products, my global Configuration settings in the back end are:

Search Engine Friendly URLs - Yes

Use URL rewriting - Yes

When User A clicking on Editor Icon the link is as follows:

itissues.edittask=itissues.edit&a_id=36&return=aHR0cDovL2p....

And then displays my 404 address page in the URL bar

If I set Use URL rewriting - NO and click on the editor icon the link is as follows:

index.php/show-my-issues/itissues.edit?task=itissues.edit&a_id=36&return=aHR0cDovL.....

The address in the URL bar then displays index.php/show-my-issues?view=form&layout=edit&a_id=36&return=aHR0cDovL2p0.

Modified the icon.php link to the edit screen.

Tested on Chrome & Firefox.

Fixed in 1.2.1

The front end edit form displays differently in different browsers, particularly between Firefox and Chrome.

Restructured form layout so that they display the same on browsers.

One of the things missing from the front end is for an issue administrator to see ALL of the issues so that they may edit them. This option permits this.

Added option and some checks to ensure that the logged in user is an issue administrator.

If a default assignee is defined there would never be any entries in the 'Unassigned report' which makes its presence somewhat redundant.

Added option and default is not to display the unassigned issue report.

Will be in next release (1.2.2 or 1.3.0 which ever comes first).

Noticed that when an issue is marked for closure that the resolution date is not being updated which it should be (on the back end). If a resolution date is specified it does get entered.

Found a situation where the date was not being set, so have modified the model code. It only occured on the back end.