It's all about the answers!

Ask a question

Can I leverage a dependent enumeration to filter values from a contributor list?


Andrew Trobec (49712137138) | asked Oct 25 '12, 4:25 a.m.
Good Morning,

I am using RTC 3.0.1.1.

I have found how to create a dependent enumeration for value sets and I've noticed that it automatically recognises the enumerations defined within in the process template.  What I'd like to know is whether I can somehow integrate contributor lists (based on a role based user list) into this so that when a specific team enumeration value is selected in a work item, the list of people that belong to the corresponding role will be displayed.

Is this possible?

Thank you and best regards,

Andrew

Comments
Millard Ellingsworth commented Nov 07 '12, 8:46 p.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER

Trying to wrap my head around your question. Can you elaborate with an example of what you are trying to do? For example, what types of attributes are you using and what presentations are being used for them? And if you could explain the broader goal, perhaps there's another way to do it. 


Andrew Trobec commented Nov 08 '12, 2:27 a.m.

Hello Millard,


Thank you for your interest!

To elaborate, I have seen how I can configure a "parent" drop down list to determine the values available to a "child" drop down list and was wondering whether this was possible for contributor fields.

If I configure a contributor field to be populated by a specific role (Issue Managers, as an example), can I use it as a "parent" then to determine values in a "child" drop down list?

I hope this explanation makes sense!

Thank you and best regards,

Andrew

Accepted answer


permanent link
Millard Ellingsworth (2.5k12431) | answered Nov 08 '12, 11:46 a.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER

It sounds like you want something similar to a role-based enumeration (where you can say what value to default to based on the logged in user's role). For example, if the logged in user is a Product Owner, then the default value for Priority would be set to High.

But you actually want to take that a step further (if I understand) so that you can set the values in the dependent list based on the name/id of the individual contributor. So if your list of issue managers contains Bob, Ted and Alice, if someone chooses "Bob" in the person list, the list of Regions (for example), would only include areas in the south east (Bob's region) and if they chose Alice, the list of Regions would only include areas in the north west.

Since the list of Issue Managers can change (as people move, leave, get promoted), the configuration would not be quite as clean as a normal dependent enumeration since the driving list could be very dynamic (unlike the typical Operating System -> Browser example).

If you were using RTC 4.x (or if that's possible), I'd suggest looking at this article: https://jazz.net/wiki/bin/view/Main/AttributeCustomization#Dependent_Enumerations_4_0 that talks about improvements in support for Value Providers that seems to match pretty closely what you want.

If moving up to 4.x isn't possible at this time, you might consider using a Custom Filtered Value Set Provider as discussed here: https://jazz.net/wiki/bin/view/Main/DataSourceValueSetProviders There may also be an interesting way to use an HTTP Filtered Value Set Provider -- delivering the values this way may make it easier to maintain the relationships since the persons doing that would not need to have permissions to make process specification updates.

Andrew Trobec selected this answer as the correct answer

Comments
Andrew Trobec commented Nov 09 '12, 2:07 a.m.

Hello Millard,


I also considered the fact that the lists were dynamic.  I have taken a look at the value sets and think this would be the best option since I have no experience whatsoever with developing extensions.

I appreciate the feedback.

Best regards,

Andrew

Your answer


Register or to post your answer.