-
Bug
-
Resolution: Not a bug
-
Low (View bug fix roadmap)
-
None
-
6.3.9, 6.3.10
-
6.03
-
Problem statement:
During a JQL filter, projects with no permission gives a false error of non existent instead.
Steps to Reproduce:
1. As an admin, create several new projects (TIA,TIB,TIC,TID,TIE).
2. As an admin, specify ONLY user A with granted permission for viewing project TIE.
3. As an admin, perform a JQL filter including the 5 projects. (non existent project TIE false error)
Current/Actual behavior:
False Error
"A value with ID 'E' does not exist for the field project".
Add TIE in filter.
Expected Behavior:
Instead of Error Text - A value with ID 'TIE' does not exist for the field 'project'
Replace with
"User does not have permission for value with ID 'TIE' in the field project"
OR
"Project with ID 'TIE' does not exist"
while
ALWAYS showing the rest of the filter Results.
Additional Info:
- relates to
-
JRASERVER-40245 Allow JQL searches via the Issue Navigator to skip validation and return partial results
- Gathering Interest
[JRASERVER-41253] JQL filter False Error: Project doesn't exist should be no permission
Atlassian treats this a "Not a bug" , but it is not logical to me. And it looks like most of the Jira users expect just another behavior - which seems more logical to me.
At least Atlassian should offer another solution how we can achieve it.
The improvement https://jira.atlassian.com/browse/JRASERVER-40245 is open since 2014 and still in status "Gathering interest"
Isaac Abramowitz
added a comment - I've been noticing the same thing in the REST Api (/search?jql='jql'), when searching for project=x OR project = y (y does not exist), I get no return issues even though project x exists.
this applies to other fields. eg.
... project=x OR status=notastatus
{
"errorMessages": [
"The value 'notastatus' does not exist for the field 'status'."
],
"errors": {}
}
Obviously I would have liked to get the results of project=x since there are some values where this is true. I just find it a little less intuitive since I'm coming from SQL.
Anyway, I know this is an old thread, but does anyone know if this sort of thing has been resolved?
Isaac Abramowitz
added a comment - I've been noticing the same thing in the REST Api (/search?jql='jql'), when searching for project=x OR project = y (y does not exist), I get no return issues even though project x exists.
this applies to other fields. eg.
... project=x OR status=notastatus
{
"errorMessages" : [
"The value 'notastatus' does not exist for the field 'status' ."
],
"errors" : {}
}
Obviously I would have liked to get the results of project=x since there are some values where this is true. I just find it a little less intuitive since I'm coming from SQL.
Anyway, I know this is an old thread, but does anyone know if this sort of thing has been resolved? | Minimum Version | New: 6.03 |
| Workflow | Original: JAC Bug Workflow v2 [ 2844178 ] | New: JAC Bug Workflow v3 [ 2914533 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2581449 ] | New: JAC Bug Workflow v2 [ 2844178 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1541096 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2581449 ] |
| Labels | Original: ho-jql-backend | New: affects-server ho-jql-backend |
| Labels | New: ho-jql-backend |
| Component/s | New: Issue Navigation & Search - JQL [ 43398 ] | |
| Component/s | Original: Issue navigator [Deprecated] [ 10670 ] |
Please let me know why this is not solved since ages?
BR
Heiko