Creating and managing Requests
Create Requests, edit their details and ownership, link development work, and delete Requests you no longer need.
Written By Markus Palm
Last updated 39 minutes ago
Overview
A Request is the item your team tracks from a customer need to a decision or delivery. You can create Requests manually, edit their details and ownership, link development work, and delete them.
The actions available to you depend on your teammate permissions. Ask a Workspace admin to review your role if you cannot create, edit, or delete Requests.
Create a Request
Go to Requests & Insights → Requests and click 'Create request'
Enter a title and a description of the need
Choose the category and complete its form fields
Check the author and visibility
Click 'Submit request'
To create a Request on behalf of a customer, select them as the author. The button then reads 'Create request'. If Featurebase finds an existing Request for the same need while you type, it targets that Request and the button reads 'Add insight'. The feedback is then attached to the existing Request as an Insight instead of creating a duplicate. You can change or dismiss the suggested Request before saving.
Note: A Request you author yourself is created in the Internal category and never appears on the portal. When a customer is the author, category access and Request visibility determine who can see the Request.
Edit Request details
Open the Request to change its content and properties. The 'Activity' tab lists every change, 'Discussion' (labeled 'Internal discussion' when the Feedback Portal is off) holds the comments, and 'Insights' holds the supporting customer feedback.
Title, description, and form values
Click the title or description to edit it. Inline changes save when you leave the editor; if a 'Save' button is shown, click it to apply the changes. Update form values from the Request's field controls.
Describe the customer need clearly without replacing the original evidence. Use Insights to preserve quotes and source context. To change which fields the form asks for, edit the category form.
Category, labels, and assignee
Use the Request's detail controls to change:
Category: The Request type, which sets its form and access rules
Labels: Additional ways to organize the Request
Assignee: The teammate responsible for it
Check visibility after moving a Request to another category, because the new category's access rules apply.
Tip: Use bulk editing when the same change applies to a selection of Requests.
Author and status
Select the author control to attribute the Request to the correct person. On an author-only or company-only Request, changing the author can also change which customer or company can see it.
Select the current status to update progress; statuses also organize your Roadmaps. When customers need an explanation, use Sending Request status updates to control the message and follow-up.
ETA and portal pin
Set the ETA from the Request's details to record the expected delivery date. Whether customers see it depends on your Request detail display settings.
To keep a Request at the top of the portal, open 'More actions' and choose 'Pin to top of the portal'. Choose 'Unpin from the portal' to remove the pin. Pinning changes only the position; it does not change who can access the Request.
Link development work
Use the connected tool's action on the Request to link development work, such as a Linear or Jira issue. Available actions depend on the integration and your permissions.
The integration guides for Linear, Jira, ClickUp, GitHub, and Azure DevOps cover connecting each tool and configuring its synchronization. Keep customer demand and discussion on the Request, and use the linked development item to track implementation.
Share a Request
Use 'Copy request link' to share the Request, or 'More actions' → 'Copy request ID' when another tool needs its identifier. 'Copy as prompt' copies the Request context for use in an AI tool.
Delete a Request
Open the Request's 'More actions' menu, choose the delete action, and review the confirmation before proceeding.
Important: Deleting removes the Request record. To combine a duplicate with an existing Request, merge the Requests instead.