Closed pdecat closed 2 years ago
@pdecat Thanks for reporting this issue! Sorry, it's taken so long for us to respond, we missed this issue when it was first opened.
We've identified below additional key columns:
issue_id
, issue_key
, project_key
, project_id
, project_name
, status
, assignee_display_name
, assignee_display_name
, creator_account_id
, creator_display_name
, reporter_account_id
, reporter_display_name
, created
, duedate
, updated
, epic_key
, type
and priority
.
We'll start work on adding these this week, and they should be ready later early next week in a new plugin version.
Describe the bug
When querying issues, no filter is passed to the API and all issues are requested from the JIRA API.
With a large number of issues, this can take a very long time, and maybe never succeed.
I had to add traces to the plugin to understand what was going on:
Steampipe version (
steampipe -v
)v0.12.2
Plugin version (
steampipe plugin list
)v0.1.0
To reproduce
Relevant code is https://github.com/turbot/steampipe-plugin-jira/blob/v0.1.0/jira/table_jira_issue.go#L221-L225
Expected behavior
A filter should be added to the JIRA API request to avoid retrieving all issues.
Additional context N/A