Each developer can configure their own dashboard to layout and display the most useful information they need to help them with their job. There are a host of different panels to choose from so that developers and team leaders alike can get a view of the information they want to see.
For example for team leaders, there are panels to summarise developer activity and highlight current bug priorities and for developers there are panels to show times in different countries and the latest product notices.

Through roles and profiles define how you want you customers to view your data. Should it be view only? Or can they update their bugs? It's up to you.

All activity and changes to a bug are recorded in the history so any developer picking up an bug can see exactly what's happened to an bug through the course of its lifetime.

A full hierarchical FAQ system is built-in to the system. To speed the answers to new bugs, the FAQs can be searched and browsed directly within a bug.

Each of your priorities can have their own SLA timings. To ensure you respond to bugs within your set SLA times, notifications combined with a management monitoring allow you to control your bugs that are under SLA.

All the system lists are fully customisable in IssueCentre so that you can classify and report on bugs exactly as you need to.

No software is required to be installed by developers or customers to use IssueCentre. The application will work in all modern browsers and has been certified with the recent versions of Internet Explorer and Firefox.

Reports are automatically generated for weekly, monthly, quarterly and bi-annual periods. Because they are generated automatically they are quick and slick to view, with graphs and pie charts to give you a good view of how your work is split and how your developers are performing. In addition, the raw data of the charts can be exported to CSV so that you can process the data in other applications as required.

FAQs can be made available just to your internal developers or shared with your customers on the self-service customer service portal.

Each bug is classified with the type of problem that has raised the bug. It's critical that the classification list is kept clean so that from your reports you can understand what problems are taking the most time and bugs. To prevent the need to have a wide list of general error classifications, in addition to cross-product errors (such as Password Reset) you can create errors that are specific to a product.

Any number and type of files can be uploaded and associated with a bug so that screenshots, config files, debug logs etc. can all be shared between developers to help resolve the bug.

IssueCentre's high configurability extends to keeping you and the customer informed of activity happening in IssueCentre. There are many different reasons for setting up notifications, from keeping customers informed on the details and progress of the bugs you've created for them, through to your management being alerted to SLA breaches, or your most important customer logging a bug themselves. IssueCentre allows you to create notifications for each different type of activity along with dynamic content so that each stakeholder can see just the information pertinent to their interest.

IssueCentre is built on standard, reliable, scalable technologies. It uses JBoss J2EE server, backed by a PostgreSQL or SQL Server database, all of which can be scaled outwards with multiple clustered servers.

The banner can be customized to show your logo and branding and your primary brand colours can be configured to display throughout the application.

An extensive WebServices API that returns XML to allow you to integrate the creation, updating or retrieval of bugs from your other business systems.

Developers can set reminders on bugs to help them to remember to return to a bug on a particular date & time - useful if, for example, the customer/vendor is going to be uncontactable for a few days.

Because customer service never ceases your developers need to be able to work on multiple bugs at a time. For this reason we open each in a new window to facilitate developers working on multiple bugs at one time.

Define your own templates to speed the entry of standard bug bugs and email responses.

Tags allow you to categorise your bugs with further meta-data however you wish. Permissions allow you to control whether developers must use a controlled structured list or have free capability to add tags as required.

Import your developer details from your Active Directory or other LDAP directory and use it as the authentication means so that users dont have to remember another password.

Our two methods of search meets everybodys needs. Our web-style single field type anything search is super simple to use and along with our innovative text notation is really quick to use.

You can save frequent search criteria and then run from a single click. Your most recent searches are also saved automatically so that likewise you rerun them from a single click.

Be warned of lost/missed/forgotten bugs with our new idle notification. Decide for yourself exactly the criteria and frequency of your reminders to make sure you dont miss an bug again.

Privacy settings allow you to prevent your customers from seeing certain files and activity on their bugs.