-
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
-
[JRASERVER-33309] Issue key change to Issue ID after an error message occured in JQL
Minimum Version | New: 5.02 |
Workflow | Original: JAC Bug Workflow v2 [ 2839921 ] | New: JAC Bug Workflow v3 [ 2917487 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2570231 ] | New: JAC Bug Workflow v2 [ 2839921 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1537128 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2570231 ] |
Labels | New: affects-server |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 663950 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1537128 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 653358 ] | New: JIRA Bug Workflow w Kanban v6 [ 663950 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 533828 ] | New: JIRA Bug Workflow w Kanban v6 [ 653358 ] |
Fix Version/s | New: 6.0 [ 29793 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Verified [ 10005 ] | New: Resolved [ 5 ] |