Manage feature requests

Open Apps and select an app to work with its requests. Use Inbox for pending review, or Requests to track approved requests across apps.

Create a requestCopy Anchor Link

Dashboard requests are approved immediately and can appear in the connected mobile app. Use content you are ready to share with users.

1. Open your app from Apps and select New request.
2. In New feature request, enter a Title of up to 300 characters and a Description of up to 10,000 characters. Both are required.
3. Select Create request.
4. Look for Feature request created. The request starts in Roadmap with one vote from its creator.

You find it in the app's Requests tab under Roadmap. If the search box above the list contains text, clear it.

Open a requestCopy Anchor Link

Select a request's row or title in Inbox, in Requests, or in an app's Requests tab. The request panel opens from the right.

The panel header shows the status, the app name, how long ago the request arrived, and the title. Below the description you see the request's details:

• Status, which you can change here once the request is approved.
• Votes and Submitted.
• Source, either From the app or Added by you.
• Email, the submitter's address or Not provided. An Unsubscribed badge next to the address means the user turned off emails.
• Device details such as Platform, Device, App version, Locale, and Screen. These rows appear only when the mobile app sent that information.

Comments lists the discussion. Your own replies carry a Developer badge.

If you close the panel with an unsent reply or an unsaved edit, Featurama asks Discard your changes?. Select Keep editing to go back, or Discard to drop the text.

Edit a requestCopy Anchor Link

Edits to a visible request change the content users can read. There is no separate publish step.

1. Open the request.
2. Select More actions (…) next to the title, then Edit request.
3. Change Title or Description in the panel. Both must remain filled in and use the same length limits as a new request.
4. Select Save changes and look for Feature request updated. Select Cancel instead to keep the old text.

The panel then shows the updated text.

Reply to a requestCopy Anchor Link

A reply is a comment that users see under the request in the app. It is not a private note. Do not include sensitive information, even when a request is pending review.

1. Open the request from Inbox, Requests, or the app's Requests tab.
2. Read the existing Comments.
3. Type in Reply as developer.... Enter adds a new line.
4. Select Send reply, or press Cmd+Enter on a Mac and Ctrl+Enter on Windows or Linux.
5. Look for Reply posted. If the request has an email address and the user has not unsubscribed, the message reads Reply posted. The user gets an email. instead.
6. Check that the comment appears with a Developer badge.

You can reply to a pending request too. Until you approve it, only the person who submitted it can see the request and your reply in the app.

Reply emailsCopy Anchor Link

The line under the reply box tells you whether your reply also goes out by email. Also sent by email to followed by an address means the submitter left that address with the request. Visible to your users in the app. means there is no address or the user unsubscribed, so the reply appears only in the app.

When a request has an email address, each developer reply sends one email to that address and to no one else. The subject names the request and current status in the app's selected email language. The email contains your reply and says who replied. It links to the request when a public webboard or app deep link is available, and explains why the user receives the email.

• Developer replies send a reply notification. Status changes send a separate status notification. Approval without a status change and comments from other users do not send email.
• Featurama sends the email in the background after it saves your reply. A failed email is not retried, and it never blocks or removes the reply.
• Sending requires email to be set up on the Featurama instance. Reply posted. The user gets an email. confirms that the reply saved and the request has an address. It does not confirm that the email reached the user's inbox.

Every email to a user has an unsubscribe link. After unsubscribing, that user gets no reply or status emails from that app, and your replies still show in the app. The panel then shows Unsubscribed next to their address.

Users leave an address when the app's Email collection setting asks for one. Turning collection off later does not remove stored addresses, so those requests still get reply emails.

To write a separate message instead, select the address in the panel's Email row. It opens your email app.

Move requests between statusesCopy Anchor Link

Requests shows approved requests from all your apps. Pending requests stay in Inbox until you review them.

1. Open Requests.
2. Choose All apps or one app. To find a request, type part of its title, description, or email address in the search box.
3. Pick List or Board view.
4. Move the request in one of these ways:
   • In List view, select the status icon at the start of the row and choose a status under Move to.
   • In List view, hover over the row and drag it by the grip handle at its left edge onto another status group. Collapsed groups accept drops too.
   • In Board view, drag the card to another column.
   • Open the request and choose a new Status in the panel.
5. Look for Moved to followed by the status, for example Moved to Roadmap. A change in the panel shows Status updated.

List view groups requests under Requested, Roadmap, In progress, Done, and Declined. Done and Declined start collapsed. Select a group's header to expand or collapse it. Board view shows the same five statuses as columns. Select a card to open the request.

An app's Requests tab uses the same list and also shows pending requests, marked with a pending icon in their status group. Choosing a status for a pending request also approves it. Approval and review explains the visibility change.

Move several requestsCopy Anchor Link

1. In List view, hover over each request you want and select its checkbox.
2. In the bar above the list, check the number of selected requests.
3. Choose a status under Move to…, or select Mark done. Select Clear to drop the selection instead.

You can also drag one of the selected rows. Featurama then moves all selected requests together.

Each request is a separate update. When all of them succeed, you see a message such as 3 requests moved to Done. When some fail, the message says how many, for example 2 of 5 requests could not be moved. Check each request's resulting status before retrying.

Mark work done or reopen itCopy Anchor Link

• For one request, move it to Done with its status menu, by dragging, or with Status in the panel.
• For several requests, select them and choose Mark done in the selection bar. If the message reports requests that could not be moved, check those before retrying.
• To reopen a done or declined request, expand Done or Declined and move the request back to Requested. There is no separate reopen button. The request stays approved.

Moving a request never sends it back to Inbox. A pending request does not appear in Requests until you review it.

Delete one commentCopy Anchor Link

1. Open the request and find the comment under Comments.
2. Select the trash icon next to that comment, labeled Delete comment.
3. In Delete comment?, check the author and the comment text. Select Cancel to keep it.
4. Select Delete comment and wait for Comment deleted. The comment disappears and the count updates.

Only that comment and its comment votes are removed. Deletion cannot be undone. An email already sent stays in the recipient's inbox. The comment also disappears from the public board.

Delete a requestCopy Anchor Link

Deleting a request permanently removes it, its votes, comments, and comment votes. Use Declined instead if you want to hide it from the normal mobile list while keeping its history and the option to reopen it.

1. Open the request and check that it is the one you intend to delete.
2. Select More actions (…) next to the title, then Delete request.
3. In Delete this request?, select Delete request. Select Cancel instead to keep it.
4. Look for Request deleted. The panel closes and the request leaves the list.

If an action fails or times out, check its result before trying again.