Projects and workstreams
How projects and workstreams organize the work of standing up new services in Vigilis, and how templates, duplication, and archiving fit together.
Projects live at /projects, under Operations in the sidebar. Projects is part of the Projects add-on and is intended for organization admins, so depending on your plan and role you may not see it. If you expect it and it is missing, see Roles and permissions, ask an organization admin at your company, or ask your provider about the Projects add-on.
What a project is
A project is a top-level engagement, for example standing up service at a new site.
Each project breaks down into workstreams, which is where the actual task work lives. The usual pattern is one workstream per service, plus any standalone workstreams the engagement needs.
Templates, duplication, and archiving
- Templates. A template is a reusable checklist of task steps you apply to a workstream, so you are not rebuilding the same sequence of steps for every project.
- Duplication. Projects can be duplicated when a new engagement closely matches one you have already run.
- Archiving. Projects can be archived without losing their history.
How projects relate to tasks and comments
The individual action items inside a workstream are tasks, which everyone at your organization can see on /tasks. See Tasks and tickets.
When a service belongs to a project workstream, the service and the workstream share a single combined comment feed, so the full conversation appears on both pages. See Comments and notifications.
Common questions
What is the difference between a project and a workstream?
Can I reuse the same set of steps on every project?
What happens to a project's history when I archive it?
Still stuck?
If your Vigilis account is managed by an IT or telecom provider, they can resolve account and plan questions fastest. You can also reach us directly.