Closed alex-mckay closed 3 months ago
Latest commit: 0d3aa8940495e725abf1058975099cf44f7eeacd
The changes in this PR will be included in the next version bump.
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
Hi @fridajac - would appreciate a review/any feedback here whenever you have time!
Hey, I just made a Pull Request!
This PR adds support for the new frontend system to the jira plugin by exposing the entity content & API as extensions under the '/alpha' subpath. This change is fully back-compatible & has no affect on consumers who are still using the standard frontend system.
One small frontend change is in the case where the relevant annotation is missing, the JiraDashboardContent React element will now render the missing annotation screen instead of the error boundary. This is to facilitate a better frontend experience in the new frontend system, where the tab's appearance cannot (yet) be conditional on annotation values. It will be a no-op if one is using the old frontend and couched EntityJiraDashboardContent inside an if block with isJiraDashboardAvailable per the documentation.
=>
If the request to itself jira-backend fails, there's no change in behavior.
Context
Spotify will be updating OSS plugins to the new frontend & backend as we work towards an updated Backstage plugin framework. We're prioritizing some community favorites first, and the Spotify team will help manage any unintentional issues that arise!
Issue ticket number and link
Checklist before requesting a review