Project

General

Profile

Actions

Defect #17555

open

Mandatory condition for 'Category' & 'Assignee' is not working according to workflow defined

Added by Lajish Lakshmanan over 9 years ago. Updated about 4 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Administration
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Hi folks,
I encountered a loop hole in workflow where a member having tester role is having Required condition for Category & Assignee against an issues status New.
But tester can create a New issue without providing Category & Assignee.

I don't know whether this issue has been reported earlier or not. But I request humbly to incorporate this defect's remedy to very next version of Redmine.


Related issues

Related to Redmine - Defect #23394: Auto-assign on category selection does not work when assignee is a required fieldNew

Actions
Actions #1

Updated by Lajish Lakshmanan over 9 years ago

There is little change in scenario for same. Suppose tester role member is Administrator then these mandatory condition in workflow doesn't works.

Actions #2

Updated by Toshi MARUYAMA over 7 years ago

  • Related to Defect #23394: Auto-assign on category selection does not work when assignee is a required field added
Actions #3

Updated by Peter Volkov about 4 years ago

Yea, I'm having troubles with making assegnee field mandatory. And another user reported exactly the same problem here: https://www.redmine.org/boards/2/topics/54055

Actions

Also available in: Atom PDF