Issue Tracker Component
The Macrotone Consulting Issue Tracker component has its origin in a ‘Problem Management System (PMS)’ developed many years ago on an Oracle Database using Oracle Forms. It migrated to an Oracle Application Express (APEX) based application and incorporated ideas from a sample APEX application. This version takes the ideas and implements it upon a MySQL database using Joomla as the interface. It runs upon Joomla 2.5 and Joomla 3.2. As time and circumstances permit some of the original program features may/will be re-implemented on the new platform.
Wikipedia defines an Issue Tracking system (ITS, trouble ticket system, support ticket or incident ticket system) as a Computer Software package that manages and maintains lists of Issues (computers), as needed by an organization. Issue tracking systems are commonly used in an organization's Customer Support / Call Centre to create, update, and resolve reported customer issues, or even issues reported by that organization's other employees. An issue tracking system often also contains a Knowledge Base containing information on each customer, resolutions to common problems, and other such data. An issue tracking system is similar to a "bug tracker", and often, a software company will sell both, and some bug trackers are capable of being used as an issue tracking system, and vice versa. Consistent use of an issue or Bug Tracking System is considered one of the "hallmarks of a good software team".
This implementation is suitable for a small or medium sized organisation to record and efficiently respond to reported problems / issues.
This release is intended to corret any problems found with the earlier 1.6.0 release. It also introduces a new scheduled task to Auto Close issues in 'waiting for user' status which are not responded to in the specified time period.
This release adds two new requested changes. The first is a restructuring of the Issue Progress information into its own separate table, and provides individual control over each progress record change. The second is the introduction of Custom Fields such that each project may have as many or as few specific fields that a site may desire for the collection of additional information to aid in resolving problem reports. There is also a change to permit the addition of mutliple attachments to an issue in the front end, and for the user to provide a descriptive title for each attachment.
This release adds the ability to configure issue assignees by project, which is used in preference to the component defined assignee. It also corrects two major and several minor problems discovered after the earlier 1.5.1 release.
This release corrects one major and several minor problems discovered after the earlier release.
This release accomodates installing upon both Joomla 3.2 and Joomla 2.5 in one package. The code base has undergone some extensive review and a number of minor fixes incorporated. One major bug reported on a couple of Joomla 3.1.x sites involving saving of a project in the back end has also been resolved.
The release has introduced tow major new features. The first is the incorporation of advanced auditing making use of the underlying database features, but it does require the hosting site to provide the ability to use database triggers. No all hosting sites provide this feature but most of the larger suppliers do.
The second major feature is the ability to run scheduled tasks via a cron entry. The topic of scheduled tasks is quite large and the details are provided in the User (and Design - requires registration) Guides. We have currently implemented two reporting tasks: one for a summary report, and one for an assignee status report. In addition we have also implemented a mechanism to fetch 'email' from an IMAP or POP3 account enabling issue reports to be submitted, and updated via email. Before implementing this upon your site we strongly recommend reading the documentation so that you are acquainted with the implications.
This is a release for the Joomla 3.1 branch. The main change in this release is the ability to run upon 'hosts' that do not permit the use of database views, triggers and procedures. It resolves a few minor problems and incorporates changes developed from the 1.3 branch.
This release is intended for Joomla 3.1 and includes fixes for the bugs (opportunities for improvement) found in the earlier 1.4.0 release. It resolves the problems with the Tag implementation which was broken in the Joomla 3.1.4 update and also includes all the changes incorporated in the Issue Tracker 1.3.3 release. There are also changes to the installer which will be transparent to the users but lowers the component installed footprint. It also incorporates the Latest Issues Module as part of the release, avoiding the need for a separate download. The reason for this later change is due to the number of reported problems caused by the wrong version of the module being used with the component release.
This was an Alpha release only for Joomla 3.1. It was intended as a 'test' releases to allow administrators to see how it would work with the Joomla release. It was based upon the Issue Tracker 1.3.1 release.
The minor release resolves a few minor problems with the earlier 1.3.3 release but also introduces a few of the requested improvements. The details are shown in the 'changelog' link shown above.
The minor release resolves a few minor problems with the earlier 1.3.2 release but also introduces a few of the requested improvements. These include the ability to have issues and projects associated with specific user groups, thus restricting who can view specific issues and/or projects. The search plugins have also been updated to enforce this security. One other requested feature is the ability for 'staff' members to be able to edit issues in the front end. This means that Issue administration rights do not have to be given so widely. Issue Adminstrators also now have the ability to 'delete' issues from the front end. Another requested feature was the ability to prevent the re-opening of closed issues. This option applies to users and staff members and the default is to not allow closed issues to be re-opened. Issue Administrators are exempt from the restriction and can always reopen closed issues. The details are shown in the 'changelog' link shown above.
The minor release resolves a few minor problems with the earlier 1.3.1 release and also introduces a few of the requested improvements in usability. In particular the finder (smart search) plugin is ready for production use with this release. The details are shown in the 'changelog' link shown above.
The minor release resolves one major problem and a few minor problems with the earlier release. The details are shown in the 'changelog' link shown above.
The release builds upon the features of the earlier releases. The full list is shown in the 'changelog' link shown above.
Some of the main areas of change are as follows:
- Ability to use customised CSS stylesheets in front end displays
- Ability to add 'attachment' files to issues.
- Event logging (initial implementation).
- Reworking of projects table.
The documentation is accessible from the 'Joomla extensions menu' on the right hand side of this page.
There is a released module mod_latest_issues available in the download area. This module has now been incorporated within the main component release package since version 1.4. The documentation is included as part of the main Issue Tracker documentation.
Issue Tracker Overview
The documentation in PDF format and also as web pages is available upon the site. [Please see links under 'Joomla Extensions' on the site.] There is an additional Issue Tracker Design guide which was previously part of the main documentation and it is also available to registered users in both formats. This document only presents a brief overview of the functionality.
There are three main parts to the component, users (who are Joomla registered user and non-registered Issue Tracker only users), projects and issues (sometimes also known as tickets, problem reports etc.)
Users: Within the component users all have a specific role, whether it be as a customer (or user of the web site) or as a member of staff (where they may be a manager, project lead, project member etc.) The component assigns a role to each user which is managed by the administrator. Each user is also assigned a default project, which is used to set a default when an issue is raised. Non-registered users can be created automatically when a guest raises an issue, and these are used to assist in identification of user issues.
Projects: These are distinct 'category like' items, which may or may not consists of separate sub-projects. i.e. If we have a main project named 'New component', we may have sub-projects named 'Release 1.0', 'Release 2.0' etc. As many levels of sub project can be created as desired but usually two or three is sufficient for most projects. Projects have a description and a start and end date. They also have a target end date, which may or may not be the actual end date of the projects.
Issues: Issues are the problem reports themselves, raised either by the site users themselves via a front end screen, or on their behalf by a staff member within the site administration. Issues are associated with people, as they are identified (or raised) by a person; a person is also assigned to work (or manage) the issue through to completion. An issue is also associated with a project or sub-project. The issue will consist of a number of separate pieces of information such as a description; a series of progress steps; and a resolution. All of these are tracked by the component.
Most of the activities performed by the component take place in the back end, although certain displays are available as menu items on the front end of the site, and it is possible for site users to raise an issue (if configured). This may be configured to require site users to register with the site or may be open. If open then the user is required to enter certain pieces of information other wise the issue will not be saved. Captcha entry is configurable using ReCaptcha. There are also Spam and IP blocking configuration options.
We trust this brief overview is sufficient to cover the main features of the components and you are requested to look at the latest PDF documentation for more information.
If you find this component useful, you are requested to raise a review on the Joomla Extensions Directory, and possibly consider making a donation to assist in providing support and future enhancements.
We would like to thank all the people who have donated their time and effort in providing translations for our extensions, either individually or as part of a translation team, so that they may be used by the wider community.
Requested features being considered for future releases.
|Requested Change||Possible Version for implementation|
|Import/Export Facility||v1.8.0 (est)|
|Graphical Reports||v1.7.0 (est)|
|Multi-Lingual Site Features||v2.0.0 (est)|
|Progress details restructure.||v1.6.0|
Recently Closed Issues
Close date: 2014-04-14 07:00:00
Close date: 2014-04-10 11:00:00
Close date: 2014-04-09 17:30:00
Close date: 2014-04-07 14:00:00
Close date: 2014-04-06 15:00:00
If you use and find our Joomla extensions useful please consider supporting their further development.
Quote(s) of the Day
Feeling gratitude and not expressing it is like wrapping a present and not giving it.
William Arthur Ward
A journey of a thousand miles begins with a single step.
What we think, we become.