#7221 NORM -: trac improvement: replace multi-value 'blocking' and 'blocked by' fields with relationship

[Zarro Boogs per Child]

#7221: trac improvement: replace multi-value 'blocking' and 'blocked by' fields
with relationship
--------------------------+-------------------------------------------------
  Reporter:  ggoebel      |       Owner:  coderanger
      Type:  enhancement  |      Status:  reopened  
  Priority:  normal       |   Milestone:            
 Component:  trac         |     Version:            
Resolution:               |    Keywords:            
  Verified:  0            |    Blocking:  7221      
 Blockedby:  7221         |  
--------------------------+-------------------------------------------------
Changes (by ggoebel):

  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 {{{
 > 2. Try entering an invalid entry in either field, you will find it is
 removed
 >    for you automatically.
 }}}

 Ok. I just did. Ticket #7221 now blocks itself. Does that qualify as an
 invalid entry?

 I haven't tested how it does on circular dependencies between separate
 tickets... Perhaps I'll find some mention of that on trac-hacks.org.


 {{{
 Next time please at least investigate a little before filing a ticket.
 }}}

 I hope you'll excuse me, if I don't investigate trac's short comings by
 messing around with a live trac database. If #7222 is completed, then I'll
 have a copy of the trac database to mess around with.

 Thanks for the reference to trac-hacks.org. I'll check it out. I've worked
 with several such systems. Each with its own set of ideosyncracies. I'm
 not familiar with trac from the perspective of admin or customization...

-- 
Ticket URL: <http://dev.laptop.org/ticket/7221#comment:4>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system