# Epic AUTOWORK-67 - Type variants that allow for project specific settings of workflows, form configurations - easy to configure and light-weight alternative for Jira workflow schemas and screen schemas

Project: Stream Workflows & Automations
Status: in development
URL: https://community.openproject.org/work_packages/AUTOWORK-67

## Detailed specification

### Motivation and background information

Problem:  
Organizations with many projects need different teams to work with the same type in slightly different ways, while keeping governance and consistency across the portfolio. Customers coming from tools with a scheme layer, such as Jira Data Center rely heavily on Schemes to:

*   Map specific workflows to specific issue types within a project
    
*   Reuse workflow configurations across multiple projects
    
*   Enforce status transitions and governance rules per issue type
    
*   Maintain consistency across large teams and enterprise-scale project portfolios
    

OpenProject currently handles workflows differently. Each work package type can have a workflow defined per type globally, but there is no centralized scheme layer that allows admins to:

*   Define a named, reusable workflow bundle
    
*   Assign that bundle to multiple projects at once
    
*   Map different workflows to different work package types within a single scheme
    
*   Push updates to workflows at scale anytime

| Attribute | Value |
| --- | --- |
| Mockups | https://www.figma.com/design/Q5gKSjtWQpAz4wjArQ2U5R/Fundamentals--Sub-types?node-id=398-29188&t=hn3sj0ZicbUUSkdZ-1 |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2026 Q4 |
| Date | 2026-06-24 –  |
| Votes |  |
| List | RM Jira exit |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Showstopper — Go-Live Blocker |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| AUTOWORK-68 | Feature | Administrators can define and manage global type variants | closed |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-69 | Feature | Reuse a type's workflow | closed |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-70 | Feature | Reuse a type's form configuration | tested |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-71 | Feature | Reuse a type's PDF and subject configuration | tested |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-72 | Feature | Grouped types index page | closed |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-73 | Feature | Type variants are shown everywhere using their parent type's name | closed |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-74 | Feature | Project-level activation of type variants | tested |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-77 | Feature | Switching the active type variant in a project with a preview | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-78 | Feature | Allow project administrators to manage their own type variants | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-79 | Feature | Convert a project-owned type variant to a global one | merged |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-85 | Feature | Wizard-like creation flow for type variants | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-128 | Implementation | Implement details tab when editing a Type | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-129 | Implementation | Also use the wizard for creating root-types | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-131 | Feature | Rename "Sub-type" to "Variant" | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-134 | Implementation | Mark type or variant as default | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-142 | Feature | Variants can disable fields in the form configuration screen (when using linked mode) | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-144 | Feature | Variants can disable fields in the project attributes configuration screen (when using linked mode) | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-152 | Feature | Allow deletion of variants still in use | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-160 | Implementation | Simplify handling of variants enabled per project | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-163 | Feature | Create migrated variants for previous custom field selections | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-165 | Feature | Improve project selection for type variants | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-166 | Feature | Comparison view of variants | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-177 | Feature | Variants Tab under a type lists all variants | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-178 | Feature | Central overview of all workflows | tested |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-181 | Feature | New design for configuration modes (inherited/manual) and showing dependent types | closed |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-251 | Feature | Rename "Form configuration" to "Form" | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-253 | Feature | Add a purpose description to every aspect of type or variant configuration | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-254 | Feature | "Name" attribute of a type variant should indicate it is not public | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-269 | Feature | Make "Types" the first selected element for Work package administration | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-273 | Feature | Add configuration overview tab to show configuration mode and dependents overview on types and variants | closed |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-276 | Feature | Allow mandatory work package fields per type | tested |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-280 | Feature | On the custom field, show which forms, types & variants use this field | tested |  | 18.0.0 | Stream Workflows & Automations | High |  |
| AUTOWORK-281 | Feature | Allow deletion of types if they are active in a project, but not used in work packages | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-317 | Feature | Named forms that can be reused across multiple types and variants | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-328 | Feature | Update the Start page of the Create wizard for types and variants | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-329 | Feature | Inform users about which variants we created as a migration | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| AUTOWORK-338 | Feature | Edit forms and workflow: Add inset boxes to inform admins of reusable objects | tested |  | 18.0.0 | Stream Workflows & Automations | Medium |  |
| FND-253 | Feature | Change the PageHeader description text on the Type index page | tested |  | 18.0.0 | Stream workspace foundations | Medium |  |
| AUTOWORK-274 | Feature | Allow correcting stuck statuses when switching variants | new |  | Product Backlog | Stream Workflows & Automations | Medium |  |
| AUTOWORK-103 | Feature | Extend mode for form configuration | new |  | Wish List | Stream Workflows & Automations | Medium |  |
| AUTOWORK-175 | Feature | Allow bulk assignments and modifications of type variants to projects | new | Sonita Soth | Wish List | Stream Workflows & Automations | Medium |  |
| OP-19840 | Feature | Prevent / Ask for confirmation of deletion of custom fields currently in use by work package | new | Sonita Soth | Wish List | OpenProject | High |  |
| AUTOWORK-185 | Open Point | How can users best understand linked and independent mode? | decided |  |  | Stream Workflows & Automations | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| AUTOWORK-294 | Code maintenance | Variants can inherit from their parents only technically, not from other types | closed |  | 18.0.0 |  |
| AUTOWORK-167 | Bug | Missing empty state when project attribute tab is in linked mode | rejected | Cécile Guiot | 18.0.0 | Administration / Type/Variants and Workflows |
| AUTOWORK-311 | Bug | Copying project with project-specific variant causes invalid type configuration | tested |  | 18.0.0 |  |
| AUTOWORK-182 | Bug | Clicking on item in left side menu of variant wizard takes user to Create type wizard | tested |  | 18.0.0 | Administration / Type/Variants and Workflows |
| AUTOWORK-170 | Bug | Cannot create project with default types, when a variant is set to be used as a default in a project | tested |  | 18.0.0 | Administration / Type/Variants and Workflows |
| AUTOWORK-168 | Bug | Browser tab shows main type name on variant pages | tested |  | 18.0.0 | Administration / Type/Variants and Workflows |
| AUTOWORK-164 | Bug | Enabling a variant via the Types -> Projects tab shows a 500 error | tested |  | 18.0.0 | Administration / Type/Variants and Workflows |
| OP-20796 | Bug | Creating new type with new form ends up in invalid state | merged |  | 18.0.0 | Administration / Type/Variants and Workflows |
| AUTOWORK-154 | Bug | Dialog to switch to linked mode is too short | tested |  | 18.0.0 | Administration / Type/Variants and Workflows |
| AUTOWORK-185 | Open Point | How can users best understand linked and independent mode? | decided |  |  |  |
| AUTOWORK-392 | Bug | Create workflow button in Workflows index page is positioned wrong | confirmed |  |  | Administration / Type/Variants and Workflows, Administration, Administration / Work package administration |

