What is the challenge? The text editor has limited pre-set styles available. For more complex or technical documents, the ability to create and save custom styles would be beneficial, particularly for users of Aha! Knowledge Advanced. What is the ...
Brittany Rhoney
6 months ago
in Knowledge base
1
Future consideration
Who would benefit? User utilizing the prioritization page for features, and other record types What impact would it make? Reduce confusion on feature rank vs prioritization rank How should it work? Change the name of the standard field Feature ran...
Peter Whisenant
12 months ago
in Features
0
Future consideration
Automatically resize content when exporting to pdf
Who would benefit? anyone sharing pdfs What impact would it make? lift the barrier for duplicating effort by exporting content to excel then pasting in word docs How should it work? Auto shrink any content to fit to page. When I export an Aha! doc...
Nerissa Muijs
12 months ago
in Notes
3
Future consideration
Capacity planning for teams: define story point average velocity at the team level
Who would benefit? Teams using story points for team capacity planning What impact would it make? Greater flexibility to accurately define a team's available capacity in story points How should it work? Background: Story point average velocity (to...
Dale Potter
12 months ago
in Capacity planning
0
Future consideration
I'd like to be able to specify 20% contingency for a release. Meaning that if I have 100 points capacity, 20 of those points should be reserved for contingency / iteration (e.g. if doing Agile / Scrum). I'd like to see the contingency visually on ...
Elizabeth Karam
about 8 years ago
in Releases
1
Unlikely to implement
We have duplicate org names, that are only unique thru their client id. We need the ability to be able to determine the correct org (e.g. for adding an idea), by adding the client id to the organization dropdowns (e.g. Boeing 12345)
Sara Olson
over 2 years ago
in Voting
0
Future consideration
Filter the list of items to promote to or to link to.
When promoting an idea to a Feature or Epic(Existing), and when linking to another record, the list of items to be linked is not filtered by product / workspace. This creates a very long list of irrelevant items to get past if you are browsing to ...
Guest
about 3 years ago
in Application
6
Future consideration
What is the challenge? Today, users can create separate knowledge bases for public consumption vs private consumption (via SSO or password), but they cannot create a single knowledge base that contains and manages access control of both types of i...
Brittany Rhoney
3 months ago
in Knowledge base
0
Future consideration
What is the challenge? Users sometimes want to be able to share live Jira views, such as issue trackers with their knowledge base users What is the impact? This will allow important information to be surfaced to users that is not typically stored ...
Brittany Rhoney
3 months ago
in Knowledge base
0
Future consideration
Default view of Feature / Idea list for team members
You can currently customize your Feature / Idea list and save it. But there's no ability to set this customized view as the default for all team members. This would ensure everyone is looking at the same data with appropriate filters configured an...
Guest
over 5 years ago
in Features
0
Future consideration