Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Trac: Tickets

[The Trac Project] #886: Add support for Master tickets

 

 

First page Previous page 1 2 3 4 5 Next page Last page  View All Trac tickets RSS feed   Index | Next | Previous | View Threaded


noreply at edgewall

Nov 5, 2004, 6:44 AM

Post #1 of 111 (5928 views)
Permalink
[The Trac Project] #886: Add support for Master tickets

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: new
Component: ticket system | Modified: Fri Nov 5 06:44:10 2004
Severity: enhancement | Milestone:
Priority: normal | Version: 0.7.1
Owner: jonas | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
It would be cool if you could create master tickets that other tickets
refer to. Work could then be broken down into chunks (and assigned to
different people), but the master ticket could only be closed when all
referring tickets had been resolved.

You could also have it so that referring tickets are excluded from the
Roadmap ticket counts.

--
Ticket URL: <http://projects2.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Nov 5, 2004, 7:33 AM

Post #2 of 111 (5846 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: new
Component: ticket system | Modified: Fri Nov 5 07:33:42 2004
Severity: enhancement | Milestone:
Priority: normal | Version: 0.7.1
Owner: jonas | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Comment (by zilvinas [at] gemtek):

That sounds like project. Each task is composed to of tickets, the only
way to complete 'task' is close all tickets. Sounds like a good idea.

--
Ticket URL: <http://projects2.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Nov 5, 2004, 8:41 AM

Post #3 of 111 (5852 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: new
Component: ticket system | Modified: Fri Nov 5 08:41:25 2004
Severity: enhancement | Milestone:
Priority: normal | Version: 0.7.1
Owner: jonas | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Comment (by cboos [at] bct-technology):

That even sounds like ''milestone'' to me...

What about a little rework of the '''Roadmap''' module
and the ticket and milestone objects.

Let me explain the idea.

Instead of having distinct ticket and milestone objects
as we have now, we should only have tickets, but different categories
of tickets:
* {{{ER}}} Enhancement Request (simple)
* {{{PR}}} Problem Report (simple)
* {{{Milestone}}} ... like the milestones we already have (aggregate)
* {{{MasterTicket}}} ... like suggested initially (aggregate)
* {{{Deployments}}} see #821 (simple)
* {{{Task}}} anything else (simple)
* ... etc. (the list can be customized

They would have a different icon for the timeline view.

The '''Roadmap''' module could show the (aggregate) categories:
Milestones, Master Tickets, ...

A (simple) ticket can be attached to an (aggregate) ticket:
* to a milestone, as it is done now (display in the combobox only
available milestone tickets)
* to a master ticket (display in that combobox only available master
tickets)

It remains to be seen if an (aggregate) ticket could itself be
attached to another (aggregate) ticket...
A master ticket attached to a milestone makes sense.



The great unification... :) (and we need to parse smileys too!)

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Nov 9, 2004, 5:23 AM

Post #4 of 111 (5833 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: new
Component: ticket system | Modified: Tue Nov 9 05:23:11 2004
Severity: enhancement | Milestone:
Priority: normal | Version: 0.7.1
Owner: jonas | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Comment (by dmurphy25 [at] csc):

You're quite right - reworking the modules and breaking down the tickets
into different types seems a good solution, and more flexible than simply
'bolting on' master tickets.

{{{Master}}} tickets should be children of {{{Milestone}}} tickets, but
not other {{{Master}}} tickets.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Nov 22, 2004, 7:14 AM

Post #5 of 111 (5831 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: new
Component: ticket system | Modified: Mon Nov 22 07:14:06 2004
Severity: enhancement | Milestone:
Priority: normal | Version: 0.7.1
Owner: jonas | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Comment (by Tristan Seligmann <mithrandi [at] mithrandi>):

This sounds like a dup of #31 to me.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Apr 20, 2005, 5:26 AM

Post #6 of 111 (5814 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: assigned
Component: ticket system | Modified: Wed Apr 20 05:26:43 2005
Severity: enhancement | Milestone: 0.9
Priority: normal | Version: 0.7.1
Owner: cboos | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Changes (by cboos):

* milestone: => 0.9
* status: new => assigned
* owner: jonas => cboos

Comment:

This is a kind of duplicate for #31.
However, there was an additional suggestion in the comments there
about being able to create ''child'' tickets, which fits nicely
with the original description of this ticket:

''Work could then be broken down into chunks (and assigned to different
people), but the master ticket could only be closed when all referring
tickets had been resolved.''

By adding a ''Create sub-ticket'', or ''Create child ticket'' link,
any ticket could be easily broken down into subtasks.
That link would create a new ticket '''and''' a __depends-on__
relationship
between the parent ticket and the newly created child ticket.
That way, one could only close the parent ticket when all its children are
resolved,
thanks to the solution for #31.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Jun 21, 2005, 12:58 PM

