• 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.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Update 13 Jan 2016: JIRA Service Desk now has a public REST API. See comment below.

      As outlined in this answer question https://answers.atlassian.com/questions/225223/does-jira-service-desk-have-a-public-rest-api# JIRA Servicve Desk does not currently have a public REST API.

      We do have internal REST resources that we use in the agent view and we plan to expand that into the "customer portal view" soon but these do not have the strong API guarantee against change. They are there to support the "dynamic browser front end".

      Service Desk is of course built on top of the JIRA platform so issue creation / retrieval REST APIs are available via standard JIRA facilities.

      https://docs.atlassian.com/jira/REST/latest/

      As the JIRA Service Desk architect I am intrigued to learn more about about what type of REST APIs people would like and what use cases you are trying to satisfy and how they are more specific to JIRA Service Desk than the current JIRA public REST api.

      Please use this improvement request on JAC (https://jira.atlassian.com/) or send me a direct email on brad.baker@atlassian.com to further discuss what you are after.

        1. service-desk-sla.png
          service-desk-sla.png
          93 kB
        2. service-desk-sla.png
          service-desk-sla.png
          98 kB

            [JSDSERVER-107] Create a public REST API for JIRA Service Desk

            tj5julien16 there is now a /customer resource you can use to create customer accounts: https://docs.atlassian.com/jira-servicedesk/REST/cloud/#servicedeskapi/customer

            Grégory Joseph (Inactive) added a comment - tj5 julien16 there is now a /customer resource you can use to create customer accounts: https://docs.atlassian.com/jira-servicedesk/REST/cloud/#servicedeskapi/customer

            Hi Brad

            It could be fantastic if the Jira Issue Collector could be made available to work with Jira Service Desk project corresponding to the way the mail channel works for Service Desk, by creating an external users seamless and set the user as reporter.
            I discussed the issue with Mick Nassette (SDS-6243) last year and he created a feature request JRA-44338.

            Best regards
            Troels Funder

            Malte Vedel Kobborg added a comment - Hi Brad It could be fantastic if the Jira Issue Collector could be made available to work with Jira Service Desk project corresponding to the way the mail channel works for Service Desk, by creating an external users seamless and set the user as reporter. I discussed the issue with Mick Nassette (SDS-6243) last year and he created a feature request JRA-44338 . Best regards Troels Funder

            Hi Brad,

            I am developping the code mentionned by TJ above.
            As he points out, we can create a request and assign a participant with the jsd rest api. However, the participant is defined by an existing 'username'.
            what we would like, is to create a jsd user (customer) directly from the information posted on our contact form (first / last name + email), and assign it to the issue.
            I tried to create the user using 'experimental' rest api /user endpoint, but the problem is that i can't assign it to "jira-servicedesk" application (gives error "Application access permissions cannot be modified via REST in Cloud."), so we end up with a 'regular' user, which is not what we want (as it is then mixed with our own organizations users... and has access to things it shouldn't).
            Hopefully you either the assign to application issue can be fixed, or a solution could be added directly in jsd rest api...

            Best regards,
            julien

            Julien Vonthron added a comment - Hi Brad, I am developping the code mentionned by TJ above. As he points out, we can create a request and assign a participant with the jsd rest api. However, the participant is defined by an existing 'username'. what we would like, is to create a jsd user (customer) directly from the information posted on our contact form (first / last name + email), and assign it to the issue. I tried to create the user using 'experimental' rest api /user endpoint, but the problem is that i can't assign it to "jira-servicedesk" application (gives error "Application access permissions cannot be modified via REST in Cloud."), so we end up with a 'regular' user, which is not what we want (as it is then mixed with our own organizations users... and has access to things it shouldn't). Hopefully you either the assign to application issue can be fixed, or a solution could be added directly in jsd rest api... Best regards, julien

            tj5 - in its present form the REST API always requires a authenticated user, as does the customer portal.

            Do you want to post to the create request API with a "reporter" as an email address say and have that created automatically?

            You can ping me direct on brad.baker@atlassian.com if you would like to leave more specific use case information.

            Cheers
            Brad

            ɹǝʞɐq pɐɹq added a comment - tj5 - in its present form the REST API always requires a authenticated user, as does the customer portal. Do you want to post to the create request API with a "reporter" as an email address say and have that created automatically? You can ping me direct on brad.baker@atlassian.com if you would like to leave more specific use case information. Cheers Brad

            TJ Baker added a comment -

            Any chance the API might some day allow creating an issue while also creating the user (as is done when a new user sends an email)?

            We'd like to use our own forms to allow customers to create issues / contact us, but as of now it seems were limited in the API to allow this, as only authenticated users can create the issues through API.

            TJ Baker added a comment - Any chance the API might some day allow creating an issue while also creating the user (as is done when a new user sends an email)? We'd like to use our own forms to allow customers to create issues / contact us, but as of now it seems were limited in the API to allow this, as only authenticated users can create the issues through API.

            Andrew added a comment -

            Hi philip.colmer, thanks for your comment. We are actually following the model that we've used for while with our REST API docs, where we have separate docs for Cloud and Server
            (As an aside, we actually didn't split the Cloud and Server docs. We were only generating REST API docs for the Cloud REST API, since it was introduced, and it just happened to be that the docs for the Server version were the same).

            Feedback is definitely appreciated though. I'm guessing that you are building an add-on for both JIRA Service Desk Cloud and Server? I'll pass your comment on to the dev team, if they haven't already read it.

            Andrew added a comment - Hi philip.colmer , thanks for your comment. We are actually following the model that we've used for while with our REST API docs, where we have separate docs for Cloud and Server (As an aside, we actually didn't split the Cloud and Server docs. We were only generating REST API docs for the Cloud REST API, since it was introduced, and it just happened to be that the docs for the Server version were the same). Feedback is definitely appreciated though. I'm guessing that you are building an add-on for both JIRA Service Desk Cloud and Server? I'll pass your comment on to the dev team, if they haven't already read it.

            Would it be possible to add a session resource to the JIRA Service Desk API that behaves the same as auth/1/session from the JIRA REST API, but for service desk users? The idea being that we could emulate the Service Desk log in screen without it being presented to users. This would allow a seamless transition from our product to JIRA Service Desk.

            Bryce Holycross added a comment - Would it be possible to add a session resource to the JIRA Service Desk API that behaves the same as auth/1/session from the JIRA REST API, but for service desk users? The idea being that we could emulate the Service Desk log in screen without it being presented to users. This would allow a seamless transition from our product to JIRA Service Desk.

            alui I am a bit concerned to see that documentation has been split between Cloud and Server. Would it not make more sense (be safer?) to have a single set of documentation and call out any differences, if any exist? Otherwise a developer needs to literally compare the two pages to see where differences lie.

            Philip Colmer added a comment - alui I am a bit concerned to see that documentation has been split between Cloud and Server. Would it not make more sense (be safer?) to have a single set of documentation and call out any differences, if any exist? Otherwise a developer needs to literally compare the two pages to see where differences lie.

            Phill Fox added a comment -

            Is there any intention to extend the API to include the ability to respond compliance at a portal level against SLAs.

            Phill Fox added a comment - Is there any intention to extend the API to include the ability to respond compliance at a portal level against SLAs.

            edwin added a comment -

            Just a quick note that Server 3.1 has been released. The API is available with that version. Thanks!

            edwin added a comment - Just a quick note that Server 3.1 has been released. The API is available with that version. Thanks!

              Unassigned Unassigned
              bbaker ɹǝʞɐq pɐɹq
              Votes:
              309 Vote for this issue
              Watchers:
              198 Start watching this issue

                Created:
                Updated:
                Resolved: