The importer shows all repository issues, including closed issues. It also doesn't show what the issue status is, so we must click through them to find those we want to import. I suggest: adding a status filter, set it to show open issues only sho...
Alexey Zimarev
9 months ago
in GitHub
0
Future consideration
What is the challenge? I have created a number of reports in a workspace that I want to move to a product-line for visibility. People get a little antsy when a report lives in their workspace but it is used elsewhere. What is the impact? Feels dis...
Stephanie Sullivan
9 months ago
in Reports
0
Already exists
Reporting on initiatives for multiple record types
What is the challenge? We can't see if epics and features are assigned to the correct initiatives. What is the impact? Lack of proper reporting on initiatives. Describe your idea Dear Team, I have a report starting from ideas, in which we would li...
Krisztina Hodjan
9 months ago
in Features
0
Future consideration
Control which fields a Develop user can update in a record in a Roadmaps workspace
Currently when an Aha! Roadmaps record is assigned to a Develop team that gives anyone with contributor permissions in the Develop team access to edit any field on the record (even those in the Roadmaps layout). I'd like a way to control this more...
When you create Pivot you would like to have totals per groups and be able to expand 2nd level columns to see further detail. If I have a PivotTable which is showing information on Epic Level, I would like to expand this column so that I can see t...
Christophe Bucheli
almost 3 years ago
in Reports
0
Future consideration
Workspaces allow users to update/change the name AND the prefix. Similar for a Team I would like to change the prefix of the team. right now the only work around is to delete the team and rebuild everything.
Currently trying to search for any features created with no integration Name / Jira Key. Being able to search for 'Is Blank' on no Integration Name will allow me to build the report I need.
Paven Bains
almost 3 years ago
in Reports
0
Future consideration
Terminology customizations should persist throughout all screens when cascaded from Account level
We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement).
Unfortunately, this update in terminology isn’t consis...
Kirstin Maurer
over 6 years ago
in Account settings
0
Future consideration
Sometimes PMs want to share a workflow to ensure that we are consistent and on-brand. It would be nice for product owners to be able to bulk update the workflows for ideas/idea portals/etc. instead of having to do so portal by portal.
Yancey Larochelle-Williams
almost 5 years ago
in Account settings
0
Future consideration
Release Phase Dates Determined by all related records
My last idea around being able to adjust Release Phase dates was rejected but our release phases are static (Closed Beta, Open Beta, GA) so simply adding another random phase isn't an option. This level of standardization is needed as we have very...
Guest
over 6 years ago
in Releases
1
Future consideration