MokoGIT: Custom Issue Statuses, Priorities & Types

Details
Category: Guides
  • Applicable Software: MokoGIT
  • Min Version Number: 02.00.00
  • Max Version Number: Not Applicable

Custom Statuses

  • Each org defines its own issue statuses (for example In Progress, Blocked, Pending: Review, Resolved), each with a color and a closes-issue flag - applying a closes-issue status closes the issue.
  • Presets seed a standard status set into an org in one step, and a protected baseline keeps core statuses from being removed.

Priorities

  • Org-defined priorities (for example Critical / High / Medium / Low), each with a color; one is marked the default applied to new issues.

Types

  • Org-defined issue types (for example Bug, Feature, Enhancement, Task, Documentation, Security, Infrastructure), each with a color; one is the default.

Required on create

An organization can require that every new issue carry a Status, Priority, and Type. When enforced, creating an issue without them is rejected - so issues are triaged consistently across the org's repositories from the moment they're opened.

Where to set it

  • Org-wide: organization Settings → Issue Statuses / Priorities / Types. The same definitions are available over the REST API (and the MokoGIT MCP server) for automation.
  • Per issue: choose the Status, Priority, and Type when creating or editing an issue.

Get help

Open a support ticket or call (931) 820-0265.

Hits: 48