Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.2.7
-
5.02
-
8
-
Severity 3 - Minor
-
1
-
Description
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
- Create a sample issue with a status of "Open".
- Search for that issue with the following JQL:
issuekey = DERPIDO-1 and status = 1 issuekey = DERPIDO-1 and status = "1"
- Add a status or issue type as an integer, for example 1. This is easy as it conflicts with "Open".
- 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.
Attachments
Issue Links
- causes
-
JRASERVER-31811 When using the standardIssueTypes() JQL it does not return the appropriate Issue Types
- Closed
- relates to
-
JSWSERVER-7826 The JQL builder puts the ID of Status and Issue Types as a string and this can cause no issues to be returned
- Closed
(2 mentioned in)