The Stream Issues and Stream Diff (Issues) tabs are essentially similar. A table in the Issues pane (upper) displays the
issue records that are in a particular stream. The Change Package Contents pane (lower) displays the entries in a selected issue record's
change package.
Strictly speaking, the only objects that are "in" a stream are versions. It makes sense to describe a set of versions as being "in" a stream. And so, it makes sense to describe the set of versions in a change package as being "in" a stream. From there, we make the leap to describing the AccuWork issue record containing the change package as being "in" a stream.
To open a Stream Issues tab, showing the contents of a stream in terms of change packages: choose Show Active Issues from the context menu of any stream, or snapshot, or workspace in the StreamBrowser.
Note: If the StreamBrowser is displaying
development activity by issue record, you can click the

icon under the stream itself to open a subwindow containing the same data as a separate Stream Issues tab.

2.
|
Choose the Show Diff by Issues command from the selection's context menu, or click the  button on the StreamBrowser's toolbar.
|
Checkboxes at the bottom of the Issues pane control which issues are displayed. The Show Active,
Include Incomplete Issues, and
Include Hierarchy checkboxes appear only when you're displaying a single stream's change packages. (When comparing streams, AccuRev always proceeds as if these checkboxes are cleared.) The
Bidirectional checkbox appears only when you're comparing two streams.
(available only if Show Active is checked) If checked, also includes issues that are in the streams below the selected stream.
Stream Issues tab (enabled only if
Show Active is set and
Show Incomplete is cleared): promotes each currently-active head version in the issue's change package to the parent stream. That is, if a version listed in the Version column is currently active in the stream on which you invoked the
Show Issues command, that version is promoted to the parent stream.
Invoking the Promote command on issue #7 causes some or all these versions to be promoted. The versions promoted are the ones that are currently in the workspace's default group:
Stream Diff (Issues) tab (works only for issues in the source stream, not for issues in the destination stream): promotes each currently-active head version in the issue's change package from the source stream to the destination stream. If there is an
overlap between the two streams for any element, the
promote operation fails with a "merge required" error box.
(enabled only if Show Active is set and
Show Incomplete is cleared) Opens a Change Palette tab, containing each head version in the issue's change package.
(Formerly named Revert by Change Package.) Removes the changes in the selected issue's change package from the stream. A dialog appears offering you two options for performing this operation:

•
|
Use a workspace to peform revert — Choose this option if you wish to test the results of the revert before promoting them back into the stream. You must choose a workspace to which you have access to perform the revert. (All workspace appear in the selection list. If you select a workspace to which you do not have access, AccuRev will display an error). The revert operation typically involves one or more reverse patch operations on file elements' contents, performed with the Merge tool.
|
Important: If no valid workspaces exist, this dialog is bypassed and you are prompted whether or not to proceed without a workspace (see below). A "valid" workspace is one of your own workspaces which has local (or accessible mounted) storage on the machine that the
revert is being performed from. If none of your workspaces are attached to the stream the issue is being
reverted from, or for some reason are not accessible from the machine that the client is running on, you can still proceed with the revert, keeping the new file versions directly in the stream. However, AccuRev warns you that this is what happening if you choose to proceed with the
revert operation.
Note: This feature is not intended to be used
within a workspace; it is meant to be executed within a stream, but with the aid of a workspace to perform any necessary
Merge operations. If you try to execute this operation directly within a workspace, you will get an error message: "You need to have at least one workspace associated with stream..." Try the following workaround:
3.
|
Invoke the Revert Change Package Using Workspace command on that issue in the new stream.
|
•
|
Continue revert operation without using a workspace — Similar to Use a workspace to peform revert, except that the results are placed directly in the stream, without the requirement of a workspace. This means that the results of the revert will be immediately propagated downstream in the hierarchy.
|
Important: If no workspaces to which you have access exist, the dialog described above is bypassed and you are simply prompted whether or not to proceed without a workspace.
Note: Continue revert operation without using a workspace saves the step of merging and testing the revert in a workspace and then promoting the changes, but at the risk of propagating the changes as soon as the revert has been completed. This feature should not be used casually by developers, as you could easily propagate complex, untested changes to other users. This feature is useful for reverting relatively simple changes, or for backing out a change in an isolated build stream. AccuRev recommends that you build and test these changes in an updated workspace to verify the results, before promoting or cross-promoting the changes to other users.
Opens an Issue Dependencies tab, displaying the change package dependencies of the selected issue record(s).
Select any change package entry and invoke any of the commands described below. In most cases, the operation is performed on the entry's head version (
Version column). You can invoke the
Remove and
Send to Issue commands on a selection consisting of two or more change package entries.
Windows: Run the appropriate command on the file, according to its file type. (The Windows file-typing system — "file associations" — does not provide for assigning a file type if the filename has no suffix.)
UNIX: Open a text editor on the file.
Open a History Browser tab, containing the transactions involving the selected file or directory.
Open a Version Browser tab, showing all the versions of the selected file or directory, and their interrelationships (ancestry).
The default query is executed, and the results are displayed in a
dialog. You are prompted to choose one or more of the issue records selected by the query. You can also create a new issue record, whose number will be entered in the dialog.