Issue tracking application extending GitHub's issues and pull requests for the Joomla! project.
JavaScript PHP CSS HTML Shell ApacheConf Puppet
Latest commit e5051ef May 5, 2017 @elkuku elkuku [docu] Fix a link
Failed to load latest commit information.
.github Issue/PR templates Feb 17, 2016
.openshift Use the "use_composer" marker Jul 24, 2015
Documentation [docu] Fix a link May 5, 2017
bin Create a symlink to `tracker.php` with alias `jtracker` in `bin` Feb 2, 2014
build Add php7 support Feb 12, 2017
cache Add a /cache/.gitignore file Jun 23, 2013
cli fix warnings Apr 21, 2017
etc Support prepending a path on Crowdin (Ref #882) Sep 23, 2016
logs Remove log Nov 30, 2014
src Merge pull request #963 from zero-24/iftherearenochanges May 1, 2017
templates Template updates Apr 25, 2017
tests js files Apr 21, 2017
www Template updates Apr 25, 2017
.gitignore Use Symfony's Asset Component for building media asset URLs, set up s… Nov 24, 2016
.gitmodules Framework for automated testing (Ref #101) May 6, 2013
.php_cs Add a few more fixers consistent with existing style structures Jul 23, 2016
.travis.yml Rebuild Travis matrix, only test PHP 7 now Feb 12, 2017
Gruntfile.js Fix path, actually include JS Aug 13, 2016
LICENSE License file Feb 25, 2017 Update README with PHP 7 bump Feb 12, 2017
Vagrantfile Add php7 support Feb 12, 2017
bower.json Updated Octicons Aug 13, 2016
build.xml Do a once over on the documentation Jul 27, 2016
composer.json Update dependencies May 3, 2017
composer.lock Update dependencies May 3, 2017
credits.json Transifex removed Jul 10, 2016
package.json Make Octicons a Bower package, add tasks to rewrite CSS for some asse… Mar 13, 2016
phpunit.xml Clean up the unit test command a bit, update test environment Mar 25, 2016

Requirements Build Status Scrutinizer Code Quality Crowdin

The issue tracker application requires a server running:

  • PHP 7.0 or later
    • PHP's ext/curl and ext/intl should also be installed
  • MySQL 5.5.3 with InnoDB support (required to support the MySQL utf8mb4 charset)

The application also has external dependencies installable via Composer and Bower.

See also: Dependencies.

Note: All references to bin/jtracker refer to an executable symlink to cli/tracker.php. If you cannot execute the bin/jtracker symlink replace that path with cli/tracker.php


  1. Clone the git repo to where ever your test environment is located or download a ZIP file.
    • Note If you plan to contribute to the project, you might have to use git clone --recursive to get the submodules checked out.
  2. Copy etc/config.dist.json to etc/config.json.
  3. In the etc/config.json file, enter your database credentials and other information.
  4. Run composer install (or the equivalent for your system) to install dependencies from Composer.
  5. From a command prompt, run the install command to set up your database.
    • bin/jtracker install

If you are making a change to the issue tracker's web assets, you'll also need to set up Bower and Grunt. Please see the Asset Management documentation for more information.

Verify the installation is successful by doing the following:

  1. View the site in your browser.
  2. Run the get project command to pull issues, issue comments and other information related to the project from GitHub.
    • bin/jtracker get project

See also: CLI script.

Virtual Test Environment

As an alternative method, there is a setup for a virtual test environment using Vagrant and VirtualBox.

See also: Virtual server documentation

Using Login with GitHub

If you want the 'Login with GitHub' button to work properly you'll need to register an app with GitHub. To do this manage your account at and go to the applications page. Create a new application.

You'll be asked for the application URL and the callback URL. This can be your test server or your localhost environment. As long as you enter the URL that your localhost app is running on. An example might be http://jissues.local.

Once you've registered the app at GitHub you'll receive a Client ID and a Client Secret, enter these into your installation's etc/config.json file, along with your GitHub login credentials. You should now be able to login with GitHub successfully.

See also: GitHub Authentication

Support & Discussion