-
Suggestion
-
Resolution: Timed out
-
0
-
3
-
Hi Everyone,
Thank you for previously raising this feature request and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each feature request but admit that not each one will be implemented. To continue the culture of being honest and open, we are closing this ticket to focus on our upcoming roadmap for all Jira Service Management Cloud users. You can visit Atlassian Cloud Roadmap to learn more about what was recently released and the upcoming roadmap.
Thank you again for providing valuable feedback to our team!
Arjun Ganapathy
Jira Service Management Cloud team
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? 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
-
JSDCLOUD-15093 Contextual dropdowns - basic search in JSD shows incorrect options when custom field restricted by project context - should only show fields and values from current project
-
- Closed
-
-
- Closed
- mentioned in
-
Page Loading...