We have many custom fields, som are "Entry Required by user", some are information only, would be good to highlight with a colour which a user has to focus on.
Tomas Heydal
almost 5 years ago
in Ideas
0
Future consideration
Bug: Reorganizing features in Gantt produces different results for each user
1) Take a release with 4-5 features 2) On a gantt roadmap, reorganize (sort) the features differently 3) As a different user, view the gantt chart The order of the features are not the same between both users and becoming annoying.
Austin Rappaport
over 2 years ago
in Roadmaps
0
Already exists
I am using CSV import to integrate my Customer Support system (FreshDesk) with Aha!. The idea is that CS is our public interface and will receive and triage tickets (questions, defects, product enhancements, and incidents). Any valid defects/produ...
Guest
about 7 years ago
in Application
0
Unlikely to implement
Allow SAML / SSO created users to be placed in a default permissions group
We are allowing all the engineers in our company to view the roadmap information in Aha! by enabling SSO registration. It's a transparency policy that enables the engineers to see how the feature pipeline is determined.
Issue here is that SSO crea...
Marcus Gavel
over 9 years ago
in User management
6
Already exists
"Select All Current and Future Releases" within many views in Aha! (including roadmap timeline)
I love that I can save views, however, in the roadmap when save a view with all of the current releases selected, then add a new release, that new release is not reflected in the saved view - I must go back and manually edit the saved views as new...
Guest
over 9 years ago
in Reports
2
Already exists
As we manage portfolio level initiatives, it can become important to assign multiple representatives from different teams to initiatives in a certain status
Lili Sander
almost 5 years ago
in
0
Unlikely to implement
At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
I'd also like to see it highlighted where things have changed since a benchmark on a release - which is a separate distinct issue. This needs to include all fields within Features. This is not achieved by inspection of each feature, my key stakeho...
Guest
almost 5 years ago
in
0
Future consideration
Hello,
We recently started using Aha to help manage our projects. It is important to note however that those are recruitments projects and not software development. It means we had to change the terminology (because “features”, “release”, etc. d...
Guest
over 7 years ago
in Application
0
Unlikely to implement