## Details

| Attribute | Value |
| --- | --- |
| Module | Administration / Type/Variants and Workflows |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | OP Dev Sirius Team |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Feature Lead | Oliver Günther |
| Designer | Parimal Satyal |
| Developers | OP Dev Sirius Team |
| Requested by |  |
| Interest by | Black (37919), CEP (38264), Home (224196000003952096), Periscope (224196000002193032) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 15d 0h · Σ 171d 0h |

## Description

**Introduction:** Type Variants let admins adapt a work package type to the needs of a project or team without building the type from scratch. A Variant belongs to a &quot;parent&quot; Type (e.g. Bug with the variants &quot;Hardware&quot; and &quot;Software&quot;). Its workflow and form can be shared with other Types and Variants and stay in sync, or be configured independently when a team needs something different. The core concepts are the following:

*   Types and Variants: A Type can have Variants. A Variant appears with its parent Type’s name in the project, wherever work packages are displayed&nbsp;
    
*   One variant per project: Each project uses one variant of a type at a time. The same type can follow different processes in different projects.
    
*   Workflows and forms as named objects: A workflow or form can be reused by several Types and Variants
    
*   Other settings: Settings that are not standalone objects, such as defaults, project attributes and PDF export, either follow the parent type or are configured manually per variant
    
*   Linked or independent: The configuration area of a Variant can be linked to a source, so changes there flow through automatically, or configured independently
    
*   Global or project specific: Variants can be available instance-wide or owned by a single project
    
*   Delegation: Instance admins decide per type whether project admins can create and manage their own variants. Those variants are only available in that project. If not enabled, the type stays centrally managed
    
    <br>
    

**Goals**:

*   Let admins define variations (Variants) of a Type that fit specific project requirements
    
*   Make workflows and forms reusable objects that can be shared across Types and Variants
    
*   Reduce repetitive configuration when setting up new projects
    
*   Allow changes to be rolled out at scale, in one place
    
*   Make it transparent which Types, Variants and projects depend on a configuration
    
*   Reduce repetitive manual configuration when setting up new projects
    
*   Support large-scale enterprise deployments with hundreds of projects
    

**Non-Goals:**

*   This epic explains the core concept. Specific additions and refinements are tracked in the individual feature tickets.
    

**Target Users:**

*   Instance admins who maintain types, workflows and forms across the organization
    
*   Project admins who adapt how their project works within what the instance allows
    
*   Project members, who experience the result: the right statuses and fields for their work
    

**User Stories:**

1.  As an admin, I want to **define a workflow or form once** and give it a name, so that I can **reuse** it across several types.
    
2.  As an admin, I want a **change to a shared workflow or form** to **apply everywhere it is used**, so that I can **maintain processes at scale in one place**.
    
3.  As an admin, I want to **start a new workflow or form from a copy of an existing one**, so that I don’t have to build it from scratch.
    
4.  As an admin, I want to **see all workflows and forms with the types, variants and projects using them**, so that I know what exists and understand the impact of a change.
    
5.  As an admin, I want to **create variants of a type**, so that different teams can follow their own process without duplicate types.
    
6.  As an admin, I want a variant to use its parent’s configuration, another existing one, or its own, so that I **decide how much it differs**.
    
7.  As an admin, I want to **switch fields on or off** and adjust **required fields per variant**, so that each team only sees what it needs.
    
8.  As an admin, I want to decide per type whether **project admins may create their own variants**, so that I can delegate without losing oversight.
    
9.  As a project admin, I want to see which variants of a type are available and in use in my project, so that I **understand how my project is set up**.
    
10.  As a project admin, I want to **create variants for my project where allowed**, so that I can adapt the process without involving a global admin.
     

**Our vision**

[https://www.openproject.org/blog/type-variants-workflows-forms/](https://www.openproject.org/blog/type-variants-workflows-forms/)
