NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

Hey all!

I just wanted to add clarification that, as usual, customers on the Jira Release Track are receiving updates after everyone else. The next scheduled release for the Release Track is 12 Sep 2023.

Cheers,

Andre | Product Manager, Atlassian

Atlassian Update – 08 Aug 2023

Hi all!

I'm happy to inform you that rollout for our Jira products (Jira Software, Jira Service Management, Jira Work Management, Jira Product Discovery) has started today and will be available to all customers by the beginning of next week.

Cheers,
Andre | Product Manager, Atlassian

Atlassian Update - 30 June 2023

Hey everyone!

Here's some good news, and some less good news. We're happy to announce that this change will roll out to Confluence over the course of next week! That said, the release for Jira is delayed and will follow some time later in July.

I'll update you all once more when we are starting to roll out for Jira.

Cheers,

Andre | Product Manager, Atlassian

Atlassian Update - 30 May 2023

Hey all!

Thank you for your continuous feedback, and for sharing insights into the problems you are facing with our current solution.

We are pleased to announce that we're making some changes to how links open on click.

1. Same-product links will continue to open in the same tab (e.g. Jira -> Jira or Confluence -> Confluence)
2. All other links will open in new tabs (e.g. Jira -> Confluence or Jira -> Figma)

This change will be rolled out to all Atlassian products (e.g. Jira, Confluence, Trello and others) for the rich text areas you use to write your content, such as Confluence pages, Jira issue descriptions and comments, Trello card descriptions, etc.

You can expect this to be available to you within the next 2-3 weeks.

Thank you again for your collaboration - and please keep the feedback coming, to help us build even better products!

Cheers,

Andre | Product Manager, Atlassian

Atlassian Update - 30 December 2020

Hi all!

My name is Jonno and I’m a PM on the editing experience in Jira Cloud (including Jira Software and Jira Service Management). Thanks for all this feedback. Given the level of interest we’ve conducted some research to reassess the link click behaviour across Jira Cloud and our other products like Confluence Cloud that use our new editing experience.

Decision:

Based off our research, we will keep the existing default behaviour.

This existing default behaviour is:

• All links in the editor (i.e. the mode where you can see a toolbar and insert content) will open in a new tab by default.

• All links in the renderer (i.e. the published/saved view of an issue description, comment, etc) will open in the same tab by default.

Reasoning:

We assessed multiple approaches and landed on keeping the existing behaviour for the following reasons.

For users in the editor:

• We don’t want a user to be moved away from the current work they’re doing so open the link in a new tab by default. This is common behaviour.

For users in the renderer:

• Common link-click behaviour on the web is to open in the same tab.

• If we open links in a new tab by default, it’s impossible for a user to open the link in the same tab. For opening in same tab by default, however, there are common ways to open in a new tab, like cmd + click (Mac), ctrl + click (Windows & Linux), right click then select open link in new tab, or pressing the middle button on a mouse.

• From an accessibility standpoint it is better to stick with the default browser behaviour and open links in the same tab. The main arguments for this are:
  • Assistive technology users can become disoriented when a link opens a new tab or window. They cannot use the back button to return to their previous location. We want to minimize this as much as possible. We have a toolbar button for opening links in the editor to give those with accessibility needs guidance that a new tab is opening.
  • People with mobility or dexterity issues who rely on a keyboard may find it difficult or painful to perform additional navigation tasks.

For both the renderer and editor:

• We decided against giving user-level control of how their links open when clicked. Aside from the accessibility and other reasons mentioned above, we believe this could cause confusion to consumers of the content. This is because every link could hypothetically open in a different way. It wouldn’t afford the consumer of the content a predictable experience when clicking on a link.

Next steps:

I know this won’t be the decision a number of you are looking for, and I’m sorry for that. It’s what we believe is the best decision, for the majority of our user base, with the current information we have at our disposal.

Based off this decision, I’ll be closing this ticket and marking it as “Closed”.

We’re always looking to reassess and improve our experiences. If new information comes to light that suggests we should iterate this approach, we’ll definitely reconsider.

Thanks again for your feedback.

Jonno | PM, Atlassian Cloud Editor