Features like this one typically represent big ideas you have for your product. They can be defined around broad capabilities you'd like to enable, or user needs you'd like to address. The truth is, features will evolve as they progress through your prioritization process and you get a better sense for the solution they entail, and it's ok to update their name and description as you go.
Each field below represents a data field that you can also add as a column on your Features board to help you prioritize and plan.
On the Insights tab, you'll see everyone who's ever requested this feature, what they said about, and how important it is to them – based on user insights linked to this feature.
You can also add this feature as a card on your Portal to allow colleagues and customers to vote and provide feedback on it.
Features like this one typically represent big ideas you have for your product. They can be defined around broad capabilities you'd like to enable, or user needs you'd like to address. The truth is, features will evolve as they progress through your prioritization process and you get a better sense for the solution they entail, and it's ok to update their name and description as you go.
Each field below represents a data field that you can also add as a column on your Features board to help you prioritize and plan.
On the Insights tab, you'll see everyone who's ever requested this feature, what they said about, and how important it is to them – based on user insights linked to this feature.
You can also add this feature as a card on your Portal to allow colleagues and customers to vote and provide feedback on it.
More info: http://bit.ly/getting-started-with-features
Updating description to test feature updates in Productboard