Post #7 of 111 (5806 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: assigned
Component: ticket system | Modified: Tue Jun 21 12:58:05 2005
Severity: enhancement | Milestone: 1.0
Priority: normal | Version: 0.7.1
Owner: cboos | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Changes (by cmlenz):

* milestone: 0.9 => 1.0

Comment:

Deferred.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Aug 3, 2005, 5:15 AM

Post #8 of 111 (5849 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
---------------------------+------------------------------------------------
Id: 886 | Status: assigned
Component: ticket system | Modified: Wed Aug 3 05:15:45 2005
Severity: enhancement | Milestone: 1.0
Priority: normal | Version: 0.7.1
Owner: cboos | Reporter: dmurphy25 [at] csc
---------------------------+------------------------------------------------
Changes (by Gunnar Wagenknecht <gunnar [at] wagenknecht>):

* cc: => gunnar [at] wagenknecht

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <>


noreply at edgewall

Aug 31, 2005, 6:08 PM

Post #9 of 111 (5855 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: normal | Resolution:
Keywords: |
-------------------------------+--------------------------------------------
Comment (by dmbrucker [at] gmail):

I'm really interested in this feature, it will really add some useful
workflow capabilities. I think it would be better, though, to make it more
generic: don't have a special type of ticket for a Master Ticket. A ticket
is a ticket is a ticket, each capable of N-levels of dependence and
reference. It should be the context of the reference that gives a ticket
its meaning in relation to the other tickets.

I see three types of relationships:

1) '''Depends on/Depended on by''': This would be a true blocking
relationship; the ticket could not be resolved until each ticket it
depends on is resolved. It does not necessarily mean that any ticket is
the parent or child of the other, just that there is a required order to
their completion. One ticket may be depended on by multiple other tickets,
i.e. Tickets A and B both depend on C. A ticket can be in any milestone
greater then or equal to the highest milestone of its dependencies.

2) '''Parent of/Child of''': This is the task+subtask context described
here and #31. The parent encapsulates a portion of work that is
accomplished through its collection of children. A child can only have one
parent. This type is definitely different then a milestone. The Milestone
page could either include or elide the child tickets, with the opposite
view being available with another checkbox below "Show already completed
milestones". Moving a ticket to another milestone would include the option
of also moving some or all its children. Individual child tickets could be
left in milestones lesser then their parents, especially if they are
depended on by a ticket in the lesser milestone.

3) '''Duplicate of''': All of the tickets describe a similar
bug/feature/request/problem. If A is a duplicate of B, and B is a
duplicate of C, then A is a duplicate of C. Taken as a group of tickets,
they all talk about pretty much the same thing. Since trac uses a linear
display of comments, instead of threaded, it might be better to keep the
tickets unmerged for readability and context. Rather then merging the
tickets, an interesting way of handling this might be to create a new
ticket of type 2 above, that is the parent of all the duplicate tickets,
just so it would be easy to find all the dups and see what had been
discussed in each.

Each of these relationships is independent of the rest. One ticket can
depend on another ticket of which it is not the parent. A parent can
explicitly depend on one of its children, requiring the child to be
resolved first. One ticket can be the parent of 9 other tickets, 3 of
which are duplicates. Etc. There may be more relationships that would be
useful to implement in the future.

This is a lot of description, and is basically just a brain dump. My main
point is that tickets should be generic when it comes to relationships. I
think it will help to keep them more usable and extensible later.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Sep 1, 2005, 4:14 AM

Post #10 of 111 (5834 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Changes (by cboos):

* severity: normal => major
* keywords: => relations

Comment:

Very interesting. Thanks for sharing your thoughts!
Let me add a few comments.

''don't have a special type of ticket for a Master Ticket''::
Yes. I agree with this too, now.
1) and 2)::
Very interesting. So far, I didn't make a difference
between the `<<depends-on>>` relation
and the `<<parent-of>>` relation.
But I see the point, now.
2) ''... This type is definitely different then a milestone.''::
You may be right, but I'm not yet sure about that.
Think about the Milestone view: it would also make sense for
a Master Ticket (i.e. any ticket with children) to be displayed like
that.
How many of its children (optionally including sub-children)
are completed and how many are left to be done,
the children ticket status by component/type/priority, etc.
3)::
Yes, but no need to create one more ticket: it would be
enough to display, besides the ''duplicate'' status, the list
of all the duplicated tickets (the transitive closure of the
`<<duplicate-of>>` relation).
''Each of these relationships is independent of the rest.''::
Yes. What I said above about the relationship between
the `<<child-of>>` and `<<depends-on>>` relations can
be implemented without too much complexity at the point
where the check is made to see if a ticket can be closed.
The check would be: there are no depended upon tickets
opened __and__ no child tickets opened.
''My main point is that tickets should be generic when it comes to
relationships.::
You're again quite right. It's the way I intend to implement it.
Support for that is already (partially) there
in the TracCrossReferences branch, and more is to come soon.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Sep 1, 2005, 3:14 PM

