be Able to Drag Release Phases from one Release/Schedule to Another
I am adding a new Schedule to my roadmap project plan and want to move several release phases and associated activities from one Schedule to another. I cannot seem to do this. Essentially I want to split a release on the Gaant view.
Jamie Lefkovics
over 4 years ago
in Releases
0
Future consideration
Ability to add context to to-do e-mail reminders - for ex: Initiative Name - to-do; Release Name - to-do
Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...
Ability to link shipped releases and completed initiatives
Once a release ships or an initiative is marked as complete, they no longer show up as visible options for record linking and need to be re-opened to make this possible. As I'm cleaning up old content in our Aha implementation, I'm thinking it wou...
Guest
over 4 years ago
in Roadmaps
0
Future consideration
I want to assign owners to different workgroups so the owners can manage their workspaces and custom layouts. I do not want users to be able to edit existing custom fields unless authorized to do so. The reason for this is, if the custom field is ...
Guest
over 4 years ago
in Application
0
Future consideration
Currently adding existing features is not very convenient as they just get thrown somewhere into the map It would be great to see whether a feature has already been added to another map (sometimes I would like to know whether I can delete a featur...
Guest
over 4 years ago
in User story map
0
Future consideration
Working with both features and master features we find the toggle to view either Master features or features in the Board view really useful. However, we really miss the same toggle in the List view where we only can see features. Please include t...
Andreas Moritz
over 4 years ago
in Epics
0
Future consideration
Ability to add specific field from elements like feature (currently only defaults to feature name for example)
When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
Arun Kalyanaraman
over 8 years ago
in Features
1
Already exists