`jira_user` only listing first 50 entries about steampipe-plugin-jira HOT 4 CLOSED

@LalitTurbot If this table has a pagination issue, do others have the same issue as well?

from steampipe-plugin-jira.

@cbruno10 will verify other tables too for paging while working on fix for it

from steampipe-plugin-jira.

@LalitTurbot Thanks for looking into this issue earlier today. Based on our initial findings, there appear to be 2 blockers:

• The users API doesn't return filtering fields in its responses, which makes implementing pagination client side difficult
• When listing users with the maxResults (default 50) request parameter, the maximum value for that parameter is 1000

For the first issue, it seems like pagination isn't available for users in the Jira API. For instance, when attempting to get users from the API using curl:

curl --request GET \
  --url 'https://myjira-jira.atlassian.net/rest/api/2/users?startAt=0&maxResults=2' \  
  --user '[email protected]:...' \
  --header 'Accept: application/json'

The API returns the response:

[
  {
    "self": "https://myjira-jira.atlassian.net/rest/api/2/user?accountId=...",
    "displayName": "Lalit Bhardwaj",
    ...
  },
  {
    "self": "https://myjira-jira.atlassian.net/rest/api/2/user?accountId=...",
    "displayName": "Automation for Jira",
    ...
  }
]

This response is different from other APIs' responses in that it doesn't contain expected fields like startAt, total, or next, e.g.,

curl --request GET \
  --url 'https://myjira-jira.atlassian.net/rest/api/2/dashboard?startAt=0&maxResults=2' \
  --user '[email protected]:...' \
  --header 'Accept: application/json'

{
  "startAt": 0,
  "maxResults": 2,
  "total": 3,
  "next": "https://myjira-jira.atlassian.net/rest/api/2/dashboard?maxResults=2&startAt=2",
  "dashboards": [
    {
      "id": "10000",
      "isFavourite": false,
      "name": "Default dashboard",
      ...
    },
    {
      "id": "10001",
      "isFavourite": true,
      "name": "Lalit",
      ...
    }
  ]
}

These are the fields that allow us to implement paging client side, but unfortunately missing when listing users. This was mentioned in JRASERVER-65089.

For the second issue, we can use the maxResults request parameter, but that appears to be capped at 1000 users, so only 1000 users max would be returned. We're still currently doing some testing from our side, but if this is the case, then it could require another workaround from our side to ensure that we can retrieve all of the users.

from steampipe-plugin-jira.

For the record, I'm on Jira Cloud (and that JRASERVER-65089 bug is for Jira Server). Probably not helpful, but thought I'd mention it.

from steampipe-plugin-jira.