View the request catalog

The request catalog displays all the requests in a Dimensions CM product or stream. You can open any request and view its details.

To view a request in the request catalog:

  1. In PulseUno, navigate to Spaces and select a space.

  2. Select a Dimensions CM product and, optionally, a stream.

  3. In the sidebar, select Request Catalog. The Request Catalog opens, displaying information about each request, such as the request's owner, lifecycle state, and any backlogs and iterations to which it belongs.

    Tip: You can sort the list and search for specific requests.

  4. To open a request, click its name.

  5. On the request's page, you can review the following information:

    General tab

    Displays information about the request:

    • Request summary.

    • The request's acceptance criteria.

    • Attachments.

    • Related requests.

    • The related stream and design part.

    • Associated reviews.

    • Associated changesets.

    • Total and remaining story points.

    • A burndown chart (if the request is included in an iteration).

    • An external link, for example, the URL of an external website or the value of an SBM ticket related to the request. If the value is a hyperlink, it opens in a new tab or window. This field only displays a value if it has been mapped to request attributes.

      An external link may look similar to this:

      For details, see Map PulseUno attributes to Dimensions CM request attributes.

    • The request owners and their capabilities.

    • Any iteration, backlog, or epic to which the request belongs.

    Note: PulseUno administrators can configure which fields will be displayed in the General tab.

    Attributes tab

    Displays the request's user-defined attributes which record important information about the request. For example, estimated/actual completed date, estimated/actual effort, and severity.

    Some attributes may be required.

    Action History tab

    Displays information about when the request was actioned to different states in its lifecycle, and the users that performed the action.

    To filter the action history, select a lifecycle state.

Back to top

See also: