Understand Project Statuses and Workflows

Statuses & Workflows

Beginner

Understand how work moves through AlphaTales statuses and workflows, so teams can track progress clearly and know what planning step should happen next.

What you’ll learn

Know every feature status and what it means
Understand how feature work moves between statuses
Follow the typical workflow from idea to done

Overview

AlphaTales uses statuses to track feature work throughout your project. Understanding these statuses helps you organize work, communicate progress with your team, and move items through a clear workflow.

Feature Statuses

Features represent the building blocks of your product. Each feature has one of the following statuses:

Todo - The feature is defined but work has not started. This is the default status for newly created features.
In Progress - Active work is happening on this feature.
Done - The feature is fully implemented and all associated work is complete.
Cancelled - The feature has been removed from scope. It remains visible for reference but is no longer active.

Tip: Features created by AI start in a suggested state. Once you review and accept them, they move to Todo.

Additional Feature States

When features are generated by AI or managed through validation, you may also see these states:

Suggested - Proposed by AI, awaiting your review
Added - Accepted and added to the project scope
Locked - Finalized during validation and cannot be edited without unlocking

Typical Feature Workflow

The most common path is:

Suggested - AlphaTales proposes feature work.
Added - You review and accept the work into scope.
Todo - The feature is ready to start.
In Progress - Work is active.
Done - The feature is complete.

Not every feature follows every step. Manually added features may start in Todo, and cancelled work may skip the rest of the flow.

Changing Statuses

You can update status from feature details or from the Task Board when your role allows it.

Use statuses to communicate the real state of work. Avoid marking a feature Done until the team agrees the expected behavior is complete.

Empty Or Loading States

If the Task Board is empty, create or generate features first. If a status column is empty, it means no current feature work is in that state.

If features are still loading or generation is still running, wait for the page to finish before changing statuses.

Failed Or Blocked Changes

If a status change fails, refresh the page and try again. If the change still fails, confirm your project access and role.

If plan limits, credit limits, or permissions block the next step, ask the project owner or admin to update access, resolve billing, or continue after credits are available.

Next Steps

Now that you understand statuses, use the Task Board to review feature work or open a feature to manage its details.