SetGet Docs

English

Türkçe

English

Türkçe

Appearance

Create a Project ​

Projects are where work happens in SetGet. A project contains work items, cycles, modules, views, and pages — all scoped to a specific area of your team's responsibility. This tutorial walks you through creating a project, choosing a meaningful identifier, setting up workflow states and labels, and enabling the features your team needs.

Prerequisites ​

  • An existing SetGet workspace with at least one member. See Create a Workspace and Invite Members if you have not completed those steps.
  • Admin or Member role in the workspace.

Step 1: Start creating a project ​

There are two ways to begin:

From the sidebar:

  1. Hover over the Projects section in the sidebar.
  2. Click the + icon that appears.

From the projects page:

  1. Click Projects in the sidebar to open the projects list.
  2. Click the Create Project button.

Both methods open the project creation dialog.

Step 2: Choose a project name ​

Enter a clear, descriptive name for your project. This is what your team will see in the sidebar, breadcrumbs, and throughout the interface.

Naming tips:

  • Use the product, team, or domain name (e.g., "Mobile App", "Backend Services", "Marketing Site").
  • Keep names concise. Long names get truncated in the sidebar.
  • Avoid abbreviations that only some team members understand.

Step 3: Set the project identifier ​

The project identifier is a short uppercase code (typically 2-5 characters) that prefixes every work item in the project. For example, if your identifier is MOB, work items will be numbered MOB-1, MOB-2, MOB-3, and so on.

SetGet suggests an identifier based on your project name, but you can change it to anything you prefer.

Identifier rules:

  • Must be unique within the workspace.
  • Uppercase letters and numbers only.
  • Between 1 and 5 characters.
  • Cannot be changed after creation.

WARNING

Choose your identifier carefully. Once a project is created, the identifier is permanent. All existing work item references (in comments, links, and external tools) depend on it staying consistent.

Good identifier examples:

Project nameIdentifier
Mobile AppMOB
Backend ServicesBE
Marketing SiteMKT
Design SystemDS
Customer SupportCS

Step 4: Add a description (optional) ​

You can add a brief description to explain the project's purpose. This is visible on the project settings page and helps new team members understand the scope.

Step 5: Set the network (optional) ​

Choose the project's visibility:

  • Workspace-visible — All workspace members can see and access the project. This is the default and the most common choice.
  • Secret — Only members explicitly added to the project can see it. Use this for sensitive or confidential work.

Step 6: Choose a cover image and emoji (optional) ​

Personalize your project with:

  • Cover image — A banner image displayed at the top of the project page. You can upload your own or choose from the built-in gallery.
  • Emoji — An icon displayed next to the project name in the sidebar and breadcrumbs. Helps with quick visual identification when you have many projects.

Step 7: Create the project ​

Click Create Project. SetGet creates the project with a default set of workflow states and redirects you to the project's work items view.

Step 8: Configure workflow states ​

Every work item in a project has a state that reflects where it is in your workflow. SetGet creates a default set of states grouped into five categories:

GroupDefault stateMeaning
BacklogBacklogWork acknowledged but not yet scheduled
UnstartedTodoScheduled but not yet in progress
StartedIn ProgressActively being worked on
CompletedDoneWork finished successfully
CancelledCancelledWork abandoned or no longer relevant

To customize states:

  1. Go to Project Settings (click the gear icon in the project header or navigate via Settings > Projects > [Your Project]).
  2. Click the States tab.
  3. You can:
    • Rename any state by clicking on its name.
    • Add new states within any group by clicking the + button next to the group name.
    • Reorder states by dragging them within their group.
    • Delete states that you do not need (work items in a deleted state are moved to the group's default).
    • Change colors to match your team's visual conventions.

TIP

Keep your state list short and meaningful. Most teams work well with 4-7 states. Too many states create confusion about where a work item should be.

Step 9: Configure labels ​

Labels let you tag work items with cross-cutting categories like "bug", "feature", "documentation", "tech-debt", or "design". Unlike states, a work item can have multiple labels.

To manage labels:

  1. In project settings, click the Labels tab.
  2. Click Create Label to add a new label.
  3. Choose a name and color for the label.
  4. Repeat for each label your team needs.

Labels can also be created on the fly when editing a work item — you do not need to define them all upfront.

Step 10: Configure estimates (optional) ​

If your team uses estimation, enable it in project settings:

  1. Go to the Estimates tab in project settings.
  2. Enable the estimation system.
  3. Choose a scale: points, t-shirt sizes (XS, S, M, L, XL), or custom values.

Once enabled, every work item in the project gains an estimate field.

Step 11: Add project members ​

By default, if the project is workspace-visible, all workspace members can access it. For secret projects, you need to add members explicitly:

  1. In project settings, click the Members tab.
  2. Click Add Member and search for workspace members.
  3. Add each person who should have access.

Project membership also determines who appears in the assignee picker when creating work items.

Step 12: Enable project features ​

Each project can independently toggle certain features:

  • Cycles — Time-boxed iterations for sprint planning.
  • Modules — Group related work items by feature or theme.
  • Pages — Project-scoped documentation and wiki pages.

Navigate to project settings and toggle each feature based on your team's needs. Disabled features are hidden from the project sidebar, keeping the interface clean.

Tips ​

  • Start with defaults, then refine. The default states and empty label list are fine for getting started. Add customization as your team's workflow becomes clearer.
  • Use consistent identifiers across projects. If your organization has naming conventions for project codes, follow them in SetGet too.
  • Create one project per logical area. Avoid putting unrelated work in the same project. It becomes hard to filter and report on.
  • Review settings after a few sprints. Once your team has used the project for a cycle or two, revisit states, labels, and estimates to see if adjustments are needed.