Transition Properties -jira.field.resolution.include​

[Deleted user]

is there any restrictions on the order of property keys shown in transition properties when change workflow ? 

I used jira.field.resolution.include​ to control resolution selection list for different type of issue; but didn't see the result after I did -

1. modify workflow schem
2. copy the main workflow to a working workflow , e.g. workflow A to workflow B
3. modify workflow B jira.field.resolution.include​ properties to have what I want for this issue type. e.g. bug
4. apply workflow B to bug type, while workflow A still for other types
5. A and B in workflow scheme

which part went wrong ?  I can see workflow A still working fine, but workflow B not; however, the only change I did in B was to get rid of one resolution ID, so users have less to choose. 

[Alexey Matveev]

Hello,

jira.field.resolution.include does not exist. You can find the following ticket:

https://jira.atlassian.com/browse/JRASERVER-16443

[Linda H]

Actually jira.field.resolution.include does exist and it does work.  Though not fully recommended.