Feature Requests

In this use case, the team has a budget fields on the action cards as a custom field that shouldn't be visible to all team members. The request is to allow visibility permissions for specific action card custom fields to specific users.

When a user updates a Selction in the Custom Field, Hive creates a new value instead of updating the selection for existing custom fields.

Currently, it's possible to restrict it to project owner and Admins who can edit field values, but it would be helpful to set it to Admins only as well.

We can already do this using labels. But since labels are not limited to a particular project or user, labels(created for my project) show up in other projects where these labels doesn't make any sense and pollute the view there. So we need to either be able to create labels with project level visibility or use custom fields to assign color coding to actions. Having color coding helps in figuring out dev availabilities and dependancies in lengthy projects.

In the "custom fields" tab of settings, add a dropdown where you can select which projects each custom field appears in. Today, in order to add custom fields to projects, you need to go into the settings of each project and toggle on the fields you want to include. Having the ability to do this at a global level would help save time and cut down on this manual work.

We need to calculate our own project % completion based on custom fields and store the data on another custom field. It would be helpful if the custom fields can show the % sign. Thanks.

Users were able to double click on the child project's action card and edit the custom field while being at the parent project's table view. But now the user has to go into the child project, enable the custom field, then they can go to the parent project's table view and edit the child project's action's custom field by double clicking.

We have created custom fields to track bugs and releases. Ability to search and group these together will aid in narrowing issues or grouping them. Searching by date or date range without having to download Excel can aid in narrowing time frames if a bug is pushed.

Ability to have custom fields that only live on one action. Field should be easy to update across workspace and searchable / reportable.

For custom fields with multi-select turned on it could save time to have a select all button if there is a long list of options.