Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All Images shown as 'broken image' icon. (And if I can access them, they images have a Jira URL) (same Issue as #887?) #992

Closed
steverwyllie opened this issue Feb 23, 2024 · 3 comments
Assignees

Comments

@steverwyllie
Copy link

Describe the problem
(1) Broken Images..... When the ADO Work Item is opened, I see the 'broken image' icon instead of the images.
(2) With a Jira url..... I can see them by clicking Open Image in New Tab - but they have a Jira url.
The broken images are a difficult usability issue, but the Jira Server is going to be removed in about a week, so I'm also worried the images will be unavailable

To Reproduce
When I open an ADO Work Item created by the Migrator, I see the 'broken image' icon instead of the images.
When I then hover over the broken-image icon, right-click and select
-- Load Image - nothing happens
-- Open Image in New Tab - the image is presented, but with a url that 'points' to the original Jira Server
I'd like to see the images instead of the 'broken-image' icon, but the Jira Server is going to be removed in about a week, so I'm also worried the images will then become entirely unavailable

Tool version

  • 3.0.356

Attachments

Screenshots
image
image
image

@Alexander-Hjelm
Copy link
Collaborator

Here are some steps to try:

  • In your migration workspace, locate the .png image in the Attachments/ folder and verify that the .png image is rendering correctly on your local machine or VDI.
  • Are the .png images imported on the Work Item as Attachments? If so, can you maybe see what the discrepancy is between the attachment URLs and the URLs in the Work Item Description?

Otherwise here are some potentially related issues:

Copy link

This issue is stale because it has been open for 25 days with no activity.

@github-actions github-actions bot added the stale label Mar 20, 2024
Copy link

This issue was closed because it has been inactive for 5 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants