| Bug
Tracker / Request |
Create work orders for a later
date |
View queues |
Modify and grab queues/tickets |
Sort by time,
date, account, who owns, type, requestor |
Need report to say who did what |
If dependent on cc, then will attache a simple sheet behind cc worksheet
saying what item for data to release.
Those would route to data first!
Could be tricky. |
Need check item that says paid/no money needed before releases to
production!!! |
Must
have history! |
|
|
|
|
|
|
R |
R |
R |
R |
R (would
have to be done manually) |
|
R (mimics it with bugnote
feature) |
|
| Mantis |
Generally, Mantis takes the date
that the bug was created and sorts on that.
There is an "ETA" field so that you can specify when the
request is due/how long it will take. |
You can do this from the very
flexible "View Bugs" page by applying filters. |
can change "assigned
to". "priority" and most other information except
"reporter" and date submitted" |
You can sort by time/date on the
first page with the "view all bugs" page. The filters on the top of that page allow
you to additionally sort by who owns, type and requestor. Though "type" and
"accounts" have yet to be added to this db. |
What
other reporting tools do we need, specifically? Pretty good reporting tool
"summary_page.php", but they aren't very detailed. It says, in general, who
closed/open/resolved how many bugs. |
there's no such functionality as
"scripts" like RT, this would have to be manually assigned to data. |
Doesn't include this at the
moment. |
can mimic a history feature by
adding bug notes. These keep track of
who is publishing the note and what time/date it has. |
|
|
R |
R |
R |
R |
|
R (would have to be
done manually) |
|
R |
|
| RT |
You can do this within Ticket
creation |
Can view queues by 1) going to
advanced search and specify queue or from the front page |
yes, includes concept of
"stealing" |
yes, the advanced search option
allows you to specify criteria like "started date/time",
"priority", "queue", "subject", and
"content" |
Doesn't seem to have any
reporting tools included. But there
are a lot of add-ons that users have contributed. |
you can attach documents and you
can specify in the text box what data needs to do to release. We could eventually create scripts to
automatically send this to data. |
Doesn't include this at the
moment. |
Great history of ticket included
and color coded by major changes to ticket. |
|
|
R |
R |
R |
R |
R |
R (would have to be
done manually) |
|
R (mimics it with description feature) |
|
| DCL |
You can do this within workorder
creation. |
They include a concept called
"view". I've sent a
help-request to see if there's a "view-per-department" feature that
I'm missing from the app. If you modify
a WO you can change who is repsonsible and change the data of the WO. |
Modifying workorders is no
problem. Just use the drop down
menu. Within that you can also change
who is responsible. |
Can filter by person
"responsible", "product" and "status" by going
to the "Browse" page. You
can search by "account" and "time/date" by going to the "Search"
page.. |
Has some interesting reporting
tools. "Search"es can be
exported as a .txt document, there's graphs and lots of "timecard"
functionality. |
You can attach documents and can
specify that "data" is responsible, but this doesn't happen
automatically |
Doesn't include this at the
moment. |
history
is done by hand with dates and initials on the modify WO page, add
notes. Of the 3 tracking systems, this
history feature is the least "feature"-full. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|