Currently, the Pivot Table does not allow sorting column and row headings - everything is sorted in ascending order. We should use the same tech for sorting cell contents to allow sorting row and column headings.
about 5 years ago
After releasing the new Gantt, releases can now have a manually set start date which is not determined from the first phase / feature.However, you are not able to see this start date on the details drawer. That means when you are working from a re...
10 months ago
Release Gantt with rows/phases that can be ordered for a better visual layout
A release gantt sorts its rows by phase date i.e., phases with earliest starting date are on top, and later start dates at the bottom. This makes visualization for a project with many different departmental tasks difficult and cumbersome. E.g., in...
almost 5 years ago
Allow existing release templates to be copied to make a new template. For example, copy a product line template to a product to customize that template. It is too difficult to do this manually, especially when you consider that each phase has a co...
over 3 years ago
Display sequential initiatives on a single line in roadmaps
We are trying to represent on a roadmap the phases of an activity as a sequence of initiatives on a single line, e.g.:|------------Jan -------------|----------- Feb -------------|--------- March ------------| Project A – Phase 1 Project A...
9 months ago
Support the "links to" field mapping with next-gen templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates.
Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" ...
When using a custom roadmap and selecting to use "Thick bars with text inside" the placement of records will appear staggered based on the length of the record name/label, instead of allowing the records to show on the same row (side-by-side).
10 months ago
We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.