When I create a new project, I start by creating an initiative then creating epics that are associated to the initiative. When I create features related to the epics, it does not inherit the association back to the initiative.
In the Feature List > Filter by > Feature Created Date, it is a little tricky to view items added today. There are options for:
- between, before, after and custom
Can you add "Today" as the first option in Custom instead of starting with "T...
Using Link to JIRA feature to 'import' Epics with Stories into Aha!
In our rollout we are looking at EPIC to Feature mapping from JIRA to Aha.
When we link a feature in Aha! to an EPIC in JIRA the stories do not come across as requirements - we would expect them to do this!
When scoring features, the scorecard is presented dab smack in the middle of Aha! thereby blocking the text describing the feature. Scoring is an important process to us. When answering our scoring questions, I like to read and re-read the feature...
Improve feature/requirement navigation of new layout
There is not an easy way to navigate from requirement to requirement within a feature from a workflow, such as outstanding approvals. Clicking into a requirement, navigating back, etc. to find the next requirement or corresponding task has doubled...
Allow bulk editing within the requirements tab of a feature, and other places
It would be great to be able to quickly bulk edit records from various places in Aha! besides only the List report. Common examples I run into: Bulk editing requirements in a feature (bulk convert to features, assign, change status, etc.) Bulk edi...
Todd Meyer
almost 5 years ago
in Features
0
Shipped
We use a pre-defined tag field for our customer list. It's a long list and we'd like to be able to use a "type ahead" field for a better user experience.
Aha to Github Integration: Improved integration so Tables do not break once transferred
As discussed with your internal teams, the issue we experience at the moment is that we submit tables in a feature to capture requirements (We have a lot of field mapping we do) but a number of times when the table is received in to Github the tab...
Capacity planning in story points needs to support decimals
Our story points are in the following increments:
.5, 1, 2, 3
Currently you only support whole numbers so I have to create a custom field to track this.