Module switches

Per project

Open a project, Project settings, Modules. Each module has a description and a switch. Modules are chosen per project, so one space can hold a Scrum team and a support desk side by side.

• A blank project starts with Board and Releases on; a project made from a template starts with the modules chosen while it is created
• In a blank project Sprints, Time tracking, Acceptance Certificate, Gantt, Calendar, Documents, Testing, Security levels, Risks, Check-ins and Google Drive start off; Acceptance Certificate works only on top of Time tracking
• A Scrum project always has Sprints; its type decides
• A Help Desk project does not offer Sprints, Gantt, Releases, Testing, Risks or Check-ins at all

The Visible button on a switched-on module takes it out of the tabs for a while without switching it off; the button then reads Hidden.

Off means off

A switched-off module has no tab, no screens and no API. Requests to its addresses answer 404, not 403, so an old link or bookmark reveals nothing about what exists. Permissions of a switched-off module do not appear on the project's Permissions screen either.

Not modules

• Help Desk is a project type, chosen when the project is created
• Automation is a tab of the space
• Git hosting (GitLab, GitHub, Bitbucket) is connected under Administration, Integrations, for the whole system

Typical combinations

• Development team (Scrum): sprints, board, releases, testing, documents
• Operations or support: a Help Desk project with SLA policies, plus automation in its space
• Management office: Gantt, calendar, risks, check-ins and documents