Plan a release
When you finish, a project has a release with a target date and the tasks that go in it. You can see what is left, and you mark it shipped when it goes out. It takes about five minutes. A release is a version you ship, like 1.4.0, with a list of tasks that go out in it.
Luka, Mira and Ivan are a three-person studio shipping a mobile app. They make a release called 1.4.0 with a target date at the end of the month. Each of them puts the tasks they own into it. Mira keeps a view of what is not done yet. When the build is live in the stores, Luka marks 1.4.0 shipped.
What you need
- A project with some tasks in it. Create epics, tasks and subtasks if you have none.
- An admin or owner to make the release and mark it shipped. Members can add their tasks to it.
Steps
1. Open Releases
Open the project and choose Releases. It is in the sidebar on a Mac, and in the bar at the top on a phone. A new project shows "No releases yet".
2. Make the release
Press New release and type a Release name, like 1.4.0. Pick a Target date if you have one, then press Create release. The release shows in the list. The one that ships soonest is marked Next up.
3. Add tasks to it
Open a task and set its Release field to 1.4.0. Do the same for each task that must ship. The task's history now says it was tagged for 1.4.0.
4. Check progress
Go back to Releases. The line under 1.4.0 shows how many of its tasks are done, like 3/8. It only counts tasks the app has loaded, so open the board first.
5. List what is left
Make a saved view with two conditions: Release is any of 1.4.0, and Status category is none of Done and Cancelled. Every task in it still needs work. Build a saved view shows how.
6. Mark it shipped
When the release goes out, press Mark shipped. It moves down under Already shipped, with the date it shipped. The next release moves up to Next up.
7. Reopen it if you need to
Marked it too soon? Press Reopen on the release. It goes back to the list of releases still to ship. This step is optional.
Check that it works
The release sits under Already shipped, marked Shipped, with the date. Its tasks keep the release on them. So a year from now you can still ask what went out in 1.4.0.
There are no sprints in devBoard. Small teams use releases instead. If you like short cycles, name a release Sprint 12 and give it a target date. The app's own example names are 1.4.0, Q3 launch and Sprint 12.
What to try next
- Admins can ask an assistant: "Make release 1.5.0 and add APP-42 to it." See connect devBoard to Claude Code.
- Link GitHub so each pull request shows on its task. A pull request is a code change that waits for review. The page on AI assistants and GitHub has the steps.
- Track how long each task took with time tracking.
- More guides for small teams.
If it does not work
| What you see | Why | What to do |
|---|---|---|
| No New release button | You are a member or guest | Ask an admin or the owner to make it |
| "This project has no releases yet." | No release exists in this project | Make one on Releases first |
| 1.4.0 is missing from a task's Release list | Releases belong to one project | Make the release in the task's project |
| The count reads 0/0, or looks low | It counts only tasks the app has loaded | Open the board, or use a saved view |
| Tasks lost their release | Someone deleted the release | The tasks are still there. Make the release again and add them back |
Questions people ask
Does devBoard have sprints?
No. Use a release instead. Name it Sprint 12 and give it a target date two weeks out. Add the tasks you plan to finish, and mark it shipped at the end.
Can a task be in two releases?
No. A task has one release at a time. If it slips, change its Release field to the next one.
Does devBoard write release notes?
No. A release is a name, a target date and the day it shipped. Keep your notes where you keep them now.
Free while in early access; paid plans will be one plain number, posted here first.
Download on the App Store Get it on Google Play Connect your AI assistant