Is there an update on this issue?   The registry fix is impractical and doesn't appear to work on later versions of Office (e.g. 2013)

Is there a workaround for Mac users as well?

When it will be fixed? We need it.

RE: "The third-party applications that have been involved in reported cases include:
◾MS Outlook
◾MS OneNote
◾MS Word"

This also happens with MS Excel - when clicking on a link from a list of issues which has been exported from Jira.

I'm re-opening, because the client-side registry workaround is not suitable in many cases.

To summarise the underlying problem: when a user pastes a link to a JIRA OD issue or a Confluence OD page into an MS Office app, the Office app uses an unauthenticated session to follow the link behind the scenes. Being unauthenticated, it gets a redirect to the login page, and it updates the pasted link to point to that login page. Therefore, users who click the link in the Office app go to the login screen instead of the original resource, regardless of whether they are authenticated. There is a registry patch to change this behaviour in Office, but applying that fix is not practical/possible for many customers. There's more info from MS here.

This still is not fixed.

When will this fix be deployed?

This issue relates to
JST-82496

Hey Robin,

I work in an organization that has 1900 users on Confluence so I don't know how we could have this workaround applied to each of their computers individually. Whenever we send out internal communications, we link directly to the file for the user to download it. Is there going to be a fix on the Confluence side that would address this? Would this still be an issue in the local version if we were to purchase that?

This will become a more urgent issue as our organization has adopted Confluence for all of our internal wiki needs, replacing some other systems. This is one function that we absolutely need to work though so we can share files with people all over the world.

Thanks,
Dave

Hi Dave, the status of this issue is perhaps a bit misleading. The fix for this problem is available now; it must be applied on the user's side by following Microsoft's recommended registry change, as described in the comments above.

Hope that helps!
Robin