Validate a field rule under Workflow won't work with Built-in Resolution field

Question

When trying to add Validate a field rule against "Resolution" field using Matches regular expression option, the page will always return the error:

Field Resolution with actual value 'IssueConstantImpl[[GenericEntity:Resolution][sequence,6][name,Later][iconurl,null][description,There is no enough information available to continue working on the issue, but, once the information become available, we will continue to work on it. ][id,10005][version,1]]' does not match regular expression {ANY}

{ANY} can be replaced by any regular expression, e.g.

^(?:[3-9]|\d{2,})$

(Later|Invalid)

The same regular expression will work with other fields, like the text field, but it just doesn't work with this built-in Resolution field.

Does anyone have a solution for this?

Miquel Villarta Martinez · Answer

I found a solution even is not so nice. To let only "Passed" or "Not Passed" values in RESOLUTION Field in a certain Workflow, I added both possibilities typing the full detail:
(IssueConstantImpl$$\[GenericEntity:Resolution$$$$sequence,1$$$$name,Passed$$$$iconurl,null$$$$description,approved$$$$id,10040$$$$version,null$$\]|IssueConstantImpl$$\[GenericEntity:Resolution$$$$sequence,2$$$$name,Not Passed$$$$iconurl,null$$$$description,not approved$$$$id,10041$$$$version,0$$\]) bypassing all characters "[" "]"
The use of wildcards didn't worked for me

Benjamin_tmh9yg · Answer

HI @Art Hsieh ,

I'm not sure you can use it for system fields like resolutions or statuses. Most cases I've seen is for text or number fields where user can type in any string of text. However, resolution is a handful from a set list, so you can usually match a list instead of using regex.

-Ben