We update hourly rates on an annual basis. The Teams we define span Scenarios so we need to be able to define an hourly rate by Scenario for a Team. This functionality will enable flexibility in cost reporting and forecasting.
Chris Brooks
over 4 years ago
in Capacity planning
0
Future consideration
Colours for custom fields, especially record relationships
When creating custom fields for record relationships, these only are presented as plain grey links. It would be great if these links could be coloured - either by specifically choosing colours, or by programmtically setting colours like with tags....
Guest
almost 6 years ago
in Account settings
0
Future consideration
Update mapped initiative field in integration when changing text of initiative name
The initiative field is available in the Jira integration under the Aha! feature record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the initiative record.) However, the mapped i...
Craig Pflumm
over 4 years ago
in Integrations
0
Future consideration
Implement app protection policies using MSFT SDK to enable iPhone users to use the app with MSFT SSO.
Who would benefit? IPhone users What impact would it make? Would allow iPhone users whose firms implement SSO to access the Aha! app to be able to use it on mobile How should it work? When a user tries to log into the mobile app on iPhone it shoul...
Guest
about 1 year ago
in Application
0
Future consideration
when adding file into feature of epics, i shall be able to select document from my notebook
Who would benefit? Every person editing a feature or epic What impact would it make? As i write more on more document in the notebook, it shall be logical to be able to add these documents to my features How should it work? i shall be able to sele...
Guest
about 1 year ago
in Features
0
Future consideration
Improve Drag 'n' Drop Reordering Experience in Gantt Charts
It's kind of painful trying to reorder things inside of Gantt charts compared to drag 'n' drop reorder functionality in other platforms my company uses. It's very tedious in my opinion and kind of aggravating to be brutally honest. This applies to...
Bob W
over 3 years ago
in Roadmaps
5
Future consideration
Add message or alert when a report has more than 2000 records and is being shared as a webpage
Overview
Reports that are shared as a webpage can display a maximum of 2000 records / rows right now. We should display a message somewhere that indicates that only 2000 rows will be shown.
Challenge
If a user has more than 2000 rows on th...
Austin Merritt
over 3 years ago
in
0
Future consideration
User Story map should support epics that span columns
I created a user story map with multiple columns, each for one activity in my flow. Now I want to pull features from multiple columns into an epic and move into JIRA. However, as soon as I assign to a master feature, the user story map pulls the f...
Ashwin Jeyakumar
over 4 years ago
in User story map
0
Future consideration
Workspace name is removed from a sub-release in the Release Gantt
Who would benefit? Those using Roll Up releases What impact would it make? It would improve clarity How should it work? This is really a bug - often when the sub-release is expanded the workspace name is removed. It should persist.
Guest
about 1 year ago
in Releases
0
Future consideration
The default assigned colours for releases can often be very similar to each other. Being able to manually updated them will help with clarity of the view and also support teams with visual impairments/colourblindness.
Steve Dagless
over 4 years ago
in Releases
0
Future consideration