Apologize, I must have added this long ago, however, I wouldn't say it is
unusual. Trac also uses the concept of ticket and I am pretty sure there
exist others.
Cheers,
Jacek
2010/2/10 Ron Aaron
> On Wednesday 10 February 2010 10:37:51 Jacek Cała wrote:
> > For me tickets are ok and by defa
On Wednesday 10 February 2010 10:37:51 Jacek Cała wrote:
> For me tickets are ok and by default you have type 'Task' configured.
> If you create a report that filters by this, isn't it enough?
Actually, the default is:
set type_choices {
Code_Defect
Build_Problem
Documentation
Feature_
For me tickets are ok and by default you have type 'Task' configured.
If you create a report that filters by this, isn't it enough?
Regards,
Jacek
2010/2/10 Ron Aaron
> Concerning ticket [2b79f36e5a], I agree with the notion. However, I would
> take it a bit further and say "issues" rath
Concerning ticket [2b79f36e5a], I agree with the notion. However, I would
take it a bit further and say "issues" rather than "tickets", throughout the
product. I would also add a "Todo" type (well, I have in my own projects), as
Fossil is an excellent way to keep track of meta-issues as well
4 matches
Mail list logo
