• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • API and Integrations
    • None
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      As Service Desk customer, I want to fetch through the REST API only a subset of requests that I have opened.

      Currently, the /rest/servicedeskapi/request brings all requests.
      We need a way to filter that set by some fields, like created or updated, using JQL preferably.

      This request is basically to port whatever's implemented on the UI by JSDSERVER-3424 to the REST API too.

          Form Name

            [JSDSERVER-6880] Allow more search options on Jira Service Desk REST API

            Atlassian Update – 6 July 2021

            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,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 6 July 2021 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, Charlie Jira Service Management, Server & Data Center

            David added a comment -

            To expound on this, JSD customers who only have access to the portal have very limited options in the JSD API. If there could be JQL access or a limited version of JQL provided to JSD customers, that would solve many problems for our customers. The problem with providing access to the current JQL in Jira Core is it "leaks" information that wouldn't normally be available on the portal e.g., fields that should not be visible on the portal and even other Organization names if they type in "Organizations = ..."

            David added a comment - To expound on this, JSD customers who only have access to the portal have very limited options in the JSD API. If there could be JQL access or a limited version of JQL provided to JSD customers, that would solve many problems for our customers. The problem with providing access to the current JQL in Jira Core is it "leaks" information that wouldn't normally be available on the portal e.g., fields that should not be visible on the portal and even other Organization names if they type in "Organizations = ..."

              Unassigned Unassigned
              rmartinez3@atlassian.com Rodrigo Martinez
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: