Redmine

I wrote a patch to implement this feature.

Please try to apply this patch: 0001-Set-default_assigned_to_id-in-category.patch

In addition, applying this patch will allow you to set default project assignee in the same way:
0002-Set-default_assigned_to_id-in-project.patch

Committed the patch 0001-Set-default_assigned_to_id-in-category.patch. Thank you for improving Redmine.

I will commit the second patch 0002-Set-default_assigned_to_id-in-project.patch for #26680.

This is a nice feature, indeed, but I think that the current implementation has some issues that we should address/clarify:

1. The default category assignee is not cleared when the category is changed with a category without assignee
- Go to new issue page
- Select a category with assignee
- Observe that the assignee is set correctly
- Change the category with a category without assignee
- Observe that assignee remains the previous one

The expected result from my point of view is to clear the assignee.

2. Manually selected assignee is override by the category assignee.
- Go to new issue page
- Manually select an assignee
- Select a category with assignee
- Observe that the manually selected assignee is replaced by the category assignee

The expected result here (and also the current behaviour until this ticket) is to keep the manually selected assignee.

3. Because there are a lot of scenarios and the code become quite complex, we should cover the cases with system tests.

I can help on fixing this issues and adding some tests, just please let me know.

I made a small change that improves the behaviour when changing/removing the category and solves the 2 issues reported by Marius.

I found another issue:

1. Go to a project with a default category assignee
2. Go to new issue page
3. Select the category with the default assignee
4. Open the Assignee dropdown
5. Observe that the default category assignee is duplicated in the dropdown.

The issue is generated by the line source:trunk/app/views/issues/new.js.erb#L6