Mr. Meitar Moscovitz wrote: > On Aug 25, 2008, at 2:37 PM, Noah Kantrowitz wrote: > >> While I can't question if this works for you or not, I think you are >> ignoring some major usability concerns. If person A only looks at >> their >> tickets, and you (person B) mark one of your tickets as being >> related to >> one of person A's tickets, I would imagine they would want to be >> informed of that fact. If everyone watches all ticket changes, I >> suppose >> this is a non-issue, but that would be very hard to do on a project of >> any decent size. >> >> --Noah > > It's quite possible that I've never worked on a large-enough project > for this to be an issue. It's also possible that this is another > example of where the problem is actually a people issue, not a > software issue. > > That is, if I am a developer and I wish to mark my ticket as being > related to another developer's tickets, whether or not I notify that > developer of this fact should be my choice and I may choose to send > that developer a message to that effect. In essence, it's still *my* > ticket, isn't it? And the keywords I add to it are, at least under > this convention, for my own benefit anyway.
It isn't just about your convenience, if I was that other developer I would certainly want to be notified if you think you need one of my tickets fixed/implemented since that would possibly change my priorities. > I'm not saying that this feature wouldn't "be nice to have," because > sure, that'd be a nice option. As you mentioned, however, Trac > currently doesn't do this, which is obviously only a problem for those > people who want that feature *right now* (hence the existence of > MasterTicketsPlugin, I assume). > Um, Trac does support it, you just install the plugin. If such a plugin didn't already exist I could see the argument for doing this with keywords, but the hard part has already been done. --Noah
signature.asc
Description: OpenPGP digital signature
