When clicking a feature I don't have (e.g. adding an advanced shape to the whiteboard), leaving my work and jumping to a sales page is a poor experience
What is the challenge?
Jumping from a click on a feature I don't have to a sales page
What is the impact?
Unpleasant experience
Describe your idea
Open a side pane, new tab, anything else than leaving the current page I'm working on
Feature and "+Add" button missing after adding one child record in the "related" tab
What is the challenge?
The "+Add" button disappears after adding a child record on the "Related" tab
What is the impact?
I waste time/clicks navigating out of the record and then back into it.
Describe your idea
It's a bug, should be...
Laura Vassilowitch
3 months ago
in Epics
1
Shipped
As we're soliciting ideas from our internal teams, we'd like to make sure we keep the data quality high and all ideas into a proper category. Would be great if we could make Category a required field when submitting ideas.
Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets s...
Use case: I want to move my Confluence pages into Aha! so I can manage all my work in one tool Idea: Add a method to import my Confluence pages as documents in Aha!
Headers need to freeze when scrolling on the list views
When I scroll down in my list view I lose the column headers which renders my list useless. Please add scrolling on just the list details not the column header. This applies to all list views not just features.
Burndown charts based on user story points or time
Instead of showing burndowns based on feature and requirements, show them based on story points. So on day 1, you start out at full story points (release capacity) and with each daily increment you are indicating how much effort remains in story p...
Synchronize logged time and remaining estimates from Jira back to advanced estimates
Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...
We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...