Skip to main content
Version: 1.6.0

Feature Requests

Create records in the Feature Request (pda_feature_request) table to register your product development ideas in the system.

The Feature Request table is inherited from the Demand (demand) table.

tip

Roles required:

  • Create, read – any user of the agent interface.
  • Edit – admin, pda_admin can edit any fields; pda_user or any other user of the agent interface can edit any fields of the records they created. If the pda_user or any other user of the agent interface is not the record creator, they will not be able to edit the Subject, Request reason, Expected solution, and Additional information fields. Other fields will remain editable.
  • Delete – admin, pda_admin.

Create a feature request


To create a feature request, complete the following steps:

  1. Navigate to SDLC → Feature Requests → New Feature Request.
  2. Complete the required fields and click Save or Save and exit. The request will be created in the Registered state.

Feature Request form fields

FieldMandatoryDescription
SubjectYAdd a short summary of the request.
StateNThe request state. The field becomes editable after the creation of the record. Possible options:
  • Registered – the request has been created and awaits a review.
  • Pending approval – the responsible employee is reviewing the request. They are usually the product owner. Note that no approval requests are created automatically when the feature request moves into this state.
  • Information needed – the responsible employee needs more information to make a decision on the request.
  • Approved – the responsible employee has reviewed the request and confirmed it.
  • In progress – the specialists are working on the solution for the request.
  • Completed – the request is completed.
  • Canceled – the request is canceled.
ImpactNSelect the level of the potential effect of the required change or its absence on the business user, service, or CI. Possible options:
  • Low
  • Medium
  • High
  • Very high
UrgencyNSelect the urgency of implementation based on how long it takes until a situation has a significant impact on the business. Possible options:
  • Low
  • Medium
  • High
  • Very high
Cancelation reasonYThe field is displayed when Canceled is selected in the State field. Specify why the request is canceled.
Request reasonYSpecify the cause of the request.
Expected solutionYSpecify an expected solution for the problem that caused the request.
Additional informationNSpecify additional information about the request.
ProductYSpecify the product which requires new or improved functionality.
CallerYSpecify the request caller. The field is completed automatically with the current user. You can change this value.
TasksNThe field is displayed after the first saving of the request, if the Product field is completed. Specify the tasks that must be completed to fulfill the request. In this field, you can select the records of the SDLC Task (pda_backlog_item) table and its child tables that belong to the same Product as the request. If you clear or change the Product of the request, the Tasks field gets cleared.

The following widgets are located on a saved record form:

  • Timeline that displays the time the record spent in different states.
  • Activity Feed with the History, Discussion, and Work Notes tabs.

To see created feature requests, navigate to:

  1. SDLC → Feature Requests → All Feature Requests. The list contains all created feature requests.
  2. SDLC → Feature Requests → My Feature Requests. The list contains feature requests created for the products where you are the owner.

Feature requests state flow


To change the state of a feature request, on its form in the State field select one of available options and click Save or Save and exit. The diagram below illustrates possible state transitions: