Issue Tracking
Issue tracking software is used to keep track of problems and tasks, including due-dates, who is responsible, outcomes and so on. Wikipedia maintains a comparison of issue tracking software solutions. Issue tracking software sometimes requires a server to be set up. Before attempting to set up your own, talk to either your eResearch Analyst or your on-campus IT support group to discover hosting options available to you.
|
What is it and how do I get it? |
When should I use it? |
What caveats or obstacles are there? |
*Support? |
|---|---|---|---|
|
JIRA |
Use JIRA if you want to track your issues using an easy to use and highly customisable tracking system. Also, use JIRA if you are tracking issues for more than one project at a time. |
JIRA can be difficult to maintain if you want to make a lot of customisations to it. |
External (Intersect) or End User |
|
Trac |
Use Trac if you need a simple to use issue tracking tool or need excellent integration with version control software such as SVN. |
Trac can be difficult to install and it doesn’t have good support for managing issues for more than one project at a time. |
End User
|
|
* Support |
Source of Support for Service |
|---|---|
|
UoN Supplied |
Deployed, managed and supported by the University and provided to Researchers at no additional cost. |
|
UoN Supported |
Deployed, managed and supported by the University with some additional costs to the Researcher, Centre or Faculty. |
|
End User |
The item is end user supported. The University is not in a position to provide technical support or assurances that the product will work within the University environment. |
|
External |
Deployed, managed and supported by an organisation external to the University. Additional costs may apply. |