Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Multiple Owned By Attribute on a Workitem

Hi,

I have a flow that I need to implement on RTC. We need tree people to set  their own Due Date about some jobs and set other Attributes on the same workitem. They are actually not the owner of the workitem but they need to contribute to workitem with their effort.

My draft workitem looks like the one below. When FT responsible or ST Responsible is selected, I want them to be warned with an e-mail. It seems to be not possible with the current RTC configuration but I might be missing some points.

.

Do I need to write a post condition or is there a configuration that I missed?

0 votes



4 answers

Permanent link
 Hello,
as per Jim's comment,
contains details about the limitations of the Javascript API.

On my side, I would implement a save participant - see Ralph's blog and examples on this http://rsjazz.wordpress.com/

Implement this participant so that, at save time, we subscribe the FT responsible and/or ST Responsible if set.

Hope it helps.
Eric.

2 votes


Permanent link
On the surface, the easiest way to do this would be to add the Responsible people in the new attributes to the list of subscribers using a JavaScript provider. As subscribers, they'd get an email every time the WI is modified.
 The way to do this would be to create a JavaScript based value provider, pulling the contributor (user) information from the Responsible attributes and adding them to the Subscriber list. 

Unfortunately, the JavaScript API in RTC is very simple and mostly just works for strings. It won't let you pull a contributor an one attribute and add it to the Subscriber attribute.

I recommend either one of these simpler methods:

1. Add the Responsible people to the Subscribers manually. You could make this slightly easier by putting the attribute presentations for the Responsible attributes on the Links tab. Then you can add them as subscribers on the same tab.

2. Create child work items for each test type using Work Item Templates. Create a WI template that has your main WI as the parent, and 3 testing WIs as children. When you create a new WI, use that template instead of a specific WI. Then the owner of the Functional Test child WI will get an email when the WI is modified. This has the benefit of allowing you to track the status of each test separately, though you might need to create a new WI type with a small testing workflow.

1 vote

Comments

JavaScript can't access the subscriptions. If you want to automate this, you would need to create a participant as Eric suggests.

On the other hand, why flooding them with e-mail? They can have a dashboard that shows they are an additional owner - if you use a contributor list attribute. Otherwise, as suggested it would be possible to create child work items that track the individual contribution. This is much cleaner. A participant could even create the child work items based on the "Additional owner" contributor list.

1 vote


Permanent link
If multiple people are contributing to a work item, you can give each person an "Approval", which allows them to specify when they have performed their part of the task.   If you want to track more information about a contributor than whether or not they are done, then it is best to create a child work item for that contributor.

1 vote


Permanent link
In my opinion creating duplicate work item is cleaner way to do this.By doing this you can set your values as per your requirement

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 6,121
× 369

Question asked: May 21 '13, 2:12 p.m.

Question was seen: 6,734 times

Last updated: Apr 09 '14, 2:00 a.m.

Confirmation Cancel Confirm