roadie-backstage-plugins: Backstage jira proxy's URL with undefined as project value

Hi everyone.

I’m currently testing Backstage for my company, and I tried various integrations like Github, Jira, Jenkins and more. But I’m facing an issue with the Jira plugin. Maybe it’s just a bad setup.

I already search any hint to help me to fix this, but all those places are a copy/paste of the jira plug-in’s README.

Expected Behavior

I guess the URL for the proxy should be “http://localhost:7007/api/proxy/jira/api/rest/api/latest/project/{PROJECT_KEY}

Current Behavior

In my component, I can see the Jira entity, but every time, it says “failed to fetch data, status 404: Not Found”. When I look in the browser’s console (network), I can see this 404, and this is the query “http://localhost:7007/api/proxy/jira/api/rest/api/latest/project/undefined”. Why do I have “undefined”? Is it because the jira/project-key variable is not at the right place? Actually it’s in the catalog-info.yaml, under metadata.

I tested my jira’s token with postman and everything seem to be ok.

Steps to Reproduce

Open any component, and check the Jira entity tosee the 404 and in the browser’s console (network) to find the url with undefined jiraEntity BrowserConsoleHeader BrowserConsoleResponse

Your Environment

Everything was cloned/installed tuesday 11 january 2022, so it should be the latest version for everything.

  • @backstage/plugin-catalog-react version: 0.6.10
  • @roadiehq/backstage-plugin-jira version: 1.4.3

If some information is missing, let me know, I will do my best to provide them.

Thanks in advance.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (5 by maintainers)

Most upvoted comments

According to this comment https://github.com/RoadieHQ/roadie-backstage-plugins/issues/375#issuecomment-1014606371 It seems.

I red again all comments to see if anything was coming back. The only thing I can say is that our issue was that we were editing the wrong file, something like that. I can’t tell much…

Hi @Irma12 Thanks for the confirmation and the documentation. Everything is ok on our side now.

I will close this issue 😃 Thanks again.