Retrospective should ignore records that were moved in with "Will not implement" status
Who would benefit? Product Owners and Project Managers What impact would it make? This would reduce the list of records shown as "incomplete" when the records were added to the release after already been assigned "Will not implement" How should it...
Allow referencing User-type fields in custom worksheet equations
I'm trying to create a custom equation formula to determine if a user field "Team Members" is empty or not. User fields are currently unsupported in custom worksheets, so I'm not able to build the equation I need.
Phil Warden
almost 4 years ago
in
0
Future consideration
Who would benefit? ideas portal users What impact would it make? medium How should it work? Expansion of the current functionality that only supports one custom filter. For our purposes, we have three main custom fields for ideas. "Idea Type", "Ap...
Jacob Papka
12 months ago
in Ideas portal
2
Future consideration
Who would benefit? users in need of detail What impact would it make? provide additional method of validation or review How should it work? When adding columns to a List, whether features, epics, requirements, etc. it would be nice to have "Last m...
Guest
12 months ago
in Features
0
Future consideration
Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
Steven Schafer
over 1 year ago
in Features
5
Unlikely to implement
Who would benefit? All users utilizing epics, features, and workflow syncing What impact would it make? How should it work? Currently when a feature status change causes an epic's status to change due to workflow syncing, the epic history does not...
Peter Whisenant
12 months ago
in
0
Future consideration