# Bug AUTOWORK-149 - Variants are indistinguishable from their parent type when choosing a configuration source

Project: Stream Workflows & Automations
Status: closed
URL: https://community.openproject.org/work_packages/AUTOWORK-149

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 17.8.0 |
| Observed in versions |  |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | David Friquet |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Effort (shirt size) |  |
| Work |  |
| Labor costs |  |

## Description

### Before filing a report

Found on `dev` at v17.8.0 while implementing FND-169. Related to FND-190, which covers the shared root cause of the ordering half of this report.

### Steps to reproduce

Requires the `type_variants` feature flag to be enabled.

1.  Log in as an administrator
    
2.  Go to Administration → Work packages → Types
    
3.  Add two variants under the same type — for example &quot;Small&quot; and &quot;Big&quot; under &quot;Task&quot;
    
4.  Open a different type → Form configuration tab
    
5.  Click &quot;Switch to linked mode&quot; (or &quot;Change source&quot; if the form configuration is already linked)
    
6.  Open the source dropdown in the dialog
    

### What is the buggy behavior?

Every variant in the dropdown was labelled with the name of the type it belongs to rather than its own name, so the list contained entries that looked exactly alike:

> Bug, Task, Smoke consumer, Smoke source, Task, Task, Smoke consumer, Milestone, Summary task, Feature

&quot;Task&quot; appeared three times — once for the type itself, once for each of its variants — with nothing on screen to tell them apart. The list was also in no recognisable order, with variants scattered between unrelated types.

An administrator choosing from that list had no way of knowing which entry they were picking.

### What is the expected behavior?

*   Each variant is listed as &quot;Type: Variant&quot; — for example &quot;Task: Big&quot; and &quot;Task: Small&quot; — so every entry is unique and readable
    
*   Entries are grouped by family: a type is immediately followed by its own variants, in alphabetical order
    
*   The types themselves keep the order set on the Types administration page
    

### How to verify

The same list appears in three places and all three should read the same way:

1.  Form configuration tab → &quot;Switch to linked mode&quot; / &quot;Change source&quot;
    
2.  Form configuration tab → &quot;Copy configuration&quot;
    
3.  Project settings → Work packages → Types → &quot;Add type&quot;
    

Two things worth checking beyond the labels:

*   Reordering root types on the Types administration page changes the order in all three dropdowns to match
    
*   Variants always appear alphabetically, whatever order they were created in
    

### Logs

No errors in the browser console or in `production.log`. The dialog works; it just presents unusable choices.

### Screenshots and other files

Reproducible from the steps above; the dropdown contents are quoted verbatim in &quot;What is the buggy behavior?&quot;.

### Environment information

**OpenProject installation type**

*   Docker-compose installation (development environment)
    

**OpenProject version**

v17.8.0 (`dev`, commit `d718e0fd2`)

**Browser**

Not applicable — the labels and ordering are rendered server-side, identical in every browser.

**Operating System**

*   Linux (Debian, Docker development environment)
    

**Language**

Not applicable — the defect is not locale-dependent.
