Coalesce common dependencies in the dependency map
Right now, I have a task which depends on several other tasks, and some ofthose depend on the same underlying tasks. An example of this would looklike:
A / | \B | C \ | / D
I would expect the dependency map view to draw a line between B&D as ...
My use case: I have existing epics in progress I want to import from Jira and I want to show accurate progress towards these epics based on story points completed. Here is the situation I am running: Create an epic in Jira, and 2 child stories und...
Max Robbins
about 1 year ago
in Features
0
Future consideration
Our Use Case
We have a process that we've actually implemented as a product within Aha! that helps us track Change Requests. We set it up as a separate product within Aha! because this process has a different workflow that we wanted to capture, in...
Sikia Soller
almost 7 years ago
in Features
0
Future consideration
Formatting issues with description with html tags for csv import
When importing my tickets into Aha Develop via the "import with csv" option, I have some issues with the formatting. With no formatting, the new line character "\n" is completely missing. (Please see no_space.png). If I try to replace the "\n" wit...
Ravisha G
almost 2 years ago
in Backlogs / Features
0
Future consideration
Ability to add comments to the link records or the reason for dependency.
What is the challenge? Not able to comment to why a particular linked components are dependent of other one. What is the impact? For certain dependency to be created there are some additional comments required hence we are looking for a comment to...
Can we have the progress set to 100% on release items when they are closed?
What is the challenge? Manually editing the % progress is a pain What is the impact? Loss of productivity Describe your idea Make it editable in the UI and workflow to auto set to 100% when the ticket is closed.
Guest
8 months ago
in Features
0
Future consideration
Automatically update features end date by the end date of the release
If the feature will be moved from one release to another release, end date of the feature should be automatically updated by the end date of new release.
Kote Khutsishvili
over 4 years ago
in Features
1
Future consideration
There are times where we have multiple people working on a story, either due to investigating a spike or pair-programming. It would be nice to be able to assign a feature to more than one person at the same time.
Christopher Davies
over 9 years ago
in Features
5
Unlikely to implement
Allow disabling the automatic feature status updates based on requirement status while keeping the feature progress calculation based on requirement completion
we sometimes add user stories to a feature after other ones have been completed, for example feature is to deliver a piece of functionality and we create a spike, and then that may get closed before we add all the other user stories needed to comp...
Ben Snapper
over 4 years ago
in Features
3
Future consideration