Tracks Links and Cross-Project Planning
Hi,
we are currently running into an issue with cross-project planning and the "Tracks" link.
By using this link type within our plans our planning works as expected, but we're facing an issue when it comes to querying, because the "Tracks" link doesn't allow to query for an attribute on the tracked work item.
Our idea to solve the querying issue is to create a "Related" link additionally between the tracked work items.
Could this work or exists another more elegant method to solve this problem.
Thanks for your attention.
Regards
Matthias
we are currently running into an issue with cross-project planning and the "Tracks" link.
By using this link type within our plans our planning works as expected, but we're facing an issue when it comes to querying, because the "Tracks" link doesn't allow to query for an attribute on the tracked work item.
Our idea to solve the querying issue is to create a "Related" link additionally between the tracked work items.
Could this work or exists another more elegant method to solve this problem.
Thanks for your attention.
Regards
Matthias
One answer
Matthias,
in addition to being connected by track links I would assume the link targets could also reside in another project area, hence regular querying would not be the way to go.
I would have a look at how JRS is evolving ...that is the place for cross project querying and possibly for the track links.attribute
As for current use cases, if you can post the exact query that should be done we can decide between ourselves whether e.g. a BIRT approach or possibly a custom Eclipse plugin would be required in the short term.
in addition to being connected by track links I would assume the link targets could also reside in another project area, hence regular querying would not be the way to go.
I would have a look at how JRS is evolving ...that is the place for cross project querying and possibly for the track links.attribute
As for current use cases, if you can post the exact query that should be done we can decide between ourselves whether e.g. a BIRT approach or possibly a custom Eclipse plugin would be required in the short term.