Re: Manging forward and reverse links
"John P. Rouillard" <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
In message <[email protected]>, Bernhard Reiter writes: >Am Dienstag, 26. Februar 2013, 20:35:12 schrieb John P. Rouillard: >> If you are working with an issue, it is easy to add/remove links from >> the issue to other issues by simply editing the link entry. >> >> However what I want to do is the reverse: edit links from other issues >> that point to my current issue. I want to do it while changing my >> current issue and not have to load the other issues. > >Fair enough. :) >But why not leave out the "(" and ")" characters entirely? Ah ok, I didn't explain myself well enough. I want a single edit box that can be used for both: adding/removing links from this issue to another and adding/removing links from another issue that points to this one so an entry for the depends property would look like: 1 3 5 (9) (22) (10) which would be interpreted as: this issue depends on issues: 1, 3 and 5 issues 9, 22 and 10 depend on this issue so there has to be some decoration to show that the (9) (22) and (10) indicate the reverse links. Does that explain what is happening with the ()'s? As far as I know there is no way to get data from the front ends (cgi, email) to the detectors except by declaring the data as the value of a property. I don't want to create a property "backdepends" that contains 9, 10, 22 for three reasons: 1) The propery (and it's data) is redundant. This information is already stored in the depends property of the other issue and can be retrieved using a filter. 2) Every property ends us being displayed in the order and sort pulldown on the index displays. This just clutters things up (I have at least three of these foward/reverse properties in the sysadmin tracker) and AFAIK there is no way to hide a property from the pulldowns while allowing the user to edit it. 3) I want to eliminate another edit box for the property to keep the interface cleaner. This is a fake property that exists only to provide functionality in the editing interface and will be empty by default (so I don't end up storing the same data in two places). Does this explain things better? -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev