Should we post bugs in the website database still?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Should we post bugs in the website database still?

TimM-3
I'm not quite sure if we post bugs in the website database and/or mention
them here?

What's your preference andy/blair?

In many ways you bug database is a bit limiting as I often want to go back
and add new information I've found out - but you can't (maybe that feature
is disable? If it doesn't have it - consider switching to Jira - its very
good... although some of the opensource ones like Mantis look interesting)

Tim


Reply | Threaded
Open this post in threaded view
|

Re: Should we post bugs in the website database still?

Sean Malloy-11
> In many ways you bug database is a bit limiting as I often want to go back
> and add new information I've found out - but you can't (maybe that feature
> is disable? If it doesn't have it - consider switching to Jira - its very
> good... although some of the opensource ones like Mantis look interesting)

TTP is better than either of those two tools. It just isn't designed for the
web. Which means you get that basic form to enter bugs into the DB. If you
had an actual TTP Client and connected to the server, it's a very rich tool.
I don't the OA guys are going to scrap TTP just because they gain a nicer
web front end.

Just post a follow up bug, mark it somewhere as being an ammendment for a
previous bug report. It'd be nice if we had a live feed into the DB, so you
could just say "This is an ammendment to TTP Item #1995" or something.
Currently the list is manually generated