Skip to Main Content
ADD A NEW IDEA

Features

Showing 1187

Allow user be be set to "default unassigned" using automation

What is the challenge? I want to remove me the PM from the assigned field once the work has been sent to my development team, so that the right person can assign themselves. What is the impact? I have to remember to remove me from the field. Descr...
Mike Lowery 29 days ago in Account settings / Features 0 Future consideration

Allow Product value scorecard and custom scorecards to be read-only on Prioritization view

What is the challenge? Currently, it is not possible to make the Product value scorecard or a custom scorecards read-only on the Prioritization view. What is the impact? This prevents you from being able to lock-in a scorecard because even if you ...
Chris Quigley about 2 months ago in Features 0 Future consideration

Automation of feature to another release based on custom field

Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
Danielle Martinez 11 months ago in Features 2 Future consideration

Don't remove lane in feature board view once shipped

Currently when you ship a release the lane disappears from the feature board view. It would be great if instead of disappearing all together the lane was simply greyed out or marked as shipped. The feature board view is where we look to see what w...
Emily vargas over 6 years ago in Features 26 Unlikely to implement

Allow the creation of to-dos in a custom "create new feature" template

You just launched a feature whereby you can create a list of to-dos in a feature, and then when you copy that feature the to-dos are copied over with them. However this is a very clumsy way to have to create new features every single time. I need ...
Guest over 7 years ago in Features 17 Future consideration

Customize Default Fields on Records - Renaming and Adding Descriptions

This applies to all records with required default fields, not just Features: I would like to be able to customize fields that are default/'out of the box' fields on records. Specifically, I would like to be able to rename and add descriptions (hov...
Ankar S over 3 years ago in Features 10 Future consideration

Inherit field values from Epics to Features

By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
Guest over 3 years ago in Features 7 Future consideration

Enhance approval API to allow approval group to be set

What is the challenge? Managing approvals across many features efficiently What is the impact? Without using approval groups we would need to update all feature's approvers each time someone joins or leaves an approving team Describe your idea I w...
Matthew Andrews 2 months ago in API / Features 0 Future consideration

Feature IDs should change when moved from one workspace to another.

What is the challenge? Feature IDs do not get updated when moved from one workspace to another What is the impact? it is confusing to know where it actually belongs Describe your idea when moving an idea to another workspace/release, update the ID
Mary Daul about 1 month ago in Features 0 Future consideration

Add a new status category

What is the challenge? Currently there is no way to have requirements update a feature's status when ALL requirements have a status in the category of In Progress. What is the impact? As we have multiple In progress statuses but do not always want...
Guest about 1 month ago in Features 0 Future consideration