-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
5.2.11
-
None
-
5.02
-
Steps to reproduce:
- Create 2 projects in fresh JIRA instance (eg. project test and project B).
- Create an issues in both projects (eg. test-123, pb-1).
- Now create a new filter like this:
key in (TEST-123, PB-1)
- Remove the user 'Browser Project' permission of project test.
- After that, go back to the same filter. An error shown that the key for TEST-123 is invalid and change to issue key 11305. Please see attached:
Finding:
- This problem only happen in JIRA 5.2.x.
- Also, tested in JIRA 6 but not able to reproduce it.
- was cloned as
-
JRASERVER-34561 Issue key change to Issue ID after an error message occured in JQL
-
- Closed
-