Add Jira Dashboard plugin

[fridajac]

Hey, I just made a Pull Request!

This PR adds the Jira Dashboard plugin. The plugin is a Jira issue overview that can be added as a page in the EntityPage overview tabs. The issue view displays issue summaries to help achieve better task visibility and more efficient project management.

Information that this plugin provides:

• The Jira project that is relevant for that entity, with information about the project name, key, category, description, project lead, and avatar.
• Jira issues and their type, key, summary, status, and assignee.
• By default, the issue views that are provided are incoming issues, open issues and assigned to you. You can also customise the view to display the information relevant for your entity by defining Jira filters and components.

Isn’t there already a Jira plugin?

Yes, Roadie is one of the main Backstage contributors and offers the Backstage Jira plugin. This plugin also provides information from Jira, such as project and project type.

However, Roadie’s Backstage Jira plugin focuses on exposing the quantity of different issue types and the project activity stream. The new Jira Dashboard plugin in this PR takes a different approach, displaying issues in tables. In addition, the Jira Dashboard plugin provides the possibility of linking not only a Jira project, but also specific Jira components and filters to your entities.

Changes:

• Backend: Added the Jira Dashboard backend plugin
• Frontend: Added the Jira Dashboard frontend plugin

✔️ Checklist

• 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)
• All your commits have a Signed-off-by line in the message. (more info)

[backstage-goalie]

Missing Changesets

The following package(s) are changed by this PR but do not have a changeset:

• @backstage/plugin-jira-dashboard-backend
• @backstage/plugin-jira-dashboard-common

See CONTRIBUTING.md for more information about how to add changesets.

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
example-app	packages/app	none	v0.2.88-next.0
example-backend-next	packages/backend-next	none	v0.0.16-next.0
example-backend	packages/backend	none	v0.2.88-next.0
@backstage/plugin-jira-dashboard-backend	plugins/jira-dashboard-backend	none	v0.0.0
@backstage/plugin-jira-dashboard-common	plugins/jira-dashboard-common	none	v0.0.0
@backstage/plugin-jira-dashboard	plugins/jira-dashboard	minor	v0.0.0

[awanlin]

Thanks for following up on my previous comments, this is looking really solid now @fridajac 🚀

I left one comment around ownership in the catalog-info.yaml files and related CODEOWNERS file

[awanlin]

Just going to say this again but awesome work @fridajac, approving based on my review 🚀

[fridajac]

Just going to say this again but awesome work @fridajac, approving based on my review 🚀

Thank you! And thanks for all your help and feedback :)

[freben]

This is fantastic work! Really only the codeowners command and secret marker that are important, the rest is more informative and can be skipped if you want to soldier through.

Thanks also @awanlin for all your help!

[GLundh]

@freben : Is this blocked by #20266?

[freben]

Not in the sense that the RFC is what's been holding it back until now - I'm just slowly working through some reviews. But thanks for bringing it up though, because it became top of mind as late as today actually. Might as well start the discussion. Is there some possibility of having this entire plugin maintained off-repo? It'd bring significant benefits in terms of being unblocked from our review loop, if nothing else.

Since this is so far gone and ready, and you gut unfortunately stranded mid-RFC, I could perhaps consider merging this and then awaiting the processing of moving it out later on. But it'd of course lead to churn where you would probably have to deprecate this particular package on the @backstage prefix, and replacing it with a new one.

[fridajac]

We had a discussion yesterday and decided that yes, since we will have to move out this plugin later anyway, we might just publish the plugin off-repo from the start. So I'll close this pull request. Thank you for all your help and comments @freben @awanlin @vinnie-jog-on, very appreciated, really made the plugin better :)

[freben]

Awesome, thanks for your patience in this. Hopefully the reviews were useful in the mean time! And of course, we're more than happy to surface your work in the plugin list etc.