Canonical page: https://tellenze.com/help/projects-teams

Organize Projects and Teams

Choose a work owner, manage access, organize labels, and understand settings and archival.

Choose the owner of the work

Open Work in the sidebar to browse Projects and Teams. Every work item belongs directly to one Project or one Team. A Project provides a home for a product, repository, service, or initiative. A Team groups people and can own both projects and work of its own.

For example, a website release can belong to the website Project, while a recurring support process belongs directly to the Support Team. Giving the Team ownership of the website Project grants its members collaboration access there without moving the project’s work into the Team.

Open Forms inside a Project or Team to manage its Custom Forms and collect public or workspace-only requests. Each accepted response creates a work item with the form's configured defaults. Responding does not give someone access to the destination or its other work.

Set up a project

1. Open Projects → New project.
2. Enter the project name and key. The key is 2–8 letters or numbers, begins with a letter, and becomes the permanent work-item prefix.
3. Add a description and colour. Optional fields include a portfolio group, website URL, repository URL, default branch, and Registry ID.
4. Choose visibility when private projects are enabled. Workspace is visible to active workspace members; Private restricts access to the people with a grant. The creator and active administrators retain access.
5. Choose Create project, then add work with New task.

Repository details provide project context; a separate repository connection may be needed for integration features. Portfolio groups organize the project directory. Renaming a group does not rename repositories or change project behavior. Administrators see Manage groups for maintaining the shared catalogue.

The repository and website icons sit beside the project title. Hover for the full address; website and HTTP(S) repository links open in a new tab. An SSH repository icon opens its address and default branch, with a selectable address to copy. Select the description beneath a project or team title to expand its full text.

Search the directory by name, key, or description. Star a project to add it to Favourites; the directory also has a Favourites filter.

Organize a team

Administrators can open Teams → New team, choose a permanent Team key, select members and owned projects, and assign a workflow or the workspace default. Existing teams use Settings for these controls. Ordinary members can collaborate in teams they can access; creating and managing teams requires an administrator.

Inside a Team, Work brings its direct work and accessible owned-project work together. Members shows people and owned projects; select a member's name or avatar to open their profile when available. Views contains shared saved filters and curated lists, with New team view and View all team views. Templates appears when available. New task creates work owned directly by that Team.

Team work refreshes automatically every 15 seconds while visible, and when you return to the tab. Filters, layout, and loaded pages stay in place. Updates pause while you are dragging, using a dialog, or saving changes, and retry automatically after a temporary failure.

Removing one access grant does not necessarily remove a person’s project access: they may still qualify through another owning Team, direct membership, workspace visibility, or their administrative role.

Use project navigation and settings

With project planning enabled, Work shows the current execution view, Backlog organizes planning and Focus groups, and All work offers broader inspection, including an Include archived control. Search, filters, list/board layouts, and configured workflow stages help narrow the view.

On project and team Work pages, Labels (when available) and Board / List sit to the right of the section tabs. On smaller screens these controls wrap below the tabs, which scroll horizontally. Search and expandable Filters stay directly above the work.

Other project sections include Documentation, plus Milestones, Insights, and Delivery when available. Their presence depends on linked data, enabled features, and integrations.

Use Settings → Project for editable project details. The creator and administrators can have additional Access, Workflow, Templates, Automations, and Required Context sections. Assigning a different workflow to a populated Project requires mapping the current stages; review every mapping before applying it.

Choose available work types

Workspace administrators use Admin → Work types to enable or disable the built-in types: Bug, Story, Task, Discovery, Incident, Business Case, Idea, Epic, and Feature. They can also create custom types with a name and icon, then rename or change the icon later. A custom type keeps the same underlying key when renamed, so existing work still uses it.

Project members with permission to edit project settings can use Settings → Work types to narrow the workspace list for that project. A project cannot enable a type that the workspace has disabled. At least one type must remain available for each active project. Team-owned work uses the workspace list.

Disabling a type prevents new work and type changes to that type. Existing work keeps its type and remains editable. When moving work to a project that does not allow its current type, choose an available destination type before completing the move. Conversion may clear fields that apply only to the previous type, such as Business Case details, Discovery timeboxes, or Bug and Incident severity.

Understand archival and missing controls

Project archival is administrative and removes the project and its work from active views while retaining recoverable history. Team administrators can Archive or Restore from the Team header. An archived Team freezes direct work and its shared Views; it does not revoke access to its owned projects.

If work is missing, clear filters and check archival and membership. A copied link grants no access. Missing settings can reflect permissions or disabled installation features; ask the project creator or an administrator to check the relevant access.