Post #11 of 111 (5812 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by dmbrucker [at] gmail):

''...it would also make sense for a Master Ticket ... to be displayed like
that...''
I totally agree. A "milestone ticket", one designated as the parent of
all tickets assigned to the milestone would be, I think, an excellent
design. I was responding more to what had been discussed, that this
feature could be a rework of milestones as they currenly are, which I
don't think is appropriate. But, if a ticket-type object with a couple
extra fields/features could be used for milestones as well, that would be
very good.

''...no need to create one more ticket...''
Even better! If this can be done _without_ creating an extra, ugly
growth type ticket, that's all the better.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Sep 17, 2005, 12:57 PM

Post #12 of 111 (5857 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Changes (by mrovner [at] propel):

* cc: gunnar [at] wagenknecht => gunnar [at] wagenknecht,
mrovner [at] propel

Comment:

see also #2075

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Sep 22, 2005, 9:40 AM

Post #13 of 111 (5849 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by asmodai [at] in-nomine):

Potential duplicate ticket: #2087?

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 8, 2005, 6:41 AM

Post #14 of 111 (5813 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by cmlenz):

#2193 has been marked as duplicate of this ticket.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 10, 2005, 10:09 AM

Post #15 of 111 (5829 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Changes (by trac [at] justin):

* cc: gunnar [at] wagenknecht, mrovner [at] propel =>
gunnar [at] wagenknecht, mrovner [at] propel,
trac [at] justin

Comment:

I like the idea of the milestone being replaced by a ticket that is the
parent of other tickets.

I am not sure that the <<depends-on>> and <<duplicate-of>> relation is as
important. I find navigation links fine for linking wikis to tickets,
tickets to other tickets. If a ticket truly depends on another one, then
it cannot be completed before the other is completed, so who would do so?
Simple links to the other tickets will give enough information for this.

<<child-of>, however, really is useful to have explicit because then
milestones can be replaced, tickets can be half-done, and you can form a
hierarchy of increasing levels of task abstraction, which is very useful
for project management. Clearly, a parent ticket cannot be closed before
all its children (subtasks) are complete.

This also ties in nicely with the idea of "Actionable" tickets (see #31).

I think that once the scope is narrowed to only the special <<child-of>>
relation, TracCrossReferences becomes overkill to achieve this.

I disagree that relationships should be handled in a generic way, because
they are not generic (some have explicit logic behind them, which is why
we need them in the first place instead of just using navigation links)
and there are only a few (IMHO one, others think three) that will ever be
useful to the majority of users.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 10, 2005, 10:37 AM

Post #16 of 111 (5849 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by cboos):

''I think that once the scope is narrowed to only the special <<child-of>>
relation, TracCrossReferences becomes overkill to achieve this.''

That's the opinion stated in #2087. Well, we'll see what
that alternative approach will provide.

I'm currently busy with the low-level sqlite issues,
but as soon as this is done, I'll try to get some progress
on this topic, using the TracCrossReferences approach.

I fail to see why having a generic support for
relationships between objects prevents one to
associates some logic to those dependencies...
Consider it's simply a programming convenience,
which enables one to write code like {{{ for child in ticket.relation
('parent-of'): ... }}}

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 10, 2005, 2:27 PM

Post #17 of 111 (5809 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Changes (by dpeterson <dpeterson [at] enthought>):

* cc: gunnar [at] wagenknecht, mrovner [at] propel,
trac [at] justin => gunnar [at] wagenknecht,
mrovner [at] propel, trac [at] justin,
dpeterson [at] enthought

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 11, 2005, 7:05 PM

Post #18 of 111 (5824 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by trac [at] justin):

I have added a specifications proposal for SubTickets on the wiki. It
summarises a lot of what was discussed in this ticket and #31 (and a lot
of my own opinions). Once I get some feedback I will begin implementing
the changes.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 13, 2005, 9:28 AM

Post #19 of 111 (5814 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by dpeterson <dpeterson [at] enthought>):

I personally like what you've proposed except that I think the logical
starting implementation should not include any attempt at swapping in
parent tickets for milestones.

While I can't think of anything right now that forces milestones to be of
a unique object type, the fact of the matter is that they are unique right
now in Trac. (as seen by the fact that milestones have a due date and a
separate db table.)

Thinking of potential differences as I type:
* I think of a milestone as having only statuses of not started, in-
progress, or complete. How would we rule out the other resolve type
actions on a milestone if it was a ticket?
* I don't usually think of a milestone as having a 'type' such as
enhancement, task, or defect. Would we try to prevent this from being set
on a milestone-replacement-ticket?
* Do milestones have relative priorities? I don't think they do. The
project manager or owner simply schedules them out within the calendar.
If you don't use that kind of process on a project, then perhaps
priorities is needed?
* Do milestones have severities? I've never thought of them that way and
I'm not sure what that would buy me. If we don't want that, how would we
prevent people from picking a priority on a parent ticket and not seeing
any change in organization within the roadmap view or reports?

At this point, I think I've convinced myself that milestones actually are
a unique type of object.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 13, 2005, 10:13 AM

Post #20 of 111 (5823 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by cboos):

The short term prototype will not make the Milestone object disappear.
I'd simply like to push the ''common'' functionality of (parent) Tickets
and Milestones to a common parent class (be it the !TracObject class
itself
or some new intermediate common ancestor, e.g. !TicketGroup)

The long term idea, expressed in TracObjectModelProposal (need to refresh
that page, btw.) would be to have most of the functionality available
at the !TracObject level, and subclasses would only ''alter'' or build
upon the generic behavior
(e.g. that way one could have fields and custom fields for any objects,
and also the comments and changes history).

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 13, 2005, 11:08 AM

Post #21 of 111 (5831 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by trac [at] justin):

I agree that milestones are different. I see that now, but I am not sure
we should dismiss the replacement entirely; I think the milestone concept
is somewhat incomplete and some more thought should be put into exactly
what they are.

A good point was raised about statuses, priorities and severities for
milestones. They don't make sense. But currently milestones are just
groups of tickets with a date. No ordering is enforced (though it is
implied via the date the milestone was created). But the problems
mentioned with respect to milestones apply equally well to parent tickets.
Do subtickets have the same type as their parent? How do the priorities of
subtickets relate to the parent? They can't have relative priorities
because they all must be completed to complete the parent ticket. How can
their severities be different?

Perhaps we should not be trying to generalise subtickets at all.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 15, 2005, 10:39 AM

Post #22 of 111 (5850 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by trac [at] justin):

I like Christian's proposal to abstract common functionality into a
!TicketGroup class in his x-ref branch. I would recommend against the
!TicketGroup being descended from !TracObject because this would result in
the worst kind of multiple inheritance, a common ancestor inherited twice.
Instead, I would propose the !TicketGroup just be an abstraction of group
functionality only, and not actually a !TracObject.

{{{
TracObject TicketGroup
/ \ / |
Ticket Milestone |
\ |
ParentTicket ------
}}}

The only potential problem either of the designs is that subtickets are
not aware they are subtickets, meaning it might be more difficult to say,
show only parent tickets in a search.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Oct 20, 2005, 6:11 PM

Post #23 of 111 (5841 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Comment (by dpeterson <dpeterson [at] enthought>):

I would say that it is not necessary for subtickets to know they are
subtickets to differentiate between them and parents -- it's enough if
just the parents know they are parents. i.e. rather than saying 'hide all
subtickets' you would say 'show only parent tickets'.

Maybe not ideal, but it should work.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Nov 29, 2005, 8:08 AM

Post #24 of 111 (5833 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Changes (by anonymous):

* cc: gunnar [at] wagenknecht, mrovner [at] propel,
trac [at] justin, dpeterson [at] enthought =>
gunnar [at] wagenknecht, mrovner [at] propel,
trac [at] justin, dpeterson [at] enthought,
bruno [at] inertiacreeps

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>


noreply at edgewall

Dec 7, 2005, 4:09 PM

Post #25 of 111 (5809 views)
Permalink
Re: [The Trac Project] #886: Add support for Master tickets [In reply to]

#886: Add support for Master tickets
-------------------------------+--------------------------------------------
Reporter: dmurphy25 [at] csc | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 1.0
Component: ticket system | Version: 0.7.1
Severity: major | Resolution:
Keywords: relations |
-------------------------------+--------------------------------------------
Changes (by anonymous):

* cc: gunnar [at] wagenknecht, mrovner [at] propel,
trac [at] justin, dpeterson [at] enthought,
bruno [at] inertiacreeps => gunnar [at] wagenknecht,
mrovner [at] propel, trac [at] justin,
dpeterson [at] enthought, bruno [at] inertiacreeps,
shishz [at] hotpop

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/886>
The Trac Project <http://trac.edgewall.com/>

First page Previous page 1 2 3 4 5 Next page Last page  View All Trac tickets RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.