Defect #23394
Auto-assign on category selection does not work when assignee is a required field
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Issues | |||
Target version: | - | |||
Resolution: | Affected version: |
Description
When the assignee is set as a mandatory field, the auto-assign function related to category does not work.
Test setting:
Category definition:
Attempt to create issue:
If the assignee requirement is removed, the assignee is set as expected after a category has been chosen and the issue has been created.
Environment: Redmine version 3.3.0.stable Ruby version 2.1.8-p440 (2015-12-16) [i386-mingw32] Rails version 4.2.6 Environment production Database adapter Mysql2 SCM: Subversion 1.8.16 Git 2.7.4 Filesystem Redmine plugins: no plugin installed
Related issues
History
#2
Updated by Toshi MARUYAMA almost 6 years ago
- Category set to Issues
#3
Updated by Toshi MARUYAMA almost 6 years ago
- Related to Feature #6889: Set assignee on category change added
#4
Updated by Toshi MARUYAMA almost 6 years ago
- Related to Defect #17555: Mandatory condition for 'Category' & 'Assignee' is not working according to workflow defined added