We are hoping to either: 1) Set-up a manual automation trigger for features created prior to an automation rule or 2) Have an option to retroactively apply a new automation rule too all features or just new features.

It would be helpful to be able to grab a project and slide it from left to right to "sort" the projects

The filters have been upgraded with some nice Quarter options, like This Quarter, Next Quarter, etc. I like that! I would also find it very useful to have specific Q!, Q2, Q3, Q4 filters, so I don't have to manually set them up in the filter or in...

Currently when requesting work from another workspace via the to-do feature, the only way to change the response (e.g. changing from rejected to approved) is to delete the workspace then adding it back in. Would be great if there's a simpler way t...

It'd be nice to filter as I type. When there's a lot of saved views and I'm looking for something, I'm not always exactly sure the name. This would help the discover process.

Feature cards on the features board are colored based on their status. When stakeholders, such as leadership, are browsing the features board, they may not know how the statuses correspond to the color of the feature cards. It would be helpful to ...

To reduce the potential of missing a milestone we are creating to-dos for the milstone. To see the to-dos a user has to navigate to the milstone itself, view on My Work page or create a report. Would like the to-dos for milestones/phase to show at...

To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.

This would be useful, as an option so those who prefer the prefix can still access it. At the moment the prefix is clouding our users view, an slowing down different internasl processes