New issue 156 by russelw.young: Field value condition passed in v3.13.5 but
fails in v4.2
http://code.google.com/p/jira-suite-utilities/issues/detail?id=156
What steps will reproduce the problem?
1. Create conditions for field "Issue Type" = "Defect" (String)
and "Project" = "Platform" (String)
2. In v3.13.5 using 0.7.8 both of these conditions pass, showing the
workflow action
3. In v4.2 using 0.7.15 the Issue Type condition passes but the Project
condition fails
What is the expected output? What do you see instead?
I expected it to work the same as it did before
What version of the product are you using? On what operating system?
Jira 4.2 plugin 0.7.15
Please provide any additional information below.
Thanks for your help!
Comment #1 on issue 156 by abashev: Field value condition passed in v3.13.5
but fails in v4.2
http://code.google.com/p/jira-suite-utilities/issues/detail?id=156
Looks like it is a bug. I'll fix it but right now you can use workaround -
compare Project field with "Project: Platform"
I encountered this bug today trying to put a condition on project name.
Note the workaround works using project key not project name (eg "Project:
PLAT" or whatever the key is not "Project: Platform").
When you fix the bug, will it use key or name? My preference would be for
key. Thanks.
It will be available at the next version. And it will be key as project id.
Comment #4 on issue 156 by abashev: Field value condition passed in v3.13.5
but fails in v4.2
http://code.google.com/p/jira-suite-utilities/issues/detail?id=156
(No comment was entered for this change.)