Issue Types enable you and your organization to categorize different types of work in Zenhub. Combined with Sub-issues, this structure provides a well-defined work breakdown system, allowing teams to tailor workflows to their needs. Here’s how to get started:

Setting Up Issue Types in GitHub (One-Time Step)

Your GitHub Organization Admin needs to configure Issue Types in GitHub. Follow these steps:

  1. Navigate to: https://github.com/organizations/ YOUR_GITHUB_ORGANIZATION_NAME /settings/issue-types.

  2. Add the following four Issue Types for Zenhub:

    • Objective

    • Project

    • Epic

    • Sub-task

Notes:

  • These names can be customized. Ensure you’ve added at least three Issue Types above day-to-day issues and one below.

  • Additional Issue Types can be added; Zenhub will integrate them.

Setting Up Your Issue Type Hierarchy in Zenhub (One-Time Step)

Your Zenhub Organization Admin needs to establish the hierarchy. Here’s how:

  1. Go to: https://app.zenhub.com/settings/o/ YOUR_ZENHUB_ORGANIZATION_NAME /issue-types.

  2. You’ll see five levels of Issue Types. Assign your types to the levels based on your needs. The default hierarchy is:

    • Level 1: Objective (Big-picture goals)

    • Level 2: Project (Major milestones and initiatives)

    • Level 3: Epic (Work spanning multiple sprints)

    • Level 4: Bug / Task / Enhancement / Story (Day-to-day issues)

    • Level 5: Sub-task (Granular tasks)


To Adjust Levels:

  • Click the three dots beside an Issue Type and select Edit.

  • Assign the Issue Type to the desired level.

  • Save your changes.

Issue Type Integration with Goals & Planning Panel and Timeline View

  • Levels 1/2/3: Shown by default in the Goals & Planning Panel and the Timeline View.

  • Levels 4/5: Shown on the Board and in Reports by default.

Customizing Visibility:

  • Use the Issue Type filter on the Board to display Level 1/2/3 Issue Types.

  • Add Level 4 Issues to the Goals & Planning Panel for organizations needing additional hierarchy (e.g., Business Unit, Product Line). Note: Enabling this for day-to-day Issues may impact performance.

Coming Soon: Default Issue Types Per Level

Set default Issue Types for each level. For example, if Level 4 contains Bug/Task/Enhancement, you could set “Task” as the default.

Steps to Set Default:

  • Click the three dots beside an Issue Type and select Edit.

  • Toggle the switch to mark the Issue Type as the default for that level.

Automated Hierarchy Management

Zenhub streamlines the assignment of new issues based on the hierarchy, some examples:

  • Creating Sub-issues in Epics (Level 3): Automatically assigned the default Issue Type for Level 4.

  • Setting a Parent for a Task (Level 4): Defaults to Issues in Level 3. This can be overridden by searching for other Issues.