Orangescrum
Documentation index for AI agents (llms.txt). A markdown version of this page is available at /project-templates.md or by requesting this URL with the header Accept: text/markdown.
8 templates

Project Templates That Set Up the Workflow

Pick a template when you create a project and it starts on the right status workflow and the right default view, so nobody has to configure a board before the first task goes on it.

Unlimited users Change the workflow later Cloud or self-hosted

What a Project Template Actually Does

A template is a saved project structure. Choosing one at project creation decides the set of statuses your work moves through, how work is grouped, and the view the project opens on, whether that is a task list, a board, or a backlog. Only the Agile template switches on sprints, story points, epics, burndown and velocity. The other seven differ from each other by their status workflow, not by hidden modules.

Nothing here is locked. Statuses can be added, renamed, or swapped for a different workflow after the project exists. And once you have a project set up the way you like it, you can save that project as your own template, which then carries its task lists, tasks, labels, task types, and workflow automation rules into every project made from it.

Pick One in Ten Seconds

All eight templates run the same product. The only real difference is where you start.

TemplateBest forOpens onStages
Agile ScrumProduct and engineering teams working in sprintsBacklog and active sprint4
Bug TrackingQA engineers, support engineers and developersBoard4
SimpleSmall teams and anyone running their first projectTask list4
KanbanAny team that works from a visual queueBoard4
Task TrackingOperations, admin and cross functional teamsBoard2
Content ManagementContent, marketing and communications teamsBoard5
RecruitmentHR and hiring managersBoard7
ProcurementPurchasing, finance and operations teamsBoard3

Project Template Questions

What is a project template in Orangescrum?
A project template is a saved project structure you reuse. When you create a project you pick a template, and the project starts with that template's status workflow and default view already in place, rather than with an empty board you have to configure first.
Do the built in templates create tasks for me?
No. The eight templates Orangescrum ships with set up the structure, which is the status workflow, the way work is grouped, and the view the project opens on. They arrive empty of content. A template you save from one of your own projects is different, and does carry its tasks across.
Can I change the workflow after I have picked a template?
Yes. Statuses are not locked to the template. You can add a status from the board or from the status workflow page, rename the ones you have, or switch the project to a different workflow at any point.
Can I save my own project as a template?
Yes. You can save an existing project as a template, or build one from a set of tasks. A template made this way carries its task lists, tasks with their story points and estimates, labels, task types, and workflow automation rules into every project created from it. That is how most teams end up with templates specific to their own work.
Which template should I pick if I am not sure?
Simple. It gives you one list and four statuses with nothing to configure, and you can move the project onto a different workflow later without starting again.
Are templates available on every plan?
Yes. Templates are part of project creation, and every Orangescrum plan includes unlimited users. Some of the capabilities a template pairs with, such as sprints or custom fields, sit on higher plans.

Start Your First Project

Create a project, pick a template, and start adding work. Unlimited users on every plan, and the workflow is yours to change.

14 day free trial. No credit card. Cloud or self-hosted.

Ready to transform your workflow?