Change Requests

Propose changes to approved or baselined items, have the project's approvers review them, then apply them in one step with a record of who approved what.

Where to find it

• In the navigation rail: Plan & Deliver → Change Requests.
• The log is at changes; ?cr=<id> opens one request.

Main actions

• New Change Request (or Propose Change… on an item under configuration control): a title and the reason for the change.
• Affected Items: the items the change touches. Items traced to them are suggested; + adds one.
• Add Change ▾ stages a change without changing the model: Change an Item…, New Item…, Delete an Item…, Add a Relationship…, Remove a Relationship…. Description changes show as a word diff.
• Submit for Review sends it to the approvers. They click Approve… or Reject… (a rejection needs a reason). On the hosted service each decision asks for your password and is tied to the exact changes; editing the changes later asks for new approvals.
• Apply Changes (editors and owners, once approved) applies every staged change as one undo step; each item's History shows via CR-n.
• Settings: project owners turn on Changes to approved and baselined items require a change request, and set the approvals required (1 to 3), who approves (owners, owners and editors, or a change board) and whether authors may approve their own requests.
• Export ▾ saves the change request log as Excel or Word.

Tips

• Configuration control covers approved requirements and items in the latest project baseline. Comments, reviews and requirement approvals stay open.
• An approval record is not a legally regulated electronic signature.

Related

Baselines & Versions · RVTM · Review Packages · SE Process Guides