forked from AxisCommunications/backstage-plugins
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Enhanced Jira integration to support filtering by components in JQL q…
…ueries
- Loading branch information
1 parent
c108b55
commit 7384a0d
Showing
4 changed files
with
38 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
'@axis-backstage/plugin-jira-dashboard-backend': major | ||
--- | ||
|
||
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters