2 column layout for custom fields on the flyout that comes up for features, master features etc.
When we open features or master features, on the flyout, the system fields are all shown in a 2 column layout but for the custom fields, only 1 field is shown per row. It would be good to see these also in a two column layout
Arun Kalyanaraman
over 4 years ago
in Features
1
Future consideration
Option to reflect Prioritization Rank in other areas of the platform
Who would benefit? Product Managers using Prioritization functionality as well as the feature board What impact would it make? It would reduce the time and administrative burden with feature prioritization while improving consistency across the pl...
Claire A
about 1 year ago
in Features
1
Already exists
We want to add a dependency type to show that a dependency is no longer needed. Unfortunately, we sometimes create dependencies on other product Roadmaps but then are unable to contact the owner to remove the dependency.
As a solution, we though...
I've recently started to use requirements within features more - and see them as a good way to clear a lot of unnecessary detail from feature overviews / reports. However to change a large number of features into requirements is a slow one-by-one ...
Guest
about 9 years ago
in Features
4
Already exists
Don't Default Time Estimates to Reflect Start on and Due on Dates When Feature is displayed on the Releases Roadmap View
If you try to clear a feature estimate and the feature is already added to the roadmap, then it fills in the value of the estimate duration automatically to reflect the start on and due on dates. This means that if you try to plan a release and th...
Matt Case
about 9 years ago
in Features
1
Already exists
Automatic adding features to a release phase based on the feature type
We actually recieve many features through the Import from Jira. When I move this features from the parking lot to a release, they are usually not assigned to a release phase and I have to move them to the desired phase in the release gant.As we ha...
Waldemar Vierheilig
over 5 years ago
in Features
2
Future consideration
Automatically create new copy features in other workspaces based on feature tags
Who would benefit? Any product owner that has multiple workspaces or multiple tiers of workspaces. What impact would it make? Reduce the amount of work by creating tickets once instead of copying and moving. Further, changes in the feature in one ...
Guest
about 1 year ago
in Features
1
Unlikely to implement
Create Folders in the "attach documents" section on each project
Hi, I'm a big one for attaching documents to my projects. Some projects are starting to look a little messy now with the number of files attached. It would be good to be able to create folders to store the files in i.e. a folder for gate 1 and ano...
Guest
about 9 years ago
in Features
1
Will not implement
Capacity for teams: Bulk change how estimates are calculated
This idea relates to capacity planning for teams. You currently have to manually set initiatives or master features to compute from a child record. It would be so great if we could make this change in bulk.
Show related or dependent features indented beneath parent feature in Features Board
Hi there,
Like many, we are trying to find the right balance of granularity and manageability for our features. Managing the roadmap and backlog is much easier with multiple features than with the requirements under a feature, since the requiremen...
Guest
about 9 years ago
in Features
1
Unlikely to implement