Feature Requests

Teams would like a nice overview of what's happening in Canny. Let us know what specific data you're interested in seeing!

Have more granularity on emails received from Canny. For example, comment emails are only sent when mentioned. However, as an admin, I would like to receive a notification every time someone makes a comment.

Display both votes by users and votes by users' companies.

Make the back-end Canny-generated user ide accessible to clients from within the Canny interface.

Maybe using some tool that allows the community to work on the translations.

Canny's current (Un)subscribe implementation seems to be an All or Nothing selection. As an Admin and User I would like to be able to edit subscriptions on a more granular level, e.g.: -Updates to Posts that a user has created -Updates to Posts that a user has voted on -Weekly digest of new tickets -Weekly digest of ticket activities that a user has created / voted on -Updates when an admin tags a user in a comment The available options shall be shown in the user settings in the Canny web application and also in the Unsubscribe page linked in emails footers.

It would be nice to be able to grant different access to the API for difference services without having to share an API key with access to the entire API.

In a number of cases we redirect users to the login screen, but we don't have any messaging to indicate why. We should pass in a query param with an ID to indicate what message to render on the page. Examples: Arriving from a redirectTo : "You need to log in, in order to view that page" Arriving from SSO redirect attempt, but they are a member. "Your account exist in Canny, but you need to verify your Canny credentials before you can login" Session expiry: "Your Canny session expired, please login to continue"

I'd like to be able to relate feature request to each other, so that features that are not similar but still are related would be more easily discovered both by users and internally. A feature that does not have many votes might still be easy to do if we do a related feature. A feature might get more votes if you can easily find it because you are a voter or requester of some other request that is related, if you have an easy way to find related requests. I would add the "related" link for end users as an option in the suggested posts when posts are created.

In the Canny-Jira integration, Canny tags should come through on Jira tasks as labels, but they don't currently.