Ticket graphing bug?

Hi all,

I am trying to understand ticket graphing behavior. Example ticket relations:

A -> RefersTo -> B -> DependsOn -> C

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to “RefersTo” then all 3 tickets a graphed.

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to ANY other link type, only A and B are graphed.

What is meant by “Main type of links” and why does it affect graphing like this?

My goal is to graph all tickets related to the main ticket, now matter
what link type or an what link depth.

Thanks!

-Todd

Does anyone have some insight into this? Any help is appreciated.On Tue, Mar 1, 2011 at 10:12 PM, Todd Chapman todd@chaka.net wrote:

Hi all,

I am trying to understand ticket graphing behavior. Example ticket relations:

A -> RefersTo -> B -> DependsOn -> C

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to “RefersTo” then all 3 tickets a graphed.

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to ANY other link type, only A and B are graphed.

What is meant by “Main type of links” and why does it affect graphing like this?

My goal is to graph all tickets related to the main ticket, now matter
what link type or an what link depth.

Thanks!

-Todd

Todd,

My experience with this is to set the 'Main Type" of links at the first
level to “Members” with the “Show as Well” set for the other
types;
“Members of”, “DependsOn” & “Refers To” only and set the levels
for however
many level I need. Then I leave the lower levels alone. If I want lower
level info to display in an info box for a ticket, then I check that info
at the lower levels. I find that WAAAYYY TOOO Busy. All I want is the ticket
numbers and their relationships to all levels (in other words … arrows
only) and this seems to work for me. I have found that the less I check at
any lower level, the better it looks.

Hope this helps.

Kenn
LBNLOn Thu, Mar 3, 2011 at 8:15 AM, Todd Chapman todd@chaka.net wrote:

Does anyone have some insight into this? Any help is appreciated.

On Tue, Mar 1, 2011 at 10:12 PM, Todd Chapman todd@chaka.net wrote:

Hi all,

I am trying to understand ticket graphing behavior. Example ticket
relations:

A -> RefersTo -> B -> DependsOn -> C

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to “RefersTo” then all 3 tickets a graphed.

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to ANY other link type, only A and B are graphed.

What is meant by “Main type of links” and why does it affect graphing
like this?

My goal is to graph all tickets related to the main ticket, now matter
what link type or an what link depth.

Thanks!

-Todd

Hi,

Main type of links is type that is used to build main graph, only such
links are followed recursively. Once main graph is built by following
links of the main type then graph expanded with all additional types
for every node in the main graph.

Suggest clear wording if you have any.On Thu, Mar 3, 2011 at 7:15 PM, Todd Chapman todd@chaka.net wrote:

Does anyone have some insight into this? Any help is appreciated.

On Tue, Mar 1, 2011 at 10:12 PM, Todd Chapman todd@chaka.net wrote:

Hi all,

I am trying to understand ticket graphing behavior. Example ticket relations:

A -> RefersTo -> B -> DependsOn -> C

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to “RefersTo” then all 3 tickets a graphed.

If you graph A with “Show as well” selecting ALL link types and “Main
type of links” set to ANY other link type, only A and B are graphed.

What is meant by “Main type of links” and why does it affect graphing like this?

My goal is to graph all tickets related to the main ticket, now matter
what link type or an what link depth.

Thanks!

-Todd

Best regards, Ruslan.