Import, create, and review backlog work
Create supported backlog items from CSV, Markdown, a guided hierarchy, or generated proposals.
ScrumPulse provides three related workflows: Import Backlog, New Backlog, and Backlog Review.
Required permissions:
work_items:managefor Import Backlog and New Backlog.backlog:managefor proposal decisions in Backlog Review.
Administrators, Managers, and Product Managers receive both permissions by default.
Import a backlog file#
- Open Import Backlog.
- Select the board type and enter the project key or ID.
- Choose file upload or pasted content.
- Provide CSV or Markdown content.
- Review the parsed preview.
- Submit the import.
- Review Import Results for created and failed counts.
The API accepts supported item types and routes creation through the provider integration. Validate a small sample in dry-run or a non-production project before importing a large backlog.
CSV shape#
The importer recognizes fields used by the repository’s parser, including item type, title, description, tags, and parent title. Use descriptive placeholders and save the file as UTF-8.
type,title,description,tags,parent_title
epic,Platform reliability,Improve operational resilience,"platform,reliability",
story,Add readiness monitoring,Expose a safe readiness check,observability,Platform reliability
task,Document alert ownership,Name the responding team,operations,Add readiness monitoring
Create a backlog in the browser#
- Open New Backlog.
- Select Jira or Taiga and enter Project Key/ID.
- Add an epic title and optional description.
- Add stories beneath the epic.
- Add tasks beneath each story.
- Select Create All.
- Review the created and failed counts.
The form creates the hierarchy in one request. A partial result can include both successful items and errors; verify the provider board before retrying so you do not duplicate successful items.
Review generated proposals#
- Open Backlog Review.
- Filter proposals by state.
- Select one or several proposals.
- Choose Approve, Reject, or Defer.
Decisions are locked after they reach a terminal state. Approval records a decision; whether a proposal becomes a live provider item depends on the execution path and safety configuration.