-
Suggestion
-
Resolution: Low Engagement
-
None
-
3
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Steps to Reproduce:
- Create a custom field with a project context (preferably a JSD project).
- Go to the Queues tab and make a new Queue.
- Try selecting the custom field under Issues to Show.
Expected Results:
Able to select the custom field because the JQL should be only specific to the JSD project even if the project is not specified.
Actual Results:
Not able to select the custom field.
Workaround:
- Remove the project context from the custom field.
- Or add project query into the JQL field and specify the project so that the field is now specific to the JSD project.
- is related to
-
JSDSERVER-4737 Basic search in JSD shows incorrect options when custom field restricted by project context
-
- Closed
-
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-1659] Can't choose custom fields bound by project context at JIRA Service Desk Queue JQL field
I agree, this surely must be classed as a bug. The fact that the work round is to specify the JSD project in the JQL of a queue specific to the JSD project implies that the intended logic is broken.
As Julia said, we don't want our JIRA Software projects cluttered up with support specific fields. What's the point of having the flexibility to restrict fields to projects if that breaks fundamental features of Service Desk like queues?
Hi ,
this bothers our users.
We have Jira Service Desk and Jira Software running on our instance, so a lot of our custom fields are restricted to one Service Desk project. We also have quite a few queues.
The SD Queues are built into a single Service Desk project, so maybe the filter should restrict itself to this one project automatically. And since the Project cannot be added to the filter in the Basic view, our users were quite annoyed with the workaround.
We consider this a bug, not a suggestion.
We're looking forward to this being fixed. 
Best Regards
Julia
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center