Quick start
Sign in, connect a Taiga or Jira project, and complete your first safe dry run.
This guide uses the hosted dashboard and keeps the first run in dry-run mode.
Before you begin#
You need:
- A ScrumPulse account with access to a Clerk organization.
- A Taiga or Jira base URL.
- A project key, slug, or ID.
- An API token that can read the target project.
- The
integrations:managepermission to connect the board. - The
runs:triggerpermission to start the first run.
Use the least-privileged board token that supports the workflows you plan to run. Do not paste credentials into support messages or documentation.
1. Create an account or sign in#
- Open the ScrumPulse dashboard.
- Select Start free to create an account, or Sign in if you already have one.
- Complete the Clerk-hosted authentication flow.
- Select or join the correct Clerk organization if prompted.
You should arrive at Overview. New organizations see the Welcome to ScrumPulse setup wizard.
If the setup controls are read-only, ask an organization administrator for the required permissions. Administrators can assign an operational role or a narrowly delegated permission under Settings → Access & Roles.
2. Connect a board#
- In step 1 of the wizard, select Taiga or Jira under Board Type.
- Enter the Base URL.
- Enter the Project Key / Slug.
- Enter the API Token.
- Select Test Connection.
Expected result: the wizard reports Connected to <project name>.
If the test fails, confirm the provider URL format, token scope, and project identifier. See Integration troubleshooting.
3. Select cycles and safety mode#
- Continue to Enable Cycles.
- Select only the cycles you want to evaluate.
- Choose Dry run.
- Review the summary and select Finish Setup.
Free workspaces remain in dry-run mode. Live mode is available only when the workspace plan allows it.
4. Run the agent#
- From Overview, select Run Agent Now.
- In Select Cycles to Run, confirm the cycle selection.
- Start the run and wait for the live status modal to finish.
- Open the new item under Recent Runs.
Expected result: the run is marked as a dry run and shows cycle summaries without applying board writes.
5. Review the result#
- Open the run’s Action Log.
- Review proposed actions and before/after context.
- Open Approvals if the run created approval requests.
- Download a CSV or PDF if you need an offline review artifact.
Do not enable live mode until the proposed actions, project scope, action cap, and confirmation threshold match your operating policy.