Project

General

Profile

Actions

Defect #43869

closed

Default assignee selected by category is not shown in UI

Added by Piano Tako 16 days ago. Updated 9 days ago.

Status:
Closed
Priority:
Normal
Category:
UI
Target version:
Resolution:
Fixed
Affected version:

Description

When selecting a category, the default assignee of that category should be shown automatically.

This feature works correctly in Redmine 5.1.2.
However, after upgrading to Redmine 6.1.1, it no longer works.
The assignee is actually selected, but it is not shown correctly in the UI.

We found the difference in the HTML of the assignee field.
In Redmine 5.1.2, the HTML is:

<select name="issue[assigned_to_id]" id="issue_assigned_to_id">
  <option value="">user2 test</option>
  <option value="1">&lt;&lt; me &gt;&gt;</option>
  <option value="1">Redmine Admin</option>
  <option value="5">user1 test</option>
  <option value="6">user2 test</option>
</select>

In Redmine 6.1.1, the HTML becomes:
<select name="issue[assigned_to_id]" id="issue_assigned_to_id">
  <option value="" label=" ">user2 test</option>
  <option value="1">&lt;&lt; me &gt;&gt;</option>
  <option value="1">Redmine Admin</option>
  <option value="5">user1 test</option>
  <option value="6">user2 test</option>
</select>

There is a new attribute label in the first <option>:
<option value="" label=" "></option>

According to the HTML specification, if an <option> has a label attribute, the browser will display the label value instead of the inner text.
Because the label is " " (empty space), the selected assignee appears blank in the UI, even though the value is set.

We suspect this change may be related to the new UI/theme in Redmine 6.x, but we are not sure where it should be fixed.
Could someone help check and fix this issue?


Files

assignee_not_shown.jpg (75.9 KB) assignee_not_shown.jpg Piano Tako, 2026-03-10 10:24
43869.patch (1.89 KB) 43869.patch Go MAEDA, 2026-03-13 04:33

Related issues

Related to Redmine - Feature #15919: Set default category assignee immediately upon category selectionClosedJean-Philippe LangActions
Actions #1

Updated by Piano Tako 16 days ago

Actions #2

Updated by Go MAEDA 14 days ago

  • Related to Feature #15919: Set default category assignee immediately upon category selection added
Actions #3

Updated by Go MAEDA 14 days ago

  • Status changed from New to Confirmed
Actions #4

Updated by Go MAEDA 14 days ago

Thank you for reporting the issue.

The attached patch should fix the reported issue.

Actions #5

Updated by Marius BĂLTEANU 11 days ago

  • Assignee set to Marius BĂLTEANU
  • Target version changed from Candidate for next minor release to 6.0.9

The issue reproduces on all 6.* versions.

Actions #6

Updated by Go MAEDA 11 days ago

The test in test/functional/issues_controller_test.rb:4245 fails after commit r24491 because the changes to app/views/issues/new.js.erb included in the original patch 43869.patch were omitted.

Actions #7

Updated by Mizuki ISHIKAWA 11 days ago

https://github.com/redmine/redmine/actions/runs/23107324918/job/67118743164

It looks like there are unnecessary blank lines on lines 9058 and 9059 in the https://www.redmine.org/projects/redmine/repository/svn/revisions/24491/diff, and the lint check is also failing because of them.

Actions #8

Updated by Marius BĂLTEANU 10 days ago

Go MAEDA wrote in #note-6:

The test in test/functional/issues_controller_test.rb:4245 fails after commit r24491 because the changes to app/views/issues/new.js.erb included in the original patch 43869.patch were omitted.

I wanted to validate first on which branch the issue reproduces. I've committed now also the fix.

Actions #9

Updated by Marius BĂLTEANU 10 days ago

  • Status changed from Confirmed to Resolved
  • Resolution set to Fixed
Actions #10

Updated by Marius BĂLTEANU 10 days ago

  • Affected version changed from 6.1.1 to 6.0.8
Actions #11

Updated by Marius BĂLTEANU 9 days ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF