fix(jira): check if issues field is defined in response (#214)

Co-authored-by: Niklas Aronsson <niklasar@axis.com>

.changeset/bright-singers-retire.md

@@ -0,0 +1,5 @@
+---
+'@axis-backstage/plugin-jira-dashboard-common': patch
+---
+
+Set issues field as optional in JiraResponse

.changeset/hungry-spiders-shop.md

@@ -0,0 +1,5 @@
+---
+'@axis-backstage/plugin-jira-dashboard': patch
+---
+
+Check if the `issues` field is set before use

plugins/jira-dashboard-common/api-report.md

@@ -54,7 +54,7 @@ export type JiraDataResponse = {
   name: string;
   query?: string;
   type: 'component' | 'filter';
-  issues: Issue[];
+  issues?: Issue[];
 };
 
 // @public

plugins/jira-dashboard-common/src/types.ts

@@ -47,7 +47,7 @@ export type JiraDataResponse = {
   name: string;
   query?: string;
   type: 'component' | 'filter';
-  issues: Issue[];
+  issues?: Issue[];
 };
 
 /**

plugins/jira-dashboard/src/components/JiraTable/JiraTable.tsx

@@ -52,7 +52,7 @@ export const JiraTable = ({
     );
   }
 
-  transformAssignees(tableContent.issues);
+  transformAssignees(tableContent?.issues || []);
 
   const nbrOfIssues = tableContent?.issues?.length ?? 0;