Sometimes our QA or Doc teams will reject a requirement because they have questions or additional clarification is needed. Once they are satisfied with the requirement they would like the ability to go back and approve it. This way we don't have t...
Sikia Soller
over 4 years ago
in Features
0
Unlikely to implement
Aha scorecard screen view access for viewers/reviewers
We are sharing the features with the devTeams and we believe that the rating information gives them the understanding on the value/importance of the feature (in our case it is a WSJF sorted out calculation, so they could see which was the business...
I would like to create a report that shows by release the feature development by calendar quarters.
For Wolters Kluwer our development team uses program increments which are calendar quarters. Then the quarter is broken down into iterations. So I would want to create a report for a release showing the features by the quarter in which they were d...
Guest
over 4 years ago
in Features
0
Already exists
push the columns out so the Feature details slideout screen doesn't cover them (Features List view)
Right now you're using a CSS fixed position style, which slides out OVER the x-scrollable feature list. This means when you're looking at the details of the last two columns in the list, the details screen covers the columns, and the only way that...
Melissa Hopkins
over 9 years ago
in
0
Unlikely to implement
Instead of just using custom or default fields to filter and segment ideas, it would be nice if under a workspace you could have multiple partitioned queues. We want to use Aha! for all ideas, regardless of type/size, but I want to partition inter...
Differentiation on Ideas Portal of Idea Promotion Work Item Type
Many of our Ideas entered from the ideas portal become Features in our backlog, however there are also ideas that become Epics/Master Features. When an idea is promoted a feature or an epic, the idea status changes to "Likely to Implement". It wou...
Guest
over 4 years ago
in Ideas portal
0
Future consideration
Update automation logic to employ looking at child records before making a change to the parent record
For example, if I create a rule that states, when the status of a feature is changed to Closed in Jira, update the status of the initiative; will this change the status of the initiative to closed even though there may be other open features in it...
Fatimah Gorin
over 4 years ago
in
0
Future consideration