Use HiveAI with project work¶
HiveAI can use current project facts to help explain delivery work and prepare supported changes for review. A useful request identifies the project, the relevant item or milestone and the outcome you want. The project remains the authoritative record of the work; an answer, proposed change and completed action are different outcomes.
Availability: Project questions and controlled changes are implemented in the backend. HiveAI Final Screens show a shared conversation, exact-change review, expired/unavailable review and uncertain-outcome experience. These are the intended interaction patterns. The connected interface and deployment have not been verified, and the project-specific selection and result screens still need reconciliation. This guide explains the supported capability and the inspected shared journey without promising that every action is available in your environment.
Before you begin¶
You need access to HiveAI and the relevant project permissions in your workspace. Reading project facts and changing projects require different authority. Repository changes and formal governance requests also have their own permissions. Being named in a conversation, being a project participant or receiving an AI suggestion does not grant those permissions.
Project questions use Basic capability. Preparing and carrying out project changes uses Advanced capability and the rules for reviewed changes. Availability also depends on current workspace entitlements, permissions, policy and the wider HiveAI controls described in HiveAI access. Those controls must be satisfied when work is performed; a previously visible button does not guarantee continuing access.
The tools use the workspace's prepaid-credit charging scope. This is not a fixed price for a question or a guarantee that an action attempt is free. Treat any visible estimate, reservation and actual usage as different values. Sample costs in a design are not a price list.
Ask about current project facts¶
The implemented read capabilities include:
| Area | What the assistant can obtain | What to check |
|---|---|---|
| Portfolio and setup | Project discovery, current portfolio counts, supported status/delivery choices and project detail | Confirm the project reference; a short result is not a complete portfolio |
| Execution | Sprint/phase groups and work items, assignment, progress, review and evidence summaries | Open the item before relying on a summary for a delivery decision |
| Governance | Milestone criteria, deliverables and saved formal-review links | Criteria met, review requested and approved remain different states |
| Repositories | Linked repositories, provider availability, repository and branch discovery | Available metadata does not prove healthy synchronization or accepted evidence |
| Reports | Selected current report measures and report-history observations | Apply the count, freshness and history limits in the report guide |
For example, “Explain the blocked work in project PROJ-EXAMPLE” is more useful than “How is everything going?” Use actual project references in your workspace; the example is illustrative, not a supplied record or a guarantee of intent recognition.
Several answers use a limited selection rather than every record. Execution information can include groups before work items, so a large group list can leave fewer items in the answer. The list of possible subjects for a formal review may also omit further choices without showing a partial-results warning. Absence from a response therefore does not prove that a work item, deliverable or milestone does not exist. Narrow the question or inspect the project directly when completeness matters.
A read does not mutate the project. A report summary does not supply every chart and breakdown, and a historical observation can reflect later changes to the underlying records. Check the source and observation context before using an answer for a formal review or executive report.
Understand the separate due-work view¶
The due-project-activity capability returns dated execution items and milestone gates from projects you own or participate in. It does not include every item merely because it is assigned to you, and it does not include work with no due date. It is not the same population as a general project search.
The view includes selected unfinished work states and unapproved milestone states. A completed or cancelled parent project is not separately filtered out by this query, so unfinished child work may still appear. Investigate the project and item state instead of assuming that their appearance means the whole project remains active.
The selected time window and “overdue” label answer different questions. The overdue selection compares the due date with the beginning of the requested window, while the returned urgency label compares it with the current time. A historical window can therefore contain an item selected as due that is overdue now. The active selection includes eligible dated work up to the window end, including older overdue work; it is not limited to items whose status is In progress.
This read can provide further pages. A partial result needs its continuation before it can support a complete count. Its freshness value can come from a due, assignment, review-ready or milestone-achievement time; it is not a universal last-edited time. The intended user-friendly route back to each source still needs frontend verification.
Prepare a supported change¶
The implemented project actions cover the following changes, subject to the review process:
| Change family | Supported requests |
|---|---|
| Project setup and lifecycle | Create a draft, update setup, activate, hold, complete or cancel |
| Delivery organization | Create or update a sprint/phase; create, update, assign or move a work item |
| Work execution and review | Start, block, submit for review, complete, approve or reject review, reopen, configure or reevaluate completion requirements |
| Milestones and outputs | Create/update/evaluate a milestone; add a deliverable; request a formal governance workflow |
| Repository evidence | Link/update/unlink a repository, request synchronization, attribute/remove attribution or record evidence acceptance |
| Shared work | Record a dependency resolution or shared-delivery result |
These actions retain the ordinary project restrictions. A repository that cannot be unlinked through the ordinary rule remains blocked. Completing a project does not certify all its children as complete. Resolving a dependency and recording shared delivery do not themselves complete an item or approve an output. Use the corresponding execution, governance, repository and shared-delivery guides for those rules.
Be explicit about the target and desired values. Some changes replace settings or apply defaults to omitted fields; they are not always “change only what I mentioned.” Review dates, assignment, progress, completion requirements, recipients and proof before deciding. The exact project-specific form of that review remains implementation and design follow-up.
Follow the intended review journey¶
- Enter HiveAI through the access journey and start or continue the relevant conversation.
- Describe the project and requested change. Resolve an ambiguous target before proceeding; do not approve a proposal for a similarly named item.
- Read Review this change. The inspected shared screen shows the current value, proposed value and a review deadline. Confirm that the displayed target, responsibility and consequences match your intention.
- Select Approve change only for that exact proposal, or Reject change if it is wrong or no longer needed. These labels are verified in the shared HiveAI design; project-specific field selection and confirmation companions have not all been verified.
- Wait for the action outcome and inspect the underlying project record. Approval is permission to attempt the prepared change; it is not proof of completion, synchronization, formal acceptance or successful downstream delivery.
If the review says Review unavailable or Review expired, use the intended Refresh review control before requesting another proposal. The inspected design states that refreshing the saved review does not start a new change. Recheck the resulting proposal; do not assume that an earlier decision carries over to changed data.
The system checks whether the project has changed, but this is not a complete safeguard against every edit to its individual work items. Passing preview checks does not guarantee that the change will pass every business rule when it runs. Keep the underlying record open for consequential changes and verify the final saved values.
Recover from an uncertain result¶
The shared conversation design includes Checking the outcome and explains that some steps may already be complete. If the connection is interrupted or an action returns an unclear result, avoid creating the same change again immediately. Check the saved action status and inspect the project first; support can investigate a pending, confirmed or unavailable result.
A processed request can still report a rejected outcome. A failure after saving or while retrieving the updated record can also leave uncertainty about what changed. Read the action's result and check the project itself; a generic error or saved result alone does not prove that no work occurred or that every follow-up step completed.
A general Undo action has not been verified for project changes. A correction may need a new authorized change and the target must still permit it. Do not infer undo support from another HiveAI action's example.
For help, retain the conversation, project reference, requested action, target item, approximate time and visible message. Keep sensitive project content inside your organization's approved support channel. Administrators should check current access and policy; support should reconcile action status and saved project state before recommending a retry.
Managers remain responsible for delivery decisions and approvals. Executives can use sourced answers to identify questions and exceptions, but bounded reads and AI-generated explanations do not establish full portfolio coverage, individual productivity or realized business value.