Purpose of the superceder property.

Pardon my ignorance if this is naive question, but is there
anything in the
implementation of the superseder property, or its intended
usage in a generic
tracker that mitigates using it simply as a "related
issues" property?

That is, issues linked via this property simply meaning
"these are issues
related to this one" rather than "these issues
supersede this one".

Cheers, Bruce.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Roundup-users mailing list
Roundup-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/roundup-u
sers

On Mon, 2 Apr 2007, Bruce Tulloch wrote:
> Pardon my ignorance if this is naive question, but is
there anything in the
> implementation of the superseder property, or its
intended usage in a
> generic tracker that mitigates using it simply as a
"related issues"
> property?
>
> That is, issues linked via this property simply meaning
"these are issues
> related to this one" rather than "these
issues supersede this one".

There is no meaning attached to that property other than
what you give it.


    Richard

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Roundup-users mailing list
Roundup-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/roundup-u
sers

Bruce Tulloch <brucecausal.com> writes:

> Pardon my ignorance if this is naive question, but is
there anything
> in the implementation of the superseder property, or
its intended
> usage in a generic tracker that mitigates using it
simply as a
> "related issues" property?
>
> That is, issues linked via this property simply meaning
"these are
> issues related to this one" rather than
"these issues supersede this
> one".

I'd want "related" to be more tightly defined.
Related how? Are they
duplicates? Should they be merged into this one, treated as
the same
issue? How do I (a user) determine that issue 23 has this
type of
relationship with issue 42, but not with issue 69?

-- 
           "Instead of a trap door, what about a trap
window? The guy |
  `      looks out it, and if he leans too far, he falls
out. Wait. I |
_o__)             guess that's like a regular window." 
-- Jack Handey |
Ben Finney


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Roundup-users mailing list
Roundup-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/roundup-u
sers

Richard Jones wrote:
>> That is, issues linked via this property simply
meaning "these are issues
>> related to this one" rather than "these
issues supersede this one".
>
> There is no meaning attached to that property other
than what you give it.

Good, thanks. I thought so.

Ben Finney wrote:
> I'd want "related" to be more tightly
defined. Related how? Are they
> duplicates? Should they be merged into this one,
treated as the same
> issue? How do I (a user) determine that issue 23 has
this type of
> relationship with issue 42, but not with issue 69?

I guess like Richard says, it's up to you (or me .

Cheers, Bruce.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Roundup-users mailing list
Roundup-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/roundup-u
sers

Ben Finney wrote:
> I'd want "related" to be more tightly
defined. Related how? Are they
> duplicates? Should they be merged into this one,
treated as the same
> issue? How do I (a user) determine that issue 23 has
this type of
> relationship with issue 42, but not with issue 69?

In my installation, it is just a mere cross-reference; I
made this clear 
in my local translation. For merging issues, see

   http://www.mechanicalcat.net/tech/roundup/wiki/MergeIs
sues

To make it more obvious, it is a good idea to iterate the
superseded 
issues and show them in the issue.item.html in their own row
(below the 
input field), e.g. linking them and displaying title and
status.

-- 
Tobias


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Roundup-users mailing list
Roundup-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/roundup-u
sers

Tobias Herp wrote:
> To make it more obvious, it is a good idea to iterate
the superseded 
> issues and show them in the issue.item.html in their
own row (below the 
> input field), e.g. linking them and displaying title
and status.

My code:

<tr tal:condition="context/superseder">
   <td></td>
   <td colspan=5>
    <div tal:repeat="sup
context/superseder"><a
      tal:attributes="href
string:issue${sup/id}"><b
        tal:content="sup/id">3</b>:
      <tal
replace="sup/title">title of cross-referenced
issue</tal>
      (<tal
content=sup/status
i18n:translate="">unread</tal>)

  </a></div></td>
</tr>

-- 
Tobias



------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Roundup-users mailing list
Roundup-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/roundup-u
sers