Enable Support for Multiple Jira Project Keys

[SaachiNayyer]

Hey, I just made a Pull Request!

This enhancement would be highly beneficial for users managing multiple Jira projects associated with a single entity

Context

This PR supports both single and multiple project keys. It ensures that the function can handle an array of project keys and constructs the JQL query accordingly.

Issue ticket number and link

#232

• Fixes # (issue)

Checklist before requesting a review

• I have performed a self-review of my own code
• I have verified that the code builds perfectly fine on my local system
• I have verified that my code follows the style already available in the repository
• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)

[changeset-bot]

🦋 Changeset detected

Latest commit: 0472085

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@axis-backstage/plugin-jira-dashboard-backend	Minor
backend	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[fridajac]

Can you also update the README.md in jira-dashboard to show the user how to use multiple projects?

[fridajac]

There seems to be an error when I add the optional annotation jira.com/incoming-issues-status: (https://github.com/AxisCommunications/backstage-plugins/blob/main/plugins/jira-dashboard/README.md#optional-annotations). If the submitted status, for instance Incoming, doesn't exist in the project, an error is thrown.

[SaachiNayyer]

There seems to be an error when I add the optional annotation jira.com/incoming-issues-status: (https://github.com/AxisCommunications/backstage-plugins/blob/main/plugins/jira-dashboard/README.md#optional-annotations). If the submitted status, for instance Incoming, doesn't exist in the project, an error is thrown.
Hi @fridajac
Thank you for pointing this out. I’d like to clarify my understanding to ensure we're aligned:
The jira.com/incoming-issues-status annotation should work based on the provided status and project keys. From my perspective, if a valid status is specified and corresponds to an available status in the specified Jira project(s), the query should execute correctly. If the status is not valid or doesn't exist in the specified projects, Jira should return an empty response, not throw an error.
Could you please confirm if this issue is directly related to the recent change for supporting multiple project keys? If so, any additional details or scenarios where this error occurs would help me investigate further.

[SaachiNayyer]

Can you also update the README.md in jira-dashboard to show the user how to use multiple projects?

Done

[fridajac]

There seems to be an error when I add the optional annotation jira.com/incoming-issues-status: (https://github.com/AxisCommunications/backstage-plugins/blob/main/plugins/jira-dashboard/README.md#optional-annotations). If the submitted status, for instance Incoming, doesn't exist in the project, an error is thrown.
Hi @fridajac
Thank you for pointing this out. I’d like to clarify my understanding to ensure we're aligned:
The jira.com/incoming-issues-status annotation should work based on the provided status and project keys. From my perspective, if a valid status is specified and corresponds to an available status in the specified Jira project(s), the query should execute correctly. If the status is not valid or doesn't exist in the specified projects, Jira should return an empty response, not throw an error.
Could you please confirm if this issue is directly related to the recent change for supporting multiple project keys? If so, any additional details or scenarios where this error occurs would help me investigate further.

Sure! I'll have a look at it this afternoon and get back to you 🙂

[fridajac]

There seems to be an error when I add the optional annotation jira.com/incoming-issues-status: (https://github.com/AxisCommunications/backstage-plugins/blob/main/plugins/jira-dashboard/README.md#optional-annotations). If the submitted status, for instance Incoming, doesn't exist in the project, an error is thrown.
Hi @fridajac
Thank you for pointing this out. I’d like to clarify my understanding to ensure we're aligned:
The jira.com/incoming-issues-status annotation should work based on the provided status and project keys. From my perspective, if a valid status is specified and corresponds to an available status in the specified Jira project(s), the query should execute correctly. If the status is not valid or doesn't exist in the specified projects, Jira should return an empty response, not throw an error.
Could you please confirm if this issue is directly related to the recent change for supporting multiple project keys? If so, any additional details or scenarios where this error occurs would help me investigate further.

Sure! I'll have a look at it this afternoon and get back to you 🙂

I added a comment on the specific line that is causing problems :) And yes, the backend should return an empty response, not throw an error.

[SaachiNayyer]

There seems to be an error when I add the optional annotation jira.com/incoming-issues-status: (https://github.com/AxisCommunications/backstage-plugins/blob/main/plugins/jira-dashboard/README.md#optional-annotations). If the submitted status, for instance Incoming, doesn't exist in the project, an error is thrown.
Hi @fridajac
Thank you for pointing this out. I’d like to clarify my understanding to ensure we're aligned:
The jira.com/incoming-issues-status annotation should work based on the provided status and project keys. From my perspective, if a valid status is specified and corresponds to an available status in the specified Jira project(s), the query should execute correctly. If the status is not valid or doesn't exist in the specified projects, Jira should return an empty response, not throw an error.
Could you please confirm if this issue is directly related to the recent change for supporting multiple project keys? If so, any additional details or scenarios where this error occurs would help me investigate further.

Sure! I'll have a look at it this afternoon and get back to you 🙂

I added a comment on the specific line that is causing problems :) And yes, the backend should return an empty response, not throw an error.

Thanks @fridajac, I have made the changes :)

[fridajac]

Hi again @SaachiNayyer! Please have a look at the formatting errors, and then I'll take a closer look at the PR again :)

[fridajac]

Great job! Thanks for this contribution, it's really nice. 💯