Releases: AxisCommunications/backstage-plugins
@axis-backstage/plugin-jira-dashboard@1.0.0
Major Changes
- 517c68a: Update default project lead name from 'key' to 'displayName' for clarity and consistency Additionally, this commit introduces provisions for displaying the image of the assignee, enhancing the user interface and providing visual context alongside the assignee's display name.
Patch Changes
@axis-backstage/plugin-jira-dashboard-common@1.0.0
Major Changes
- 517c68a: Update default project lead name from 'key' to 'displayName' for clarity and consistency Additionally, this commit introduces provisions for displaying the image of the assignee, enhancing the user interface and providing visual context alongside the assignee's display name.
@axis-backstage/plugin-jira-dashboard-backend@1.0.0
Major Changes
-
9456530: Updated the getIssuesByFilter function to accept an array of components,
enabling the construction of more flexible JQL queries.
Introduced a new variable named componentQuery to represent the portion of the JQL query related to components.Enhanced the getIssuesFromFilters function to include support for filtering by components.
Now, along with project keys and filters, the function also accepts an array of components.
This change allows for more comprehensive filtering options when retrieving issues from Jira.Modified the router implementation to pass the array of components to the getIssuesFromFilters function.
By including components in the request, users can now specify additional criteria for filtering Jira issues,
resulting in more refined search results.The introduced changes provide users with greater flexibility and control when retrieving Jira issues,
allowing for more precise filtering based on project keys, components, and filter criteria.
This enhancement improves the overall usability and effectiveness of the Jira integration functionality.
Patch Changes
- Updated dependencies [517c68a]
- @axis-backstage/plugin-jira-dashboard-common@1.0.0
@axis-backstage/plugin-jira-dashboard-backend@0.7.4
Patch Changes
- f23bacd: added content type header to searchJira call
@axis-backstage/plugin-jira-dashboard@0.7.4
Patch Changes
- f3203e9: Fix dependencies in published packages
@axis-backstage/plugin-jira-dashboard-backend@0.7.3
Patch Changes
- f3203e9: Fix dependencies in published packages
@axis-backstage/plugin-statuspage@0.3.2
Patch Changes
- 60b6270: Fix broken release
@axis-backstage/plugin-jira-dashboard-backend@0.7.0
Minor Changes
-
135e3b2: Updated the resolveUserEmailSuffix function to utilize config.getOptionalString method, providing a more concise approach. This modification ensures that an empty string is returned if the Jira user email suffix configuration is missing, effectively preventing failures and enhancing error logging capabilities.
Modified the retrieval of project keys in the router module to handle multiple project keys specified in annotations for e.g., jira.com/project-key: abc,def,ghi
The updated logic now parses multiple project keys properly and supports comma-separated values. It's important to note that in cases where multiple project keys are present, only the first project key (projectKey[0]) is used for display on the project card i.e, in this case project-key "abc", assuming it represents the main project. However, the response table will include data from all project keys specified in the annotations.
@axis-backstage/plugin-statuspage@0.3.1
Patch Changes
- 73b296f: Better README and small UI-fixes