background image
<< Examine the enhancement requests | What Will Happen in the Next Iteration? >>
Modify an enhancement request
<< Examine the enhancement requests | What Will Happen in the Next Iteration? >>
Chapter 11 - Planning the Next Iteration
Exercise: Modify an enhancement request.
Go back to the previous enhancement request you looked at (CLSIC00000036,
Need to notify customer via email when order ships)
. Since we know that a similar
request has already been assigned, we'll close this request as a duplicate.
On the Main tab, click Actions, then click Duplicate.
In the Mark as Duplicate dialog box, enter
, then click Find to make
sure you have identified the correct record to which CLSIC00000036 is a duplicate.
Click OK to return to the defect you are modifying.
On tabs where you must fill in a box, a red square appears.
Go to the Analysis tab.
The Owner box is marked red, indicating that a value is mandatory. Recall that
you logged in as pat and you are determining the resolution for this entry. So
from the Owner list, click pat.
Go to the Resolution tab. Notice that TestManager has already filled in boxes
related to the duplicate of this record.
Click Apply. You may need to click Run Query from the toolbar to refresh the query
You will see that enhancement request CLSIC00000036 is now in the Duplicate
Other Planning Activities
During an iteration, you usually work both to correct defects and to implement
enhancements. As part of planning, you might also use ClearQuest or RequisitePro to
identify the work to do in the next iteration.
During iteration planning, you can produce a Rational SoDA report showing the
defects and enhancements planned for the next iteration. You can also use
ProjectConsole to automatically generate charts and gauges with metrics gathered
from tools like RequisitePro and ClearQuest. This report helps you analyze the status
of your next project and share it with members of your team.