Announcing Team and User smart links: Say goodbye to messy URLs!

[#1]

Hey all,

Starting this week, you can collaborate faster and cleaner using smart links for Teams and Users!

✨ What’s new?

• No more messy, unreadable URLs!
  Just paste a Team or User profile link into any Atlassian editor and choose your preferred display:

  • Inline

  • Card

  • Embed

• Instant context:
  See key details like team description, member count, and user avatars, right where you’re working. No more switching tabs!

• Works everywhere:
  Smart links are supported wherever there's an editor in a product with Teams. Use it in Confluence, Jira,and even Whiteboards.

🔍 Why you’ll love It

• Stay in flow: Instantly view and share team info without breaking your stride.

• Better visibility: Make it easy for your teammates to discover who’s who and what each team is about.

• Looks great: Clean, consistent cards and embeds make your pages and tickets shine.

👀 What’s next?

• In-card actions: Add members or request to join a team—right from the card.

• Quick previews: Use “open preview” to see full team or user details in context.

💬 We want your feedback!

Have ideas or spot something we can improve? Let us know in the comments. 

Once again, big thank you to you all for the constant feedback and love for Teams. Looking forward to providing more exciting features 🙏

[Joe Johnson]

This is great! Will make cleaning up and templating team spaces in Confluence much easier!

Are there any plans to clean up the @ mention for teams in Jira?

[Rimantas Andrulevičius]

Maybe you have plans to make the Atlassian teams accessible in automations?

Currently - to set an Atlassian team to  a work item via automation is cumbersome and impossible to make dynamic. To set a team on a work item I need to select the advanced edit action (json format) and set the Atlassian team id (which is somewhere in the URL).

Some use cases:

In Jira: Set team on work item based on issue type/ asset field/ component.

In JSM: set team (the first line or second line support team) on work item based on affected service/ asset field 

[Josh]

I've been using this for the past few days and it has been really helpful!

One of the best parts is that it works within Jira Assets. If you have an attribute (field) for each object that you want to reference a Team, you just drop in the URL and it will render the friendly name of the Team.

[April Chi]

Hey @Joe Johnson ,

Thanks for the comment and glad this helped :) I don't have a timeline yet but cleaning up team mentions is on our radar.

If you're interested, I can keep you in mind for when we are open to feedback/early testing. Let me know! 

[April Chi]

Hi @Rimantas Andrulevičius ,

Thank you for the feedback and appreciate your feedback in helping us make Teams better. We acknowledge that this is a common pain point.

There's a JAC ticket you can vote for here.

In terms of where this is at, it's on our radar. We're working on building two triggers at the moment i.e. 'user removed from team' and 'user added to team', which we aim to ship by the end of the year.

For other automations, we want to start explorations but it's too early to give you timeline on when this will be complete. If you're interested in early testing, please let me know and I can keep you in mind. 

[April Chi]

I've been using this for the past few days and it has been really helpful!

One of the best parts is that it works within Jira Assets. If you have an attribute (field) for each object that you want to reference a Team, you just drop in the URL and it will render the friendly name of the Team.

@josh Nice! Appreciate the feedback and glad it's been helpful. Please let us know if you have any further feedback :) 

[Joe Johnson]

Hi @April Chi 

Thanks for the replies to my and other comments, these are all super useful features and I'm always happy to be involved in testing/EAPs or other feedback!

[Rimantas Andrulevičius]

@April Chi yes, I'm interested