What you can do with pulpForge
- Organise a backlog. Epics, features, stories, tasks and bugs in a tree, drag-and-drop ordering, quick keyboard entry (Enter for a sibling, Tab for a child), total points and remaining work on every parent.
- Follow progress on a board. Columns by state category, lanes by person or parent, work-in-progress limits, workflows you can customise per type.
- Plan sprints. Capacity per person, a load gauge that turns red when over-committed, ideal and actual burndown.
- Link the code. Add a repository address, import a Git log: commits and branches attach to items, and “Fixes PRJ-3” proposes closing the item, never without your approval.
- Follow tests. Import a JUnit report: pass rate per build, and a button to create the bug for a failing test.
- Bring your tickets over. Import Jira exports (CSV and XML), Azure DevOps, GitHub and GitLab, with mappings proposed automatically. An import adds and never replaces without asking.
- Export. CSV in Jira or Azure DevOps format, GitHub-style JSON, release notes in Markdown, full
.pforgebackup. - Get help. Type and priority suggested from the title, likely duplicates, an estimate from similar items, a sprint summary: all computed on the device.
Who is it for?
pulpForge is for small development teams, freelancers and technical leads who want solid tracking without hosting a tool or creating an account, and for anyone moving from one tool to another who wants to keep their history.
Your projects stay on your device, and the app works offline once loaded. Sharing with a team goes through a synced folder, a phone or a guest; real-time editing and per-person permissions will come later with the pulpSuite server.
Your files
pulpForge saves as .pforge (an archive holding all projects, their history and attachments). It reads Jira CSV and XML exports, Azure DevOps query CSVs (flat or tree), GitHub and GitLab JSON issues, Git logs and JUnit XML reports.
Frequently asked questions
Is pulpForge an alternative to Jira?
For tracking work items, sprints, repositories and tests at the scale of a small team, yes. It does not replace the permissions, notifications and integrations of a hosted service: those will come later with the pulpSuite server.
How do I bring over my Jira tickets?
In Jira, export the issue view as CSV (all fields) or XML, then drop the file into the import wizard of pulpForge. Numbers (PRJ-12), parents, sprints, labels, estimates and links are carried over. The formats detail lists what is read.
Are my tickets sent to a server?
No. Everything is read and stored in your browser. Only the requests you make to pulpAssist go through the configured assistant gateway.
Does pulpForge connect to GitHub or GitLab?
Not in this version: it reads files you give it and never contacts your repositories. Connectors will come later with the pulpSuite server.