LoginSign Up
← Back to all sparks
Hive logo

Hive

COLLABPM
Velocity10.0

Project management and collaboration platform

hive.com ↗

Governance and cross-workspace plumbing, not new AI surface

approvalsjira-syncresourcingadmin-controlsnotifications
◆Current state
August's batch is administrative: approval rounds and stages can be locked against edits, action cards can hide apps and areas per action, and status libraries filter by project. Managed Jira actions now move through transitions from List View with Jira still the source of truth. My Actions spans workspaces, and notifications carry comments and reactions.
◆Where it's heading
Hive is hardening what it already shipped rather than opening new ground. Permissions around approvals, less clutter on action cards, and tighter two-way Jira sync all read as preparation for larger multi-team deployments, where a workflow has to survive many editors. The AI work that dominated July — Buzz sub-tasks, AI Proofing — is absent from this window.
◆Prediction
Expect more admin-scoped controls around approvals and templates, plus continued Jira parity work; on the evidence here the next Buzz change is likelier to be scoping and permissions than a new capability.

◆Recent moves

  1. 2d ago

    Group Resourcing assignments by project

    The Resourcing Users view can group assignment rows by project name instead of scattering a person's work across the view. A small but real reporting change for resource managers.

    View source ↗
  2. 2d ago

    Move Jira statuses straight from Hive List View

    Managed Jira actions can be advanced through Jira transitions from the status cell in List View, without opening each card. Manually linked issues stay read-only, so Jira remains the source of truth.

    View source ↗
  3. 2d ago

    Choose which apps and areas appear on each action card

    Action cards can show a different set of apps and areas per action, with subactions and templates inheriting the choice. Configuration depth for teams running several distinct workflows in one workspace.

    View source ↗
  4. 2d ago

    Lock approval rounds and stages against edits

    Approval rounds and stages can be locked so users without permission cannot restructure them, and the interface explains who can. It is the clearest example of the governance theme running through this batch.

    View source ↗
  5. 6d ago

    Polish Tables grid interactions and alignment

    Interaction and alignment polish for the Tables grid, with no change to what Tables can do. Cosmetic follow-through on the module Hive recently wired into Forms as a data source.

    View source ↗
  6. 6d ago

    Show planned dates alongside actions in dashboards

    Dashboards can display planned dates next to the actions themselves, so scheduling context arrives without a trip to a Gantt or calendar view. Modest on its own, and consistent with the batch's habit of pulling adjacent context into the surface a team already has open.

    View source ↗