Allow creation of groups of Aha! users to make the allocation of Features/Requirements/Todos to Aha! users simpler, quicker and less painful
Consider this real world example from Aha! this week. I need to allocate a ToDo task for everyone in the CS team to complete. Right now my workflow is:
1. Consult a third party source to get a list of everyone who is in CS (and keep this list open in another tab so I can check back on it)
2. Eyeball the list of nearly 100 users, scrolling alphabetically so I can check next to each name in CS
3. Repeat x28 until everyone in CS has a ToDo allocated
This is painful for me in an organisation the size of Aha! I cannot imagine how painful and prohibitive this would in an instance the size of Aha! with more users.
This has not been reported to me by a specific large enterprise company but would apply to any of the Enterprises on the list.