Vetrix Docs

Project configuration

The Project Configuration pages define the building blocks that every repository's issues share across the instance: the issue types that categorize issues, the workflows that describe the states an issue moves through and the transitions between them, and the link types that describe typed relationships between issues. You manage each of these as an administrator, and the choices you make here become available for repositories to adopt. This page covers all three.

Where to find it

Open your avatar menu in the top navigation bar and select Admin panel, or go to gitvetrix.com/admin directly. In the admin sidebar, under Project Configuration, select one of:

  • Issue Types — the instance-wide catalog of issue types.
  • Workflows — the state-and-transition definitions.
  • Link Types — the typed relationships between issues.

URL patterns: gitvetrix.com/admin/issue-types, gitvetrix.com/admin/workflows, and gitvetrix.com/admin/link-types.

Issue types

The Global Issue Types page lists every issue type defined for the instance and lets you create, edit, and delete them. Repositories draw on this catalog when they build their own issue type schemes.

Read the issue type list

Each row shows a colour swatch, the type rendered as a coloured badge using its display name and colour, its slug in a monospaced font, a sub-task marker when the type is a sub-task type, and its position as pos followed by a number. Every row has Edit and Delete controls on the right. When no types exist yet, the page shows No issue types with the note "Create issue types to categorise issues in your repositories."

Create an issue type

  1. Select New issue type. A New issue type form opens at the top of the page.
  2. In Name (slug — immutable after create), type a lowercase identifier such as bug, task, or story. Only letters, numbers, hyphens, and underscores are allowed, and the slug cannot be changed later.
  3. In Display name, type the label shown to users, such as Bug or Task.
  4. Optionally, add a Description.
  5. Choose a Colour: select one of the preset swatches, or type a six-character hex value in the field beside the # prefix. A preview badge shows the type as it will appear.
  6. Optionally, fill in Icon (optional name or URL) with an icon name such as bug or star, and turn on Sub-task type (cannot have children) if this type should only ever be a sub-task.
  7. Select Create issue type to save it, or Cancel to discard the form.

Edit an issue type

  1. Find the type in the list and select Edit. The row turns into a form pre-filled with the type's current values. The slug cannot be changed, so the Name field is not shown.
  2. Change the Display name, Description, Colour, Icon, or Sub-task type setting as needed.
  3. Select Update issue type to save your changes, or Cancel to leave the type unchanged.

Delete an issue type

  1. Find the type in the list and select Delete.
  2. In the Delete issue type dialog, read the warning: "This issue type will be permanently deleted. This will fail if any issues still use this type."
  3. Select Delete issue type to confirm, or close the dialog to keep it.

If any issues still use the type, the deletion is blocked and a persistent alert appears at the top of the page, headed Delete blocked — "" is in use and naming the reason. The alert stays until you select Dismiss. Remove the type from the issues that use it, then try again.

Workflows

The Workflows page lists every workflow defined for the instance. A workflow is a named set of states an issue can occupy and the transitions that move an issue between them. Repositories assign a workflow to govern how their issues progress.

Read the workflow list

Each row shows the workflow name as a link, its description when it has one, and a count such as 3 states. Each row has an Edit link and a Delete control. When no workflows exist yet, the page shows No workflows with the note "Create a workflow to define the states and transitions for your issues." and a Create first workflow button.

Create a workflow

  1. Select New workflow. A New workflow form opens at the top of the page.
  2. In Name, type a name such as Development Process.
  3. Optionally, add a Description.
  4. Select Create workflow to save it, or Cancel to discard the form.

The new workflow starts with no states; open it to add them.

Open and rename a workflow

Select a workflow's name, or its Edit link, to open its editor. The editor opens with a breadcrumb of Admin and Workflows, the workflow name, and its description.

To rename the workflow, select its name, type the new name, and select Save, or select Cancel to keep the current name.

Add and edit states

The States row shows each state as a badge coloured by its category. A star marks the workflow's initial state and a lock marks a terminal state. Select a state to open its edit panel on the right. When a workflow has no states, the editor reads "No states yet. Add a state below."

To add a state:

  1. Select + Add state. An Add state form opens below the graph.
  2. In Name, type the state name, such as In Review.
  3. Choose a Category — To Do, In Progress, or Done.
  4. Turn on Initial to make it the starting state, or Terminal to mark it as an end state.
  5. Select Add state to save it, or Cancel to discard the form.

To edit a state, select it and use the Edit state panel to change its Name, Category, Initial state, or Terminal state, then select Save. To remove it, select Delete state and confirm in the Delete state dialog. A state that still has issues in it cannot be deleted, and a message notes that issues are in this state.

Add and edit transitions

Below the states, each transition appears as a labelled connector showing its name and the states it links. The Transitions list further down repeats them as rows, each showing the transition name, the states it moves between, a Rules link, and an Edit control.

To add a transition:

  1. Select + Add transition. An Add transition form opens. (This button is unavailable until the workflow has at least one state.)
  2. In Name, type the transition name, such as Start Progress.
  3. Choose a From state, or leave it as Any state to allow the transition from any state.
  4. Choose a To state.
  5. Select Add transition to save it, or Cancel to discard the form.

To edit a transition, select it and use the Edit transition panel to change its Name, From state, or To state, then select Save. To remove it, select Delete transition and confirm.

Set transition rules

Each transition can carry rules that govern when and how it runs. On a transition row in the Transitions list, select Rules to open its rules editor, titled Rules: followed by the transition name. Use ← Back to workflow to return. The editor has three sections, each with an Add button; every rule you add appears as a row with a control to remove it.

  • Conditions decide who may run the transition. Available types are Minimum role, Any of roles, Caller is assignee, and Caller is reporter. The role choices are Read, Triage, Write, Maintain, and Admin. With no conditions, the section notes that anyone may execute the transition.
  • Validators require the issue's fields to be complete before the transition runs. Available types are Required field, Field value constraint, No open child issues, and Not blocked by open issues. A required-field or field-value rule lets you pick fields such as Assignee, Milestone, Priority, Due date, or Components.
  • Post-functions run actions automatically after the transition. Available types are Assign to current user, Assign to reporter, Clear assignee, Set priority, Set due date, Close child issues, Add comment, Notify watchers, and Trigger webhook. Each post-function has a Position (execution order) value, and lower positions run first.

To add a rule, select Add condition, Add validator, or Add post-function, choose a Type, fill in any fields that appear for that type, and select the matching add button. Post-functions can also be edited later from the pencil control on their row; a post-function's type cannot be changed once created.

The Link types page lists the typed relationships you can create between issues, such as "blocks" or "relates to", and lets you add and remove them.

Each row shows a Symmetric or Directed badge, the link type's name, and its Inward and Outward wording. For a symmetric type, the outward wording reads "same as inward". Each row has a Delete control. When no link types exist yet, the page shows No link types with the note "Create a link type to define typed relationships between issues." and an Add first link type button.

  1. Select Add link type. An Add link type form opens.
  2. In Name, type the relationship name, such as blocks.
  3. In Inward name, type the wording used when this issue is the target, such as is blocked by.
  4. In Outward name, type the wording used when this issue is the source, such as blocks.
  5. To make the relationship read the same in both directions, turn on Symmetric. The Outward name field is hidden while Symmetric is on, and the inward wording is used for both directions.
  6. Select Create link type to save it, or Cancel to discard the form.
  1. Find the link type in the list and select Delete.
  2. In the Delete link type dialog, read the warning, then select the confirm button, which names the type.

If the link type is still in use by any issue links, the deletion is blocked and a persistent alert appears, headed Delete blocked — "" is in use. The alert stays until you select Dismiss. Remove the links that use the type, then try again.