Project

General

Profile

Actions

Defect #23394

open

Auto-assign on category selection does not work when assignee is a required field

Added by JW Fuchs over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
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

Files

01_required_field.PNG (31.4 KB) 01_required_field.PNG JW Fuchs, 2016-07-21 13:04
02_category_settings.PNG (7.06 KB) 02_category_settings.PNG JW Fuchs, 2016-07-21 13:04
03_error_on_creation.PNG (26.6 KB) 03_error_on_creation.PNG JW Fuchs, 2016-07-21 13:04

Related issues

Related to Redmine - Feature #6889: Set assignee on category changeNew2010-11-15

Actions
Related to Redmine - Defect #17555: Mandatory condition for 'Category' & 'Assignee' is not working according to workflow definedNew

Actions
Actions

Also available in: Atom PDF