Feature Requests

This feature allows users to seamlessly copy an action from one project to another within Hive, preserving all attachments, comments, and metadata associated with the action. This ensures that all critical information follows the task, supporting greater workflow consistency, transparency, and efficiency across projects. Expected Benefits: Increased Productivity: By eliminating the need to manually replicate action details, this feature saves time and reduces potential errors. Improved Project Continuity: Teams moving actions across projects retain the full scope of information, maintaining consistency and clarity. Enhanced Team Collaboration: By making attachments and comments readily available in new projects, cross-functional teams can collaborate more effectively without needing to switch between projects. This feature would be a valuable addition to Hive, making it easier to manage projects with full information continuity, thus enhancing team productivity and reducing friction when moving actions across different project scopes.

This will help users in organizing informations that are best formatted in Tables.

It would be great if Hive sent an email when an action card gets unblocked.

A dependent action's start and end dates should be updated as the predecessor task's is completed, so that the project and/or action cards adjust according to the delay / acceleration. For example, I have 3 tasks: Task A takes 5 days and is set with start / end dates of 2024-08-05 through 2024-08-09. Task B takes 3 days and cannot start until Task A is completed, so Hive automatically sets the start / end dates to 2024-08-12 through 2024-08-14 (because we're observing no work on weekends). Finally, Task C takes 2 days and cannot start until Task B is completed, so Hive automatically sets the start / end dates to 2024-08-15 through 2024-08-16. [Note, this is the existing, standard functionality]. Let's say Task A completes on 2024-08-14 (3 days late). Task B should have the start and end dates update to 2024-08-15 through 2024-08-19 (again, observing no work on weekends) and Task C should have the start and end dates update to 2024-08-20 through 2024-08-21. Similarly, let's say Task A completes on 2024-08-08 (1 day early). Task B should have the start and end dates updated to 2024-08-09 through 2024-08-18 and Task C should have the start and end dates update to 2024-08-19 through 2024-08-20. Like with the Dependency options of Off, On and Strict, this should be an option for users, as not everyone may want this feature. I could also see someone wanting a "rolling update", as in we pass the due date for Task A, so Task B and Task C have their start and end dates adjust accordingly. Note: I believe this is a duplicate of https://hiveteams.canny.io/feature-requests/p/set-dependent-due-date-based-on-predecessors-completion , but it's 2 years old, so not sure how visible it is. Also, it doesn't have an detailed description of the request.

copy and paste a sub action into a new action card.

Some of our teams have consistent subactions - would love to be able to create a dropdown list of commonly used subactions that we could have users choose from when adding a subaction to an Action Card.

When copying an action from one project to another it would save us time if it also copied labels and assignees. Otherwise we have to add in all of the labels and assignees again.

We can add links in the description or in custom fields. It would be nice to have a dedicated section in action cards for links.

As a project member, I can connect an action to a related action in another project so that both project teams can be aware of related actions. Ex: Team A launched the original iteration of a campaign landing page. Team B is now building a new version of the campaign landing pages. Team B wants to wants to connect their action card to the card with the work history from Team A so they have it as reference if needed. These actions are not dependent up one another, just related. This could expand on the dependencies function by adding others ways actions can be related. Including: Is dependent upon (or depends on) Is blocked by (or blocks) Relates to Is duplicated by (or duplicates) (this is from Jira issue linking)

It would be a huge time-saver and would help with overall productivity to be able to have more than one action card open side by side, so that you can work in both of them simultaneously. Right now, if I need to reference an existing action card when updating another action card, I have to keep switching between the cards or have to use screenshots. It’s very time consuming, inconvenient and unproductive, also leaves room for error.