# Comments :: Get ## Summary Retrieves a paginated array of Comment objects for a specific JIRA issue using the asynchronous request queue. Retries are handled automatically. ## Action Inputs | Label | Name | Type | Mandatory | Description | | ----------------- | ------------------ | ------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connector | connector | Reference (Reference: Jira Connector) | No | \[optional] The sys\_id of the connector to use (If none specified, the default connector is used) | | Issue ID or Key | issue\_id\_or\_key | String | No | The JIRA issue ID or Key of the issue to retrieve | | Start At | start\_at | Integer | No | \[optional] Where to start the pagination within the entire list of comments for the issue. (Default is 0) | | Max Results | max\_results | Integer | No | \[optional] How many results to return. If not specified, the framework's default value is used | | Order By | order\_by | String | No | \[optional] Which attribute to use when ordering the comments. In most JIRA versions, the only attribute currently supported is created. (default: N/A) | | Sort Direction | sort\_direction | Choice | No | \[optional] If an Order By attribute is specified, this will be the direction by which its data is sorted. | | Execute ASAP | execute\_asap | True/False | No | Whether to run this as an asynchronous business rule when the record gets created or wait for the job to pick it up in relative order on the queue | | Expansion Options | expansion\_options | String | No | \[optional] Comma separate list of attributes of the Issue that are typically hidden in responses (In most versions of JIRA, this is limited to renderedBody) | ## Action Outputs | Label | Name | Type | Mandatory | Description | | -------------------------- | --------------- | ------------------------------------------ | --------- | ------------------------------------------------------------------------------------------- | | Request | request | Reference (Reference: Async Request Queue) | No | The original asynchronous request queue record used to make the request | | Success | success | True/False | No | Whether the communication and response was as expected | | Log | log | String | No | Scripted log statements of activities that took place during the operation of this activity | | Retry Request | retry\_request | Reference (Reference: Async Request Queue) | No | If there were Retries used in the process, the last retry record is returned | | Comments JSON | comments\_json | JSON | No | The resulting JSON representation of the JIRA Comments | | Number of Results Returned | num\_returned | Integer | No | The number of comments returned in this request | | Has Next Page | has\_next | True/False | No | If there are more paginated results beyond this set, then this value is true. | | Next Starting Index | next\_start\_at | Integer | No | The Start At index for the next set of paginated results. | | Comments | comments | String | No | An Array of Comment objects | ## Notes * This action belongs to the **JIRA Request Queue** category. * This action includes reference fields that link to other tables in ServiceNow: * references the table. * This action returns 9 output(s) that can be used in subsequent flow steps. ## Example Usage ### Example 1: Basic Usage This example demonstrates how to use the action with typical inputs. **Input:** **Output:** In this example, the action processes the provided inputs and returns the appropriate outputs. The actual values returned will depend on the specific functionality of this action and the input values provided. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.yansalabs.com/jira-integration-framework/technical-docs/spoke-actions/comments-get.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.