Re: [fossil-users] Hierarchy of tickets in fossil

[Ron Wilson]

On Sun, Mar 27, 2011 at 8:48 PM,  v...@lavabit.com 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 can (probably) be accomplished in the SQL
query using the GROUP BY and ORDER BY clauses. THis would result in
each ticket being followed by its children. Unfortunately, I have only
rudimentary knowledge of SQL, so I don't know how to do this.

To get the list to be rendered in a tree structure, you could then use
Javascript. Most likely there is existing Javascript available that
can be adapted (or, possibly, simply configured) to work with the HTML
table generated from the SQL query.

The basic logic for an outline view of the tickets would be to check
the parent-id field of each ticket in turn. If the tcket has the same
parent as the previous ticket, then set the indent level the same as
the previous ticket. If the parent is the previous ticket, then
incement the indent level. If the parent is some earlier ticket, then
set the indent level to 1 plus the parent's indent level. If the
parent ticket has never been seen, then reset the indent level to 0.

I hope this is somewhat helpful.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Hierarchy of tickets in fossil

[vuk]

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 Ticket A becomes the root of a whole
subtree of tickets.

I know it's possible to create custom ticket reports, but reports are
still flat lists, not hierarchies.

For now, I manage ticket hierarchies by using an outliner, but it requires
lots of additional work: I have to copy ticket names and ticket IDs into
it. Are there any plans to make ticket management easier in fossil, by
making it possible to group them into trees like in my example? I'm
following the list for some time, but didn't notice any threads related to
this scenario of ticket management, hence my question.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users