I am using fossil tickets as TODO items for new features that must be
implemented. Often, I realize that I can break a new feature into smaller
sub-features. So, logically, the plan changes from
- Ticket A
to
- Ticket A
- Ticket A.1
- Ticket A.2
This can be recursive, so the initial Tic
On Sun, Mar 27, 2011 at 8:48 PM, wrote:
> I know it's possible to create custom ticket reports, but reports are
> still flat lists, not hierarchies.
>>
> Are there any plans to make ticket management easier in fossil, by
> making it possible to group them into trees
Part of what you are asking c
2 matches
Mail list logo