A small annoyance. We use feature cards for stories and have long titles like "As a _, I need to do _, so I can _ ." The titles are hard to edit because the text field is a single line. The long line can't be seen all at once - I am forced to move...
Andrew Vit
over 4 years ago
in
0
Future consideration
Today there is no good way to show the delivery of requirements for one feature spanning multiple releases. For instance, if you have 3 of 4 feature requirements being delivered in Release X, but the feature itself won't be delivered until Release...
Micaela Heck
over 8 years ago
in Features
1
Unlikely to implement
Maybe this more of a product idea for Prezi team, but it would be very cool to be able to embed Aha! views and notebooks within a Prezi. Maybe there is already? The business value would be able to convey complex visual concepts (prezi) mixed with ...
Guest
over 6 years ago
in Wanted
0
Future consideration
Users should be able to create Develop Automation rules at the account level so they do not have to rebuild them every time they create a new Develop team. Currently, users need to copy and move automation rules whenever they create a new Develop ...
The competitor functionality right now represents the company rather than the products it markets, with products being represented as bullet points in the description. You therefore can't do things like e.g. have different pricing or strengths/wea...
Guest
over 8 years ago
in Strategy
1
Already exists
Currently when deactivating a user, the user then becomes 'greyed' out. This isn't readily obvious due to coloring, resolution, etc.
Suggestion is to clearly annotate the user with a Joe Smith - Deactivated or something similar
Joe Carpenter
over 8 years ago
in User management
0
Unlikely to implement