Naming a Status or Issue Type as an integer causes problems with the JQL in JIRA, breaking several areas

Summary

A Status or Issue Type as an integer messes up the way JIRA uses JQL and returns results. This presents in GreenHopper and also in JQL functions such as standardIssueTypes().

Environment

• Ubuntu 11.04
• PostgreSQL 9.1
• GreenHopper 6.1.3.2

Steps to Reproduce

1. Create a sample issue with a status of "Open".
2. Search for that issue with the following JQL:

   issuekey = DERPIDO-1 and status = 1
   issuekey = DERPIDO-1 and status = "1"
   

3. Add a status or issue type as an integer, for example 1. This is easy as it conflicts with "Open".
4. Search again using the above - the behaviour for "1" will change.

This also happens for Issue Types.

Expected Results

JIRA would either:

• Present an error about conflicting Status/Issue Types.
• Restrict users from being able to create Status/Issue Types that were an integer due to conflicting.

Actual Results

Nothing is returned as there are no issues with a status of "1".

Notes

Presented in several places so have raised a bunch of bugs for it.