Feature #15919
closed
Set default category assignee immediately upon category selection
0%
Description
Currently, the one can see default assignee only after the issue is created. This confuses people and it should be good to set it ASAP using AJAX call.
Files
Related issues
Updated by Jean-Philippe Lang about 10 years ago
- Tracker changed from Defect to Feature
Updated by Go MAEDA over 6 years ago
- Related to Feature #26680: Show default assignee when creating new issue added
Updated by Mizuki ISHIKAWA over 6 years ago
- File 0001-Set-default_assigned_to_id-in-category.patch 0001-Set-default_assigned_to_id-in-category.patch added
- File 0002-Set-default_assigned_to_id-in-project.patch 0002-Set-default_assigned_to_id-in-project.patch added
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
Updated by Toshi MARUYAMA
Updated by Go MAEDA almost 6 years ago
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Priority changed from High to Normal
- Target version changed from 4.1.0 to 4.0.0
- Resolution set to Fixed
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.
Updated by Marius BĂLTEANU almost 6 years ago
- Status changed from Closed to Reopened
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.
Updated by Jean-Philippe Lang almost 6 years ago
- Status changed from Reopened to Closed
I made a small change that improves the behaviour when changing/removing the category and solves the 2 issues reported by Marius.
Updated by Go MAEDA almost 6 years ago
- Related to Defect #28951: Cannot clear category field on copying an Issue added
Updated by Marius BĂLTEANU almost 6 years ago
- File duplicated_assignee.png duplicated_assignee.png added
- Status changed from Closed to Reopened
- Assignee changed from Go MAEDA to Jean-Philippe Lang
- Resolution deleted (
Fixed)
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
Updated by Marius BĂLTEANU over 5 years ago
We can deliver this feature as it is and I will try to find a proper implementation for the next minor version of Redmine 4.
Updated by Jean-Philippe Lang over 5 years ago
- Status changed from Reopened to Closed
- Resolution set to Fixed
Updated by Marius BĂLTEANU over 5 years ago
- Related to Defect #29695: Duplicated assignee option when selecting a category with default assignee added