Design question: LinkTypes vs. Attributes?
![]() We were recommended to use LinkTypes for custom connections between work items (we basically rebuilt everything in RTC because it just didn't work at all with our processes - and since we were told that we could configure RTC basically the way we wanted - we did).
|
One answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jan 11 '17, 4:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Jan 11 '17, 6:01 a.m. In general, RTC is customizable. Like with every tool, there are limitations in what can be done and it is a good advice to stay within the limitations. Some limitations can be overcome if throwing enough custom coding and computational power at them, some can't. So it is a good idea to understand the limitations. Here material I presented last year about what I think the limits are: https://rsjazz.wordpress.com/2016/07/15/rtc-process-customization-what-you-can-and-cannot-do/
Comments I do not need individual attributes from one work item in the other - I just need a link to the other work item. So I'm guessing I can ignore the complete first part of your post as far as I understand. Besides - that wouldn't be something to decide either way (link types or work item lists) because it doesn't work either way.
Besides of course it would be interesting how those two possibilities compare in other ways as well.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you can detect added and deleted work item links using custom advisors as far as I can tell. You have to look at the links in the old state and compare them to the links in the new state. Note, i did a prototype but that was for a link type that DOES NOT TRIGGER THE ADVISOR (the aforementioned CLM link types such as tracks). So I gave up on it. No, you can not use work item attribute customization/JavaScript.
Excellent responses and brilliant slides about what can and cannot be done, @rschoon
This question is another example of the importance of having someone with the knowledge of the tool advising along the way.
For starter, I would strongly discourage creating custom LinkTypes.
RTC can be quite powerful, capable of supporting complex custom use cases, if implemented properly and accepting small sacrifices.
I see here at jazz.net more and more questions with requirements which are questionable. I wonder if sometimes it's a problem of expectations and lack of in-depth knowledge of the tool, which is key when adapting the tool to customers' needs.
What sometimes looks like a big limitation in the tool can be easily overcome using a different approach and being a bit flexible.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There are several problems leading to questionable questions 8)).
1
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Don't get me wrong, there is a lot of information on this particular question, even if I misunderstood it or did not get the main topics the first time around. And as Miguel mentions, this is complex and even very experienced users sometimes can only answer "I think this would be a way to solve the need".
I'm sure you can imagine that I cannot disclose all the company information that lead to the decision to implement things the way we are doing right now.
I think your expectation is way off. We are not talking about standard tool usage and configuration here. This is basically custom development and unless you have a prototype that works, all bets are off. I consider myself an expert in these areas, but I would not dare to say I could do stuff unless I prototype it. Luckily I have done a lot of prototypes
showing 5 of 8
show 3 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.