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

      Problem Definition

      We currently have a public API GET /rest/servicedeskapi/servicedesk that retrieves all Service Desk IDs from the database, but no API to specifically retrieve Portal IDs (IDs at end of customer portal URL). Although, Service Desk ID and Portal ID will match most of the time, however, we have in fact seen cases where Service Desk ID and Portal ID don't exactly match.

      Response of existing GET /rest/servicedeskapi/servicedesk typically looks like this:

      "size":2,
         "start":0,
         "limit":50,
         "isLastPage":true,
         "_links":{  
            "base":"http://localhost:8008",
            "context":"",
            "self":"http://localhost:8008/rest/servicedeskapi/servicedesk"
         },
         "values":[  
            {  
               "id":"3",
               "projectId":"10401",
               "projectName":"HELP",
               "projectKey":"HELP",
               "_links":{  
                  "self":"http://localhost:8008/rest/servicedeskapi/servicedesk/3"
               }
            },
            {  
               "id":"1",
               "projectId":"10200",
               "projectName":"Service Desk",
               "projectKey":"SD",
               "_links":{  
                  "self":"http://localhost:8008/rest/servicedeskapi/servicedesk/1"
               }
            }
         ]
      }
      

      It's very easy for a user to assume that the Servicedesk IDs here will always correspond to the portal Id seen from the URL when browsing customer portals, and may blindly rely on using the IDS returned by the existing GET /servicedesk API, which would fail when those ids don't coincide with portal ids. There is no database or API constraint to enforce IDs on ao_54307e_servicedesk table to be same as actual portal IDs seen from the UI or URL.

      Suggested Solution

      Either list all portal IDs corresponding to each Servicedesk in this same API, or provide a different API to retrieve list of portals specifically including the portal IDs.

      Workaround

      No workaround known at this time. This space will be updated when we have a workaround.

      Note

      The actual portal ids match ids on ao_54307e_viewport table in the database.

            [JSDSERVER-6463] Provide API to retrieve Portal IDs

            Thiago Masutti made changes -
            Remote Link Original: This issue links to "JSDS-6261 (Bulldog)" [ 484027 ] New: This issue links to "JSMDC-6261 (JIRA Server (Bulldog))" [ 484027 ]
            Aliaksei Melnikau (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 490999 ]
            Aliaksei Melnikau (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 490972 ]
            Aliaksei Melnikau (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 490972 ]
            Aliaksei Melnikau (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 490949 ]
            Przemyslaw Czuj (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Aidan Goldthorpe made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 489900 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            Aidan Goldthorpe made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Aidan Goldthorpe made changes -
            Fix Version/s New: 4.10.0 [ 91825 ]

              agoldthorpe Aidan Goldthorpe
              takindele Taiwo Akindele (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: