Skip to Main Content
Status Future consideration
Categories My work
Created by Cy Caine
Created on Jan 15, 2016

Features by Person List on Home-My Work Screen too granular

Currently the page referenced above provides a very useful summary with these headings:

  • Assigned to me
  • Created by me
  • All features (by assignee)
  • All features (by status)

The problem with this it only allows me to view one "release" at at time. For teams working on a single product this would be perfect, move on. HOWEVER, we are a team that works on 15 products and each has its own product line in AHA but all are on the same sprint / release schedule. In the instance on my screen right now, I want to see the info under the headings above for our 14.4 sprint with a release date of January 27th. But I have to view each of these separately (Medical, Events, McKnights, myCME, etc.)

To be clear, I think it is great to be able to get the view that currently exists. I just want an option to "select all" for releases that are tied to the same release date or sprint #. 

  • ADMIN RESPONSE
    Jan 15, 2016

    As described, the current My work -> summary tab shows information per release. The List page is also available and shows features across all releases, however the page only includes featured which have been assigned to you.

    There are two workarounds which may be helpful. You can leverage Aha! Reports to create a view across all releases and products and filter and sort accordingly to your preference. You can save the view of your custom report (and share it with your team so that anyone can have easy access to the page.)

    You can also leverage the Feature -> Workflow page to show information across products/releases. This can also be saved view which can be shared.

    At this time, we are unlikely to make changes in this area but we hope that the above workarounds can help you and your team. We hope you can understand.

  • Attach files
  • Cy Caine
    Reply
    |
    Jan 15, 2016

    Thanks for the prompt response though I am disappointed in the "Unlikely to implement" flag. I do understand that similar info to what I am looking for can be obtained by running a report, but it isn't a very elegant solution. Hope you will reconsider at some point.