This support Issue Tracker FAQ (Frequently Asked Questions) is intended to assist you in answering some of the more common questions that are raised. It is intended to supplement the Issue Tracker documentation.
Issue Tracker is a Joomla component that assists in the tracking of issues or problems with a project, or an item that can be uniquely identified. Based upon a product originally running upon an Oracle database using Oracle's Application Express product it has been used internally for several years. This version has now been ported over to Joomla and following extensive internal testing is now being made available to the wider public. The product documentation describes the product in more detail.
If you find the product useful please consider making a donation to fund future development and support.
Release 1.6 and below run upon Joomla 2.5.x and Joomla 3.x
Release 1.7 and above run upon Joomla 3.4 and above.
The latest version of the product documentation is available in PDF format at this web link.
No the status code are configurable on the 'Statuses' tab in the Back end administration. There are a few supplied status codes to get one started (which are also used by the sample data), but these can also be edited to anything you desire.
The default project and a default user (known as the anonymous user), both with a default identifier of 1, are used to establish defaults for issues where they are not specifically defined. The names and details of these may be changed as the site requires. It is possible to define alternative defaults in the parameters.
It is also possible to define different default assignees for each project or sub-project.
No, these are values supplied to help one get started. They are also used by the sample data. They can be edited and changed as required by the site.
Note: Be aware that prior to release 1.2.1 the issue states of Open (id=4) and Closed (id=1) were treated as being special within the component and were used to initiate emails (if configured) to interested parties. In these early releases the specific id's should not be deleted, although the name (spelling) can be changed. In release 1.2.1 these are now configuration options.
When installed, the component synchronises the existing Joomla users and creates entries in the it_people table. In addition as new users are registered with Joomla these users are also added to the it_issues table. It is an administrative requirement to set the appropriate setting for these users within Issue Tracker. However it is recognised that occasionally users may be accidentally deleted and for this reason we provide a mechanism to re-synchronise the Joomla and Issue Tracker users table. It is very likely that it will never have to be used on your site. Note that if unregistered users are configured to be created upon the site, that these once deleted will not be recovered by resynchronising since they exist only in the component tables, not in the Joomla users table.
Yes the default roles can be defined in the Back end administration. The supplied roles are samples only and are supplied to help get the site started. They may be removed, changed and added too, as the site requires. Note that the 'CEO' and 'Manager' roles are 'special in that they do not accept a default project assigned. This 'feature' is implemented by code and can not (currently) be altered. The sample roles are also used by the supplied sample data.
[It is not a requirement to use any of the roles supplied, but in particular it is probably wise not to use the specific ids associated with the CEO and Manager roles if it is a specific problem for your site.]
These instructions are modified from an original article in Joomla magazine September 2011 and reproduced here for your usage.
Copy the file ''component.php'' from the folder joomla-installation/templates/system to the root of the the template folder of your template that you are using: (for example: joomla-installation/templates/rhuk_milkyway/component.php).
If you need to overwrite some component.php in your new placed template folder, don't do it, as it may include code that the template needs to use (I don't know, but it's safer if you don't do this action in this case).
Search for the line that states: <body class="contentpane"> Around lines 47 on beez_20 template.
Now, copy and place this code right under it: <img src="/www.yourwebsite.nl/templates/your-template-folder/your-images-map/logo.png" alt="Logo" /> To use a relative URL use it relative to the httd directory. i.e. src=”<?php echo $this->baseurl ?>/templates/your-template-folder/your-image-map/logo.png” where you use the appropriate folder and logo name for your site.
Just change the source of the image so it matches exactly the image that you want included, and that's it!
An indefinite level of sub-projects can be created. Just be aware that in the displays that the project name is composed of the concatenation of all the sub project levels along with the top parent project name. If long names are used this could make the complete project name very long.
Yes, there is a limited ability to edit the Issue Tracker users, but these users are derived from the Joomla site registered users, so most of the information is derived from Joomla. It really only makes sense to edit the user role, the email notification and default assigned project details.
No, only issues and projects marked as 'Published' will be displayable on the front end. Remember also that the display of the projects and issues list is controlled through the menu options as well. It is worth mentioning that the 'Issues List' display can be configured such that only certain projects are included.
Issues marked 'PRIVATE' will not be visible on the front end except to Issue staff and the person who raised the issue.
Note that if suitable configured, issue administrators can edit any issue, published or unpublished in the front end.
Yes there are configuration options available on the menu item that determine which columns are visible on the front end. For example it may not be desirable to display the audit fields.
It is also possible with release 1.3.0 (and above) to use custom CSS to style the front end displays.
This is part of the design criteria. Users who have a role of CEO or Manager are expected to be associated with many projects by default, so it does not make any sense to assign them any one specific project. The default project is really intended to make the entry of issues easier by populating the project field automatically.
There are currently three plug-ins installed with the component.
This initial release does not support any database other than MySQL. This is mainly due to the fact that it has not been tested, more than anything else. There is some work under way to support SQL*Server and MS-Azure but we are generally not aware of any demand.