@pipedream/jira_service_desk 2.3.0 → 2.4.0

package/actions/create-comment-on-request/create-comment-on-request.mjs

@@ -4,7 +4,7 @@ export default {
   key: "jira_service_desk-create-comment-on-request",
   name: "Create Comment on Request",
   description: "Create a comment on a customer request. [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-comment-post)",
-  version: "0.1.4",
+  version: "0.1.5",
   annotations: {
     destructiveHint: false,
     openWorldHint: true,

package/actions/create-request/create-request.mjs

@@ -15,7 +15,7 @@ export default {
     + " Optionally attach one or more files at creation time via `attachments`; to add, replace, or delete attachments on a request that already exists, use **Manage Request Attachment** instead."
     + " Returns the created request including its `issueKey` and `issueId`. If `attachments` is set, the response also includes either an `attachments` array (on success) or an `attachmentError` string (if the request was created but the attachment step failed) — the request itself is never rolled back because of an attachment failure."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-post)",
-  version: "1.1.0",
+  version: "1.1.1",
   annotations: {
     destructiveHint: false,
     openWorldHint: true,
@@ -69,13 +69,13 @@ export default {
     requestParticipants: {
       type: "string[]",
       label: "Request Participants",
-      description: "Atlassian account IDs to add as participants, e.g. `[\"5b10a2844c20165700ede21g\"]`. Not available to users who only have the Service Desk Customer permission, or if the feature is turned off for customers.",
+      description: "Atlassian account IDs to add as participants, e.g. `[\"5b10a2844c20165700ede21g\"]`. Run **Find Users** to turn each name or email address into an `accountId`; participants are often approvers or managers who are not customers of this desk, which is why this uses the site-wide search rather than **Find Service Desk Customers**. Not available to users who only have the Service Desk Customer permission, or if the feature is turned off for customers.",
       optional: true,
     },
     raiseOnBehalfOf: {
       type: "string",
       label: "Raise On Behalf Of",
-      description: "Atlassian account ID of the customer to raise this request for, e.g. `5b10a2844c20165700ede21g`. Not available to users who only have the Service Desk Customer permission.",
+      description: "Atlassian account ID of the customer to raise this request for, e.g. `5b10a2844c20165700ede21g`. Run **Find Service Desk Customers** with this same Service Desk ID to turn a name or email address into an `accountId`, which also confirms the person is a customer of this desk; fall back to **Find Users** if they are not found there. A desk that restricts who may be one of its customers can reject a reporter who is not, so if creation then fails on the reporter field, retry without this field and name the requester in the description instead. Never guess an ID, and never pass a name or email address here. Not available to users who only have the Service Desk Customer permission.",
       optional: true,
     },
     form: {

package/actions/download-issue-attachment/download-issue-attachment.mjs

@@ -12,7 +12,7 @@ export default {
   key: "jira_service_desk-download-issue-attachment",
   name: "Download Issue Attachment",
   description: "Download the binary content of a Jira Service Desk attachment to the file-stash directory, returning the saved path plus the attachment metadata (`filename`, `mimeType`, `size`). Run **List Issue Attachments** first to obtain the attachment `id`, then pass both it and the same `issueIdOrKey` here. Example: passing `issueIdOrKey` `IT-42` and `attachmentId` `10042` downloads `screenshot.png` to `/tmp/10042-screenshot.png` and returns `{ \"filedata\": [\"10042-screenshot.png\", \"/tmp/10042-screenshot.png\"], \"attachment\": { \"id\": \"10042\", \"filename\": \"screenshot.png\", \"mimeType\": \"image/png\", \"size\": 84213 } }`. [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-attachment-attachmentid-get)",
-  version: "0.0.3",
+  version: "0.0.4",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/find-service-desk-customers/find-service-desk-customers.mjs

@@ -0,0 +1,102 @@
+import app from "../../jira_service_desk.app.mjs";
+
+export default {
+  key: "jira_service_desk-find-service-desk-customers",
+  name: "Find Service Desk Customers",
+  description:
+    "Finds the customers of one service desk by name or email address and returns the `accountId` of each match."
+    + " **Pick this tool when the person is the one the ticket is being raised for on a service desk you can identify**, i.e. to fill `raiseOnBehalfOf` on **Create Request**."
+    + " Natural-language cues: \"raise a ticket for Jean on the IT desk\", \"open a request on behalf of john@acme.com\", \"file this for my colleague Dana\", \"submit a hardware request for the new starter\"."
+    + " Pick **Find Users** instead when the person does not have to be a customer of this desk, such as an approver, manager, or agent you are adding to `requestParticipants`, or when you cannot tell which service desk applies."
+    + " Prefer this tool wherever both would work: it searches only this desk's customer list, so a match proves the person can actually raise a request here, and bot accounts are excluded (a site-wide search on a live site returned 17 users of which 16 were integrations)."
+    + " Use **List Sites** for `cloudId` and **List Service Desks** for `serviceDeskId` first."
+    + " Worked example: for \"open a laptop request for Joseph Wilson on the IT desk\", call this with Service Desk ID `1` and Query `Joseph Wilson`, read `accountId` `5b10a2844c20165700ede21g` off the single match, then call **Create Request** with Service Desk ID `1` and that `accountId` as `raiseOnBehalfOf`."
+    + " Omit Query to list every customer of the desk, which answers \"who can raise requests on this desk?\"."
+    + " Query is matched against `displayName` and `emailAddress`, and matches more than just the start of them. Pass a full name or a full email address to keep the result set tight."
+    + " If nobody matches, the person may exist on the site without being a customer of this desk, retry with **Find Users**."
+    + " Results are paginated automatically up to `maxResults`."
+    + " Returns `{ users, truncated }`, where `truncated` is `true` when more matches remained unfetched."
+    + " `accountId` is the only field guaranteed present: Atlassian's profile visibility rules hide `emailAddress` on users who have not made it public, so match on `displayName` and never require an email to be returned."
+    + " An unknown or inaccessible Service Desk ID fails with a 404 rather than returning an empty list, so an empty list really does mean nobody matched."
+    + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-servicedesk/#api-rest-servicedeskapi-servicedesk-servicedeskid-customer-get)",
+  version: "0.0.1",
+  type: "action",
+  ai: "optimized",
+  annotations: {
+    destructiveHint: false,
+    openWorldHint: true,
+    readOnlyHint: true,
+  },
+  props: {
+    app,
+    cloudId: {
+      propDefinition: [
+        app,
+        "cloudId",
+      ],
+    },
+    serviceDeskId: {
+      propDefinition: [
+        app,
+        "serviceDeskId",
+      ],
+      description: "The service desk whose customers to search, e.g. `1`. Run **List Service Desks** to map a project name or key to its ID. Use the same ID you will pass to **Create Request**, so the match is checked against the desk the ticket will actually be raised on.",
+    },
+    query: {
+      propDefinition: [
+        app,
+        "query",
+      ],
+      description: "Name or email address to search for, e.g. `Joseph Wilson` or `joseph@example.com`. Matched against `displayName` and `emailAddress`. Omit to list every customer of the desk.",
+      optional: true,
+    },
+    maxResults: {
+      propDefinition: [
+        app,
+        "maxResults",
+      ],
+      description: "Maximum number of customers to return across all pages (1-1000).",
+    },
+  },
+  async run({ $ }) {
+    const {
+      app,
+      cloudId,
+      serviceDeskId,
+      query,
+      maxResults,
+    } = this;
+
+    const {
+      results, hasMore,
+    } = await app.searchServiceDeskCustomers({
+      $,
+      cloudId,
+      serviceDeskId,
+      query,
+      maxResults,
+    });
+
+    // Dropping the avatar URLs and `_links` the raw payload carries.
+    const users = results.map(({
+      accountId, displayName, emailAddress, active,
+    }) => ({
+      accountId,
+      displayName,
+      emailAddress,
+      active,
+    }));
+
+    $.export("$summary", `Found ${users.length} customer${users.length === 1
+      ? ""
+      : "s"} on service desk ${serviceDeskId}${query
+      ? ` matching "${query}"`
+      : ""}${hasMore
+      ? ", truncated at Max Results; raise it to fetch more"
+      : ""}`);
+    return {
+      users,
+      truncated: hasMore,
+    };
+  },
+};

package/actions/find-users/find-users.mjs

@@ -0,0 +1,93 @@
+import app from "../../jira_service_desk.app.mjs";
+import constants from "../../common/constants.mjs";
+
+export default {
+  key: "jira_service_desk-find-users",
+  name: "Find Users",
+  description:
+    "Finds any active user on an Atlassian site by name or email address and returns the `accountId` of each match."
+    + " **Pick this tool when the person does not have to be a customer of one particular service desk**, i.e. to fill `requestParticipants` on **Create Request** with an approver, manager, watcher, or agent, or when the user names somebody but no service desk is known yet."
+    + " Natural-language cues: \"add my manager Dana as a participant\", \"cc the security lead on this ticket\", \"loop in john@acme.com\", \"what is the account ID for Jean?\"."
+    + " Pick **Find Service Desk Customers** instead when you already know the service desk and the person is the one the ticket is being raised for (`raiseOnBehalfOf`). That tool is more precise, confirms the person can actually raise a request on that desk, and excludes bots."
+    + " Use **List Sites** first to obtain the required `cloudId`."
+    + " Worked example: for \"open a laptop request and add Dana Lee as a participant\", call this with Query `Dana Lee`, read `accountId` `5b10a2844c20165700ede21g` off the match whose `accountType` is `atlassian`, then pass `[\"5b10a2844c20165700ede21g\"]` as `requestParticipants` on **Create Request**."
+    + " Most users on a Jira site are bots, not people. Integrations come back as ordinary matches carrying `accountType` `app`, so read `accountType` and use only `atlassian` accounts as `raiseOnBehalfOf` or `requestParticipants`."
+    + " Query is matched against `displayName` and `emailAddress`, and matches more than just the start of them. Pass a full name or a full email address to keep the result set tight."
+    + " Results are paginated automatically up to `maxResults`."
+    + " Returns `{ users, truncated }`. `truncated` is `true` when the result set may be incomplete, either because more matches remained unfetched or because collection stopped at Atlassian's 1000-match limit, which looks the same whether or not further matches exist. Once you have 1000 matches, narrow the query rather than raising `maxResults`, which cannot go higher."
+    + " `accountId` is the only field guaranteed present: Atlassian's profile visibility rules hide `emailAddress` on users who have not made it public, so match on `displayName` and never require an email to be returned."
+    + " An empty `users` list means either nobody matched or the connected account lacks the \"Browse users and groups\" global permission, which Atlassian reports as zero results rather than as an error."
+    + " [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-search/#api-rest-api-3-user-search-get)",
+  version: "0.0.1",
+  type: "action",
+  ai: "optimized",
+  annotations: {
+    destructiveHint: false,
+    openWorldHint: true,
+    readOnlyHint: true,
+  },
+  props: {
+    app,
+    cloudId: {
+      propDefinition: [
+        app,
+        "cloudId",
+      ],
+    },
+    query: {
+      propDefinition: [
+        app,
+        "query",
+      ],
+    },
+    maxResults: {
+      propDefinition: [
+        app,
+        "maxResults",
+      ],
+      description: "Maximum number of users to return across all pages (1-1000).",
+    },
+  },
+  async run({ $ }) {
+    const {
+      app,
+      cloudId,
+      query,
+      maxResults,
+    } = this;
+
+    const {
+      results, hasMore,
+    } = await app.searchUsers({
+      $,
+      cloudId,
+      query,
+      maxResults,
+    });
+
+    // Dropping the four avatar URLs per user the raw payload carries.
+    const users = results.map(({
+      accountId, displayName, emailAddress, active, accountType,
+    }) => ({
+      accountId,
+      displayName,
+      emailAddress,
+      active,
+      accountType,
+    }));
+
+    // At the offset ceiling raising Max Results cannot help, so say so instead.
+    const atSiteLimit = users.length >= constants.USER_SEARCH_MAX_OFFSET;
+    $.export("$summary", `Found ${users.length} user${users.length === 1
+      ? ""
+      : "s"} on the site matching "${query}"${hasMore
+      ? atSiteLimit
+        ? ", stopped at Atlassian's 1000-match limit; narrow the query to check for more"
+        : ", truncated at Max Results; raise it to fetch more"
+      : ""}`);
+    return {
+      users,
+      truncated: hasMore,
+    };
+  },
+};

package/actions/get-current-user/get-current-user.mjs

@@ -8,7 +8,7 @@ export default {
     + " Use this to identify who is logged in, or to filter requests by the current user's `account_id`."
     + " No `cloudId` required — this uses the Atlassian Identity API directly."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/)",
-  version: "0.0.7",
+  version: "0.0.8",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/get-request/get-request.mjs

@@ -10,7 +10,7 @@ export default {
     + " Use **List Sites** first to obtain the required `cloudId`."
     + " Use **List My Requests** to find the `issueKey` of a request (e.g. `IT-42`)."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-get)",
-  version: "0.2.4",
+  version: "0.2.5",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/get-request-status/get-request-status.mjs

@@ -11,7 +11,7 @@ export default {
     + " Use **List Sites** first to obtain the required `cloudId`."
     + " Use **List My Requests** to find the `issueKey` (e.g. `IT-42`)."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-status-get)",
-  version: "1.1.4",
+  version: "1.1.5",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-cloud-id-options/list-cloud-id-options.mjs

@@ -4,7 +4,7 @@ export default {
   key: "jira_service_desk-list-cloud-id-options",
   name: "List Cloud ID Options",
   description: "Lists the Atlassian sites you can raise requests on, as `{label, value}` options, to discover the `cloudId` every other Jira Service Desk tool needs. Takes no input beyond the account. Example: returns `[{ \"label\": \"acme\", \"value\": \"822faf0d-5427-420e-9016-999d3dc76918\" }]`. Use **List Sites** instead if you want the full site records. [See the documentation](https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/#3-1-get-the-cloudid-for-your-site)",
-  version: "0.1.3",
+  version: "0.1.4",
   type: "action",
   annotations: {
     destructiveHint: false,

package/actions/list-issue-attachments/list-issue-attachments.mjs

@@ -5,7 +5,7 @@ export default {
   key: "jira_service_desk-list-issue-attachments",
   name: "List Issue Attachments",
   description: "List metadata for every attachment on a Jira Service Desk request. `issueIdOrKey` accepts either a Jira issue key (e.g. `IT-42`) or a numeric Jira issue ID (e.g. `10001`). Results are paginated automatically up to `maxResults`. Returns `{ attachments, truncated }`, where each attachment includes `id`, `filename`, `size` (bytes), `mimeType`, and `content` (an opaque reference URL whose exact shape varies by account access level and is **not** directly fetchable through this connection's authentication), and `truncated` is `true` when more attachments remained unfetched. Use **Download Issue Attachment** with an attachment `id` and the same `issueIdOrKey` to fetch the binary content — do not call `content` directly. If this connection has customer-level access rather than agent access, only public attachments are returned; internal attachments exist but won't appear here. Returns `{ attachments: [], truncated: false }` (no error) when the request exists but has no visible attachments. Example: issue `IT-42` with one attachment returns `{ \"attachments\": [{ \"id\": \"10042\", \"filename\": \"screenshot.png\", \"size\": 84213, \"mimeType\": \"image/png\", \"content\": \"<opaque reference URL>\" }], \"truncated\": false }`. [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-attachment-get)",
-  version: "0.0.3",
+  version: "0.0.4",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-my-requests/list-my-requests.mjs

@@ -13,7 +13,7 @@ export default {
     + " `requestStatus`: `OPEN_REQUESTS` (default), `CLOSED_REQUESTS`, or `ALL_REQUESTS`."
     + " `requestOwnership`: `OWNED_REQUESTS` (default) or `PARTICIPATED_REQUESTS`."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-get)",
-  version: "1.1.4",
+  version: "1.1.5",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-request-transitions/list-request-transitions.mjs

@@ -11,7 +11,7 @@ export default {
     + " Use **List Sites** first to obtain the required `cloudId`."
     + " Use **List My Requests** or **Get Request** to find the `issueKey` (e.g. `IT-42`)."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-transition-get)",
-  version: "1.1.4",
+  version: "1.1.5",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-request-type-fields/list-request-type-fields.mjs

@@ -11,7 +11,7 @@ export default {
     + " Also returns `canRaiseOnBehalfOf` and `canAddRequestParticipants`, which tell you whether the `raiseOnBehalfOf` and `requestParticipants` arguments of **Create Request** are usable with this account."
     + " Hidden fields are only visible to service desk administrators."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-servicedesk/#api-rest-servicedeskapi-servicedesk-servicedeskid-requesttype-requesttypeid-field-get)",
-  version: "0.0.5",
+  version: "0.0.6",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-request-types/list-request-types.mjs

@@ -14,7 +14,7 @@ export default {
     + " Types with `canCreateRequest: false` cannot be used to raise a request."
     + " Then call **List Request Type Fields** to see what the chosen type requires."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-servicedesk/#api-rest-servicedeskapi-servicedesk-servicedeskid-requesttype-get)",
-  version: "0.0.5",
+  version: "0.0.6",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-service-desks/list-service-desks.mjs

@@ -11,7 +11,7 @@ export default {
     + " Returns `{ serviceDesks, truncated }`, where `truncated` is `true` when more desks remained unfetched."
     + " Example: a site with one desk returns `{ \"serviceDesks\": [{ \"id\": \"1\", \"projectName\": \"Support\", \"projectKey\": \"SUP\" }], \"truncated\": false }`."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-servicedesk/#api-rest-servicedeskapi-servicedesk-get)",
-  version: "0.0.5",
+  version: "0.0.6",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/list-sites/list-sites.mjs

@@ -8,7 +8,7 @@ export default {
     + " **Call this tool first** to obtain the `cloudId` (returned as `id`) required by every other Jira Service Desk tool."
     + " Each site includes its `id` (cloudId), `name`, and `url`."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/#3-1-get-the-cloudid-for-your-site)",
-  version: "0.0.7",
+  version: "0.0.8",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/manage-request-attachment/manage-request-attachment.mjs

@@ -15,7 +15,7 @@ export default {
     + " For `update`, if the new file attaches successfully but removing the old attachment then fails, the response includes a `deleteError` string alongside the successful attachment data — the request ends up with both files rather than losing either one, and the error is never masked as a full failure."
     + " By default the attachment is visible to the customer who raised the request (`public: true`); set `public` to `false` to attach an internal-only file."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-attachment-post)",
-  version: "0.0.1",
+  version: "0.0.2",
   annotations: {
     destructiveHint: true,
     openWorldHint: true,

package/actions/transition-request/transition-request.mjs

@@ -10,7 +10,7 @@ export default {
     + " Use **List My Requests** or **Get Request** to find the `issueKey` (e.g. `IT-42`)."
     + " Optionally include a comment to explain the transition."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-transition-post)",
-  version: "0.1.4",
+  version: "0.1.5",
   type: "action",
   ai: "optimized",
   annotations: {

package/actions/update-issue-fields/update-issue-fields.mjs

@@ -11,7 +11,7 @@ export default {
     + " `fields` is a JSON object of field name-value pairs."
     + " Example: `{\"summary\": \"Updated title\", \"priority\": {\"name\": \"High\"}}`."
     + " [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put)",
-  version: "0.1.4",
+  version: "0.1.5",
   type: "action",
   ai: "optimized",
   annotations: {

package/common/constants.mjs

@@ -7,6 +7,18 @@
 // https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/#pagination
 const PAGE_SIZE = 100;
 
+// Atlassian's documented default page size for `/rest/api/3/user/search`.
+const USER_SEARCH_PAGE_SIZE = 50;
+
+// `/rest/api/3/user/search` serves nothing past the thousandth match, and answers
+// an offset at or beyond it with an empty page whether or not more matches exist.
+const USER_SEARCH_MAX_OFFSET = 1000;
+
+// The service desk customer resource is experimental and 412s without this.
+const EXPERIMENTAL_API_HEADER = {
+  "X-ExperimentalApi": "opt-in",
+};
+
 // Ceiling on how many items a single action run will collect across pages.
 const MAX_RESULTS_DEFAULT = 100;
 const MAX_RESULTS_MIN = 1;
@@ -27,6 +39,9 @@ const MAX_ATTACHMENT_SIZE_BYTES = 2 * 1024 * 1024 * 1024;
 
 export default {
   PAGE_SIZE,
+  USER_SEARCH_PAGE_SIZE,
+  USER_SEARCH_MAX_OFFSET,
+  EXPERIMENTAL_API_HEADER,
   MAX_RESULTS_DEFAULT,
   MAX_RESULTS_MIN,
   MAX_RESULTS_MAX,

package/jira_service_desk.app.mjs

@@ -33,6 +33,11 @@ export default {
       label: "Issue ID or Key",
       description: "The ID or key of the Jira Service Desk request (e.g. `IT-42` or `10001`). Use **List My Requests** to find the `issueKey` of a request (in its `requests` array).",
     },
+    query: {
+      type: "string",
+      label: "Query",
+      description: "Name or email address to search for, e.g. `Joseph Wilson` or `joseph@example.com`. Matched against `displayName` and `emailAddress`. A full name or full email address gives the tightest result set.",
+    },
     maxResults: {
       type: "integer",
       label: "Max Results",
@@ -73,7 +78,7 @@ export default {
      * items and whether the API still had more to give when collection stopped.
      */
     async _paginate({
-      $, path, params, maxResults = constants.MAX_RESULTS_DEFAULT,
+      $, path, params, headers, maxResults = constants.MAX_RESULTS_DEFAULT,
     }) {
       const results = [];
       let start = 0;
@@ -83,6 +88,7 @@ export default {
         const response = await this._makeRequest({
           $,
           path,
+          headers,
           params: {
             ...params,
             start,
@@ -173,6 +179,61 @@ export default {
         path: `/ex/jira/${cloudId}/rest/servicedeskapi/request/${requestId}/comment`,
       });
     },
+    // Site-wide user search. Returns a bare array, not the `values`/`isLastPage`
+    // envelope `_paginate` expects, so it pages by offset here instead.
+    async searchUsers({
+      $, cloudId, query, maxResults = constants.MAX_RESULTS_DEFAULT,
+    }) {
+      const results = [];
+      let startAt = 0;
+      // One row past the cap separates "cap equals match count" from "more exist".
+      const ceiling = maxResults + 1;
+
+      while (results.length < ceiling) {
+        const limit = Math.min(
+          ceiling - results.length,
+          constants.USER_SEARCH_PAGE_SIZE,
+        );
+        const users = await this._makeRequest({
+          $,
+          path: `/ex/jira/${cloudId}/rest/api/3/user/search`,
+          params: {
+            query,
+            startAt,
+            maxResults: limit,
+          },
+        });
+
+        // Only an empty page ends it: a short page may just be a clamped page.
+        if (!users?.length) {
+          break;
+        }
+
+        results.push(...users);
+        startAt += users.length;
+      }
+
+      return {
+        results: results.slice(0, maxResults),
+        // Reaching Atlassian's offset ceiling is indistinguishable from running out
+        // of matches, so report it as more-to-come rather than claim completeness.
+        hasMore: results.length > maxResults
+          || startAt >= constants.USER_SEARCH_MAX_OFFSET,
+      };
+    },
+    async searchServiceDeskCustomers({
+      $, cloudId, serviceDeskId, query, maxResults,
+    }) {
+      return this._paginate({
+        $,
+        path: `/ex/jira/${cloudId}/rest/servicedeskapi/servicedesk/${serviceDeskId}/customer`,
+        params: {
+          query,
+        },
+        headers: constants.EXPERIMENTAL_API_HEADER,
+        maxResults,
+      });
+    },
     async getCurrentUser({ $ } = {}) {
       return this._makeRequest({
         $,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pipedream/jira_service_desk",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "description": "Pipedream Jira Service Desk Components",
   "main": "jira_service_desk.app.mjs",
   "keywords": [

package/sources/new-request-created/new-request-created.mjs

@@ -6,7 +6,7 @@ export default {
   name: "New Request Created",
   description:
     "Emit new event when a customer request is created. [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/#api-rest-servicedeskapi-request-get)",
-  version: "0.1.3",
+  version: "0.1.4",
   type: "source",
   dedupe: "unique",
   methods: {

package/sources/request-status-updated/request-status-updated.mjs

@@ -6,7 +6,7 @@ export default {
   name: "Request Status Updated",
   description:
     "Emit new event when a customer request is updated. [See the documentation](https://developer.atlassian.com/cloud/jira/service-desk/rest/#api-rest-servicedeskapi-request-get)",
-  version: "0.1.3",
+  version: "0.1.4",
   type: "source",
   dedupe: "unique",
   methods: {