CR Manager is an Windows application that manages Change Requests. A Change Request (CR) is a description of a logical change that will be made in a version of some software. When you check in modified files you relate the changes in the file to one or several CRs. In its final form, a CR describes a change and lists all the file versions related to this change.
CR Manager provides a main window, showing a list of the CRs in the selected system configuration.
A session window shows CRs from a particular system configuration. All or filtered CRs are shown. Each CR displays CR name, state, responsible, date, title, and a possible baseline name. You can change the order of the columns by drag and drop. You can sort the list according to a column - just click on it. You can display one or several CRs, if you select them and choose Display function, or if you double click on a CR.
The right mouse button pop-ups a menu that corresponds to the CR menu.
CRs from different SDE system configurations can be presented in separate windows.
CR Manager includes a number of functions for CR manipulation. Here follows a brief presentation of some of them:
Open a CR library
A CR directory includes CRs. CRs are actually versioned files saved in the RCS library under the CR directory. The best way to open a CR session is to select a working session from the SDE projects you are a member of.
You can also invoke a CR Manager showing the CR directory from an open session in VersionWorks.
Another way of finding a CR directory is to select a wanted project and a system configuration in the project, or directly a system configuration. In that case CR Manager expects to find a file named confdef.def that points to the CR directory. This file is generated by WinSDE and placed on the top of the configuration.
Finally, you can find your CR directory by browsing through a directory structure. Note
that the CR
directory is placed under the master configuration in an SDE system.
Selecting View to CRs
You can show all CRs or just those that fulfill some criteria. You can show, for example, only CRs that have Exp and Init state, i.e. not completed CRs.
Creating a CR
You normally create a CR when you want to register a change that you, or someone else, will introduce in the system.
When you create a CR it gets the Init state. It includes name, title, state and the description. Later it also includes a list of registered file versions. You can classify the CR according to priority (High, Medium, Low) and Reason (Improvement, Error, New Functions) and relate the CR to a specific function. If you want to inform someone else about the CR, you can directly send a mail with the contents of the CR.
You can change any CR parameter or its description. If you select to edit a CR, you get a very similar window as when you created the CR. You can also add or remove a file to/from the CR, but from another window:
Changing CR state
You can modify CR state, according to in which phase you are with the change implementation. When a CR is created it automatically gets Init state. When a CR is changed the first time, it gets Exp status. Later, when you terminate a CR, it gets the Term state. The CRs that were included into a product release should get the state Rel. If you do not need a CR, you can put the Obsolete state, or just delete it.
Later, when you have completed and tested all the changes related to CR, you terminate it. When you terminate a CR you can put a short message, for example how many workdays the change has required.
It is not possible to modify a terminated CR, except to define the Rel state. If you really want to change a terminated CR, you must first cancel the termination, and the CR will get again the state Exp.
You can always check the contents of CR compared with the changed files in the system configuration. You can check all CRs against all files, or you can look at some particular files, directories or CRs.
The check CR functions gives you information if some file were changed without being registered in CRs. You can also see if a changed file is related to one or several CRs.
The Check CRs Window lists the latest versions of files and which versions are registered in which CRs. If a registration is not correct a sign different from "=" is shown in the Relation column.
WinSDE provides a connection between CRs and PMRs. PMR (Product Maintenance Report) is a facility for registering and following errors. In the Options function you can disable usage of PMR if you are not using it - the PMR menu will disappear.
The PMR system manages changes related to existing products and problems found in them. It makes it possible to keep track of the life cycle of an error, from its reporting trough the problem analysis, changes, to the integration in different products, etc. While CRs describe the changes made in a particular SDE structure, the PMR system describes problems in a larger aspect.
Using CR Manager you can:
You Create a new CR that is generated from the Change activity in PMR.
When you include CRs in a new product release, you can document this in the PMR system by creating the Release activity. You can do it manually in the PMR system, or you can generate these actions for all PMR being processed as CRs.
WinSDE CR Manager - Top