The 'Assignee Only Condition' fails if assignee is changed on transition screen.
This is due to the fact that the issue is retrieved from the database initially and then cached. This cached issue is subsequently used throughout the conidtion and results in errors when validating - workaround is to retrieve issue from database each time for validation purposes.
Description
The 'Assignee Only Condition' fails if assignee is changed on transition screen.
This is due to the fact that the issue is retrieved from the database initially and then cached. This cached issue is subsequently used throughout the conidtion and results in errors when validating - workaround is to retrieve issue from database each time for validation purposes.
The attached class will revert back to 3.1.1 and 3.2 Beta behaviour and allow the assignee to be changed on the transition screen without resulting in error.
Please replace the original class with the attached class:
Keith Brophy added a comment - 01/Jun/05 07:54 PM The attached class will revert back to 3.1.1 and 3.2 Beta behaviour and allow the assignee to be changed on the transition screen without resulting in error.
Please replace the original class with the attached class:
../java/com/atlassian/jira/workflow/condition/AbstractJiraCondition.java
Dylan Etkin [Atlassian] added a comment - 07/Jun/05 02:03 AM Fixed this in 3.2.1 by having the Conditions go to the db for the issue everytime. This should be changed in 3.3, I will open another issue.
Bug
Resolved
Major
'Assignee Only Condition' fails if assignee is changed on transition screen.
Please replace the original class with the attached class:
../java/com/atlassian/jira/workflow/condition/AbstractJiraCondition.java