How to associate user with custom attribute(System) and assign work item to the associated user after save
3 answers
https://jazz.net/library/article/1257
For a general description of RTC attribute customization, see the following article.
https://jazz.net/library/article/1003
Your second requirement can be easily fulfilled with a "calculated value" script (see above article for details).
Comments
Hi Donald Nong,
Since there is no "stateless record type", you can't really associate Users with System, unless you want to create a new work item type called "System", and associate contributes to it. Since RTC and ClearQuest are a bit different, you need to change your mind set, and also the design to achieve something similar. As you cannot associate, you can translate the relationship to "depends", i.e. "users" dependent on "system".
As for the calculated value, same as your other requests, you should start with the same article.
https://jazz.net/library/article/1003
You can also find some codes developed by other users on this forum, such as this one.
https://jazz.net/forum/questions/95825/rtc-calculated-value-dependent-on-status-is-triggered-by-any-change
Donald Nong Thanks for replying but brother i'm unable to totally get your idea behind this line "As you cannot associate, you can translate the relationship to "depends", i.e. "users" dependent on "system". " can you please elaborate
If I ask you to replace "subsystems" with "users" in the dependent and parametrized HTTP Value Set sample, will you understand the idea and what you can do?
About the error in the HTTP Value Set Provider, I would suggest you open a new post.
Comments
only thing you could do is use the Contributor List data type and add/remove users from that to manage your 'association'
but U will have to manage the list in some code, and having the list of users doesn't give them any permissions or anything.. its just like another enum
sam detweiler I need to design customize work item of change request where i want to associate single or multiple user with the attribute(System) in back-end(By Admin user) hence in front-end(Normal User) when user select system from drop-down of (System) then on the basis of selected system, associated user(s) with that system will display in a read-only format below system attribute also when user save the work item then work item will also be assign to the same user who is associated with the selected system.
The suggestion which you have given will not work in above requirement.
ok, I don't understand 'attribute' 'System' then. the use case is still unclear to me
Comments
Ok, getting clearer
1. workitem can only be owned by ONE contributor. group is not a contributor. so cannot be the owner..
2. the workitem will need another field, contributor LIST which you manage (some code somewhere) to hold the list of one or more users 'assigned' to this workitem..
3. having this list does not send email or anything if the status changes,so YOU will have to write code to do this. (participant to send mail on workitem save if appropriate changes)
4. there is no UI code that will change the list of potential users when the workitem editor person selects the different enum (system) in the drop down.