Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9172 of 9172

Consider inherited values when copying workspace settings for workspace templates

Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
Kristina Gass over 1 year ago in Account settings 0 Future consideration

Pivot report data visibility

The data in for a cell in the pivot report is only shown as a block of details, rather than a list view. It would be easier in the report if data could also be show as a list view. Examples attached.
Lucy Rivera over 2 years ago in Reports 1 Future consideration

When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA

Hi All, We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...
Guest almost 9 years ago in Ideas / Jira 4 Unlikely to implement

Separate Epics and Features in the My work left nav

I would find this view much clearer if these entities were in separate categories in the left side list. There seems to be plenty of room to do this.
Keith Mantell over 4 years ago in  1 Future consideration

Automation rules to update idea status when a comment comes in

I'm sure it never happens on your Ideas Portal, but often the Ideas that get submitted by our customers lack some key information that we need in order to make prioritization decisions. In those instances we put them in an "on hold or needs more i...
Derek Boriack over 7 years ago in Ideas 2 Future consideration

Automation for epics/features at the parent line level

As a portfolio manager, I want to create a single rule for epics/features for all workspaces in a parent line. Right now I have to recreate these individually at the workspace level. Part of the problem is the amount of time it takes to create eac...
Nadim Sobhani almost 4 years ago in Features 0 Future consideration

Add a "create retrospective option" to develop

What is the challenge? Having retrospectives is an important scrum practice, at the moment it's pretty manual. go to documents create a whiteboard add a copy of the end of sprint review insert a retrospective template. What is the impact? It's jus...
Mike Lowery 8 months ago in Agile reports / Sprints / Whiteboards 0 Future consideration

What if planning assistance

What is the challenge? It's rare when planning the next quarter/s that you have any real data about the size of the work you are planning. You can get engineering to do detailed estimates but that's wasteful and usually wrong, you can use gut feel...
Mike Lowery 8 months ago in Capacity planning 0 Future consideration

Displaying requirements within the Retrospective report

Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...
Sam Banks over 1 year ago in Releases 0 Future consideration

Send release phases to JIRA as proposed sprints

We would like to have a means to integrate Aha! release phases with JIRA sprints, as features included in phases are sent to JIRA.
Donna Sawyer over 8 years ago in Jira 3 Unlikely to implement