Feature Request Guidelines & How to Write a Good Feature Request

Welcome to the Feature Request Board!

This topic is for CarePortal feature requests. 

Here are a few guidelines on how to use the Feature Request forum, so that our planning team can effectively use and apply your feedback:

If it's a bug, create a ticket

This topic is for requesting new features. If you're reporting an actual bug, you should contact CarePortal Support so they can assist further. 

Search first

It's always possible that someone else has already made a suggestion similar to yours. Keeping conversations in existing threads makes them easier for others to find, and helps keep the Community organized.

Use keywords in your post title

You want your post to be as searchable and easy to find as possible. To that end, try to include any relevant keywords in your post title. That way, others will be able to find and contribute to your post (by voting or commenting) instead of creating duplicates. 

Vote for suggestions you'd love to see implemented

Votes do matter! See a feature request that would substantially improve your experience with the platform? Use that up arrow! Feel like making a post that just says "+1"? Please use the upvote button instead. Post a comment to share your detailed use case. Feel free to use the down arrow as well if you think a feature request would be more trouble than it's worth. 

Remember: this feature request board is meant to help us plan and prioritize effectively. The upvote is a vote, not a like. Only vote for those things that you think represent substantial improvements to the platform.

Give details, examples, and tell us about the problem you’re trying to solve

Our planning team members are problem solvers! The most helpful feature request posts are the ones that describe the nature and scope of a problem. Try to share the following information in your post or comment: 

• Who (what role[s]) is this Feature Request primarily for?
• What exactly is being requested? Be specific about the functionality you'd like to see. 
• Why would this new feature be a good addition to the platform? Provide use cases! 

Here is a template for feature requests that you can copy and paste - then just fill in your details. 

It's much easier for us to address a suggestion if we clearly understand the context of the issue, the problem, and why it matters to you. 

Post maintenance and archiving

Requests that have been inactive (have not received a new comment) for 6+ months will be archived. These are retained internally and remain visible to product managers. This helps  to keep the community navigable and helps us prioritize the requests that are most important to the largest number of users.

This doesn't mean your idea was bad, or that it will never happen. It just means that it wasn't something that came up for a lot of users. Since we keep records, if the idea pops up again, we’ll aggregate those ideas behind the scenes and know when something keeps coming up. 

This also means that if there's an idea you like, be sure to stay active in that conversation! 

Thank you for reading this and for understanding how we address suggestions. We value all feedback and we're happy to have a place to engage in these conversations.