The Stream Issues and Stream Diff (Issues) Tabs
The Stream Issues and Stream Diff (Issues) tabs are essentially similar. A table in the Issues pane (upper) displays the issue records A data record, consisting of values of data fields, stored in a Dispatch issue database. that are in a particular stream. The Change Package Contents pane (lower) displays the entries in a selected issue record's change package A set of entries, each in the form of a basis-version/head-version pair, recorded on the Changes tab of an issue record. The change package records the changes to one or more elements, made to implement the feature or bugfix described in that issue record. Each entry in the change package describes changes to one element: the changes between the basis version and the head version. See patch..
Notes (click to open):
Terminology: issues "in" a stream
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 Issues from the context menu of any stream, or snapshot, or workspace in the Stream Browser. [note]
If the Stream Browser 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.
To open a Stream Diff (Issues) tab, showing the difference between two streams in terms of change packages:
In the Stream Browser, select a stream, snapshot, or workspace.
Choose the Show Diff by Issues command from the selection's context menu, or click the button on the Stream Browser's toolbar.
The mouse pointer changes to . Left-click another stream, snapshot, or workspace.
The Stream Issues tab includes two panes, each with its own toolbar:
The Issues pane displays selected fields from the issue records whose change packages are "in the stream" -- partially or completely. When you're comparing the contents of two streams, this pane displays the issues whose change packages are in one stream, but not the other.
The Change Package Contents pane displays the entries in the change package A set of entries, each in the form of a basis-version/head-version pair, recorded on the Changes tab of an issue record. The change package records the changes to one or more elements, made to implement the feature or bugfix described in that issue record. Each entry in the change package describes changes to one element: the changes between the basis version and the head version. See patch. of the currently selected issue record. This is identical to the Changes tab in an issue record's edit form.
You can control which issues are displayed, and you can invoke commands on one or more issues' change packages.
Checkboxes at the bottom of the Issues pane control which issues are displayed. The Show Incomplete, Show Active, 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.
Show Incomplete
If cleared, the listing includes only change packages that are completely in the stream.
If checked, the listing includes only change packages that are partially in the stream. The Status column, along with background shading, indicates which change package entries are "in" the stream and which are not in ("missing" from) the stream.
Note that the Show Incomplete checkbox is a toggle rather than a filter: setting and clearing the checkbox displays two non-overlapping collections of change packages.
Show Active
If checked, a change package is included only if one or more of its versions was promoted to the stream, but has not yet been promoted from the stream to its parent. [note ] This helps you to concentrate on current programming efforts, rather than those that were completed long ago.
This filter has no effect when you're viewing the contents of a snapshot, since no versions can be active in a snapshot.
Include Hierarchy
(available only if Show Active is checked) If checked, also includes change packages that are in the streams below the selected stream.
Bidirectional
(Stream Diff only) If cleared, the Issues pane displays the issue records in the first stream ("source"), but not in the second stream ("destination").
If checked, the listing also displays the issues that are in the second stream, but not in the first stream. Color-shading helps you to distinguish the two sets of change packages.
Select one or more issues to invoke commands on the issues, or on their change packages. These commands are available through context menus and in the toolbar of the issues pane.
Open Issue
Open an edit form on the selected issue, and display the Changes tab.
Promote
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.
The following illustration shows the Stream Issues tab for dynamic stream plum12_dvt. Invoking the Promote command on issue #7 causes some or all these versions to be promoted:
version 8/30 of chap03.doc
version 9/36 of commands.c
version 9/10 of end.bat
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 Version X, in a workspace or stream, has '(overlap)' status if the parent stream's current version of the element contains changes that are not reflected in version X. (That is, the parent stream's version is not an ancestor of version X.) Such a version cannot be promoted to the parent stream; the user must create a new version with a merge operation, combining version X with the parent stream's version. The new, merged version can then be promoted. Similarly, an overlap can exist between the versions in two dynamic streams. See deep overlap. between the two streams for any element, the promote The operation (promote command) that transitions a version from being active in one workspace or stream to being active in the parent stream (or some other stream). This operation creates a new virtual version in the parent stream; the virtual version provides an alias for the real version, which was originally created in some user’s workspace. See version. operation fails with a "merge required" error box.
Send to Change Palette
(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.
Send to Issue
Adds (or combines) the selected issue record's change package entries with those of one or more other issue records. A popup window prompts you to specify the destination issue record(s).
Revert by Change Package
Removes the changes in the selected issue's change package from the stream. Typically, this involves one or more reverse patch An operation that removes a selected set of changes from the current version of a text-file element. See patch, change package. operations on file elements' contents, performed with the Merge tool.
Show Dependencies
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.
Open (equivalent to double-click)
Windows: run the appropriate command on the file, according to its file type. [note ] UNIX: open a text editor on the file.
View
Open a text editor on a temporary copy of the currently selected version (text files only).
Save As
Copy the currently selected version to another filename.
Promote
Promote the head version(s) of the selected entry(s) to the parent stream.
Remove
Remove the selected entry(s) from the change package.
Diff Against Basis
Compare the selected version with the corresponding basis version.
Show History
Open a History Browser tab, containing the transactions involving the selected file or directory.
Browse Versions
Open a Version Browser tab, showing all the versions of the selected file or directory, and their interrelationships (ancestry).
Send to Issue
Copies the selected entry(s) to another issue record's change package. If there's an existing entry for an element in a destination change package, an attempt is made to combine the existing entry with the entry you specified.
The default query An AccuWork query that you've designated to be executed automatically in certain situations: when you open a new Queries tab; when AccuRev prompts you to specify one or more issue records in a Send to Issue command; when you execute Promote and an AccuRev/AccuWork integration is enabled. of the current depot's issue database 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.
Properties
Displays a message box with information about the selected element.