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

RTC Work Item customization

Hi All!

I have two work item customization related questions.

1. Is it possible to configure work items in a way that specific attributes are only accessible for people having a certain role? I know that we can customize work items, but I haven't found any option for this kind of customization.

2. I would like to use Team Concert to assign work items to developers but I want that these work items can be divided into other (child) work items by the developers. However, the parent work item defines the overall working hours can be spent on the work (no matter how many child work items are created by the developer). So the working hour definition is a constraint in the parent work item. Therefore, the total working hours spent on the child work items must be less or equal with the number defined in the parent work item.

For example:
The parent work item created by the project lead is: Implement Web UI - man days: 10
The child work items created by the developer:
- Setting up the development environment and other required infrastructure: 1day
- Implementing the web services: 3 days
- Creating JSP pages: 5 days
- Testing 1 day

As you can see, the developer has 10 days to divide into other work items. These 10 days come from the parent work item which was created by the project lead and it is a constraint for the developer. Is it possible to do this in RTC? (Without using Rational Project Conductor.)

I'm working with RTC Standard Edition.

0 votes



One answer

Permanent link
Hi Akos,


Hi All!

I have two work item customization related questions.

1. Is it possible to configure work items in a way that specific attributes are only accessible for people having a certain role? I know that we can customize work items, but I haven't found any option for this kind of customization.


This is not possible with RTC 2.x today as far as I know. I have seen workitems in the plan for 3.0 for it.


2. I would like to use Team Concert to assign work items to developers but I want that these work items can be divided into other (child) work items by the developers. However, the parent work item defines the overall working hours can be spent on the work (no matter how many child work items are created by the developer). So the working hour definition is a constraint in the parent work item. Therefore, the total working hours spent on the child work items must be less or equal with the number defined in the parent work item.

For example:
The parent work item created by the project lead is: Implement Web UI - man days: 10
The child work items created by the developer:
- Setting up the development environment and other required infrastructure: 1day
- Implementing the web services: 3 days
- Creating JSP pages: 5 days
- Testing 1 day

As you can see, the developer has 10 days to divide into other work items. These 10 days come from the parent work item which was created by the project lead and it is a constraint for the developer. Is it possible to do this in RTC? (Without using Rational Project Conductor.)

I'm working with RTC Standard Edition.


This is possible at least manually today has a lot of benefits and is a typical way of working I guess. You would use Top Level work items such as stories as the parent. Developers would create execution items such as tasks. Agile planning sums up the numbers for you. See the relevant sections in http://jazz.net/projects/rational-team-concert/learnmore/.

Ralph

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

Question asked: May 03 '10, 8:43 a.m.

Question was seen: 4,691 times

Last updated: May 03 '10, 8:43 a.m.

Confirmation Cancel Confirm