I've got a custom field of type 'Labels' which is used across several different projects.
On the Issue View page the values/labels are hyperlinks - which take the user to a JQL results page with JQL like:
project in (29202, 29001, 42907, 38300, 19100) AND issuetype in ("14", "14200", "15") AND cf[37001] = APP20315
For me this JQL works - but for other users who don't have access rights to all the project Ids listed in the JQL they get an error saying 'A value with ID 19100 does not exist for the project field' for each project ID they don't have access to,.
The list of project IDs is clearly from the custom field configuration context.
Initially the projects were all configured against the one context and under those circumstances the JQL is I guess reasonable. I've since split them out into their own contexts but it's made no difference (all projects have been reindex and a Jira background re-index has also completed).
Any ideas? Is this a constraint of the custom Labels field type - that all projects using that custom field share the same autocomplete pool of labels irrespective of contexts?
Hello @James Deuchar
For me, you can ask the user to delete all project parts from the JQL. The JQL returns an error because they do not have access to some projects or because some projects are archived.
I think clicking on a hyperlink for a label field is normal system behavior: it shows all issues across the instance with this label, even if the user does not have access to some projects.
https://jira.atlassian.com/browse/JRASERVER-46384
A ticket is currently in Gathering Impact :)
Maybe by chance they will deploy it before Data Center is decommissioned in 2029 😄
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.