Closing this means it will never be fixed...? That would be not acceptable! This is very annoying!

Hi joe.jongue,

Thanks for taking the time to comment on this issue and share your thoughts. I also want to apologise for the inconvenience that this bug is continuing to create for you and your team.

To provide a bit more background about why this issue has been closed, having a leaner backlog of issues allows us to better identify areas we can focus on that will have the biggest overall impact for our customers.

I should stress that closing an issue doesn't mean that it's gone and forgotten, but it's intended to be an honest indication that we aren't prioritising a fix in the foreseeable future. JQL queries easily allow us to find and reopen these issues when circumstances change.

Kind regards,
Edith

Hi Edith,

I'm quite appalled that you would close an issue on the basis that it hasn't generated enough demand (noise) from your customers. This shows that you don't value us as paying customers, regardless whether it takes your 2 months or 2 years to fix, this should not be closed. I manage a helpdesk, and if told my customers the same thing we would be out of business.

Could you not leave this in your queue in the off chance that your team has address all the other (thousands) higher priority issues, allowing them to then clear the backlog (including this ticket)?

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on bugs with a higher impact, and more votes.

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.

I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If demand for this picks up, we will reopen the issue.

I know what you mean. I just fixed 42 of them, and I'm tired!

Thanks for sharing Tony. This will help as we develop new content, but we also have existing videos (50+) on our site. It would take considerable effort to change all those widget connectors from YouTube to iFrame.

I discovered a workaround: You can copy the embed "iFrame" URL from YouTube into the iFrame macro, and use that macro to show the video. You can click "Share" in YouTube, deselect the option to show related videos, and copy the URL from the iFrame embed code into the iFrame macro. This seems to work fine.

I also noticed that this recently broke. This has a customer impact for us and we'd like to see this resolve quickly!

Hi joe.jongue

Unfortunately I currently have no update on this issue. This is on our backlog but there are a number of higher priority issues that we need to address before this. As soon as we have an more information on this issue we'll update this ticket with details.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian

Could I please get an update?

It may be seem trivial, however we use confluence to host our online tutorial videos (youtube) and currently at the end of every clip the user is presented with other random videos that are not at all related to our training videos i.e. it keeps a record or cache of the last or most recent youtube videos.

So if its possible could this please be bumped up a little.

Regards