Skip to main content
System StatusContact Support
VersionOne Community

Working with Requests

This feature is available in Enterprise and Ultimate editions.

editions-eu.png

A request is an asset that allows you to capture submissions from internal and external users on extending or enhancing the functionality of a system. Product owners can use them to generate new stories, defects, portfolio items, or issues in future releases or map them directly to higher-level requirements in an external requirements document.

Requests.png

Adding a New Request

  1. Go to Product Planning > Requests.
  2. Click Add New... > Request in the Asset Tray on the left, or click Add Request above the grid on the right. The Request details page opens.

  3. Enter the item details and click Save. Title and Project are required fields.

Generating System Assets from a Request

You can generate various system assets directly from a request to accommodate the requirements of the request and begin development of the request features. Each request can generate multiple system assets, and the system establishes relationships between the request and the generated asset.

The following system assets can be generated from a request:

  • Story
    When a request has been approved to move forward with new development, you can create a story to implement the request. To generate a story from a request, on the Requests page, select Generate Story from the Edit action menu to the far right and enter field information on the Story Details page.
  • Portfolio Item
    When a request has been approved to group a set of stories and/or child portfolio items at a higher level, you can create a portfolio item to implement the request. To generate a portfolio item from a request, on the Requests page, select Generate Portfolio Item from the Edit action menu to the far right and enter field information on thePortfolio Item Details page.
  • Defect
    When a request is determined to result from a defect in the system, you can create a new defect to implement the request. Matching defect attributes are auto-filled. To generate a defect from a request, on the Requests page, select Generate Defect from the Edit action menu to the far right and enter field information on the Defect Details page.
  • Issue
    When a request identifies an issue for the team, you can create a new issue to implement the request. Matching issue attributes are auto-filled. To generate an issue from a request, on the Requests page, select Generate Issue from the Edit action menu to the far right and enter field information on the Issue Details page.

After generating one of these associated assets, you have several options for saving the data:

  • Click Save to save the new asset and return to the Requests grid.

  • Click Save & New to save the new asset and open a new details window to generate a second asset to be associated with the request.

  • Click Save & Close Request to save the new asset and close out the request. Closed requests remain in the system. To view all closed requests, click Filter and select Show Closed Requests.

  • Click Save & View to save the new asset and open the Detail page for the associated asset to make updates.

Tracking Progress of Related Assets

Once a request is related to one or more assets, you can use the request to track the progress of those items. To do this:

  • Click on the request to bring up its details view.

  • Click on Show Relationships to see the related items.

  • Use the grids to see assignment, scheduling and progress details for each related item.

Editing a Request

  1. Go to Product Planning > Requests.
  2. Select the request you want to update and click Edit to the far right. The Requests Details view opens.

  3. Update the item details and click Save.

Copying a Request

  1. Go to Product Planning > Requests.
  2. Select the request you want to copy and open the Edit action menu to the far right.

  3. Choose Copy from the drop-down list. The system generates a copy of the request above the original in the grid with a new ID beginning with "R". The copied request inherits the title and all other properties (attributes, links, and notes) from the original.

Closing a Request

  1. Go to Product Planning > Requests.
  2. Select the request you want to close and open the Edit action menu to the far right.

  3. Choose Close Request from the drop-down list. The Close Request page opens.

  4. In the Resolution field, select either Implemented or Rejected. Optionally you can enter a free-form description in the Resolution Description field.

  5. Click Close Request. The request is rendered inactive. Closed requests remain in the system. To view all closed requests, click Filter and select Show Closed Requests.

Viewing Closed Requests

  1. Go to Product Planning > Requests.
  2. In the filter drop-down menu, select Show Closed Requests. Closed Requests are shown with a strike out through the title.

Deleting a Request

  1. Go to Product Planning > Requests.
  2. Select the request you want to delete and open the Edit action menu to the far right.

  3. Select Delete from the drop-down list. The Delete Request page opens.

  4. Click Delete. The request is deleted from the system. On a temporary basis, you can view recently-deleted requests in the My Recent Changes box on the left.

Moving a Request to Another Project

To move a request to another project in your project hierarchy:

  1. Go to Product Planning > Requests.

  2. From the grid, select the request you want to move and click Edit on the far right. The Request Details window opens.

  3. In the Project field, select a new project from the hierarchical drop-down list and click Save.

  4. The grid redisplays showing your new project assignment for that request.

Watching a Request

You can "watch" requests, which means you receive alert notifications when any updates are made to a watched request. This allows you to keep track of changes as they occur. To watch a request, select Watch Request from the Edit action menu to the far right. See Watching Assets for more details.

Ranking and Ordering Requests

For some teams, using the priority value on requests is sufficient to organize and sort their list. Other teams might prefer to have specific control over the position of each request in the list. When in the default display settings, requests are displayed in their rank order. You can change the order of requests in your grid by:

  • Dragging and dropping requests up or down the ordered list

  • Clicking the up arrows to move a request up one spot or to the top of the page

  • Clicking a column heading to change the order from ascending to descending, or vice versa

You can use filters and customization to more quickly order a large number of requests. Absolute ordering is most important for items at the top of the list that are ready to be considered. The importance of an item's precise ordering is diminished the farther that item is down the list.

For ordering purposes, new requests are automatically appended to the end of the request list within a project.

Exporting Request Data to Excel

  1. Go to Product Planning > Requests.
  2. Click on the wrench icon  in the top corner of the grid and select Export (.xls). Refer to Export for more details.

Reporting

Use to the following reports to view request metrics.

Additional Options

  • Was this article helpful?