Are you a Team Changer? Share your story and earn a badge!

33 comments

Last year I was able to implement several new Workflows to existing Spaces. By creating custom fields based off our learning in the Projects I was able to increase the value of the work items.

The new workflows really help us stay on track and reporting to clients has become more transparent.

Last year, the end of 2025, I helped an organisation with team work by introducing Atlassian Teams, now that it can meet many of the organisation's needs and wants.

There were some challenges, and still some are there, but some of the newest features introduced in the last months of 2025 were a great help to get things in place and meet requirements.

Since this organisation uses the Spotify model, I made use of the brand new features of Team Hierarchies to replicate their structures of Domains, Tribes and Teams. This also makes a visual hierarchy possible when searching the Team directory and selecting the "List" view.

Next to that, I used the even newer feature Team Types to set those teams to the "official team" type (previously called “managed team”), to make sure the teams and the hierarchies cannot be changed by just anybody and so make sure the structures remain intact. This also allows to quickly see which teams are official from the nice blue icon and to filter on "Verified" teams only. People can still create teams for themselves, for any kind of purpose, and those are now easily distinguished from the official company teams.

A future update on this will be to use managed groups from Microsoft Entra ID, to populate the members of the groups and connect them to the teams.

For reporting and looking up items related to teams, it is important to connect the teams by linking work, but also link the teams to related Jira and Confluence spaces (max. 15 teams per space), and 1 team per Jira work item. Within this organisation there is a wish to link multiple teams to work items, that is not yet possible. Even Goals and Atlassian Projects (Platform Experiences) can have Teams connected, and there it is possible to link multiple teams to a single goal/project, the only objects where that is possible as far as I have seen.

This leads up to the part where to get information about which information is linked to a/your team, and since the Team field is not supported in standard Jira dashboard gadgets, I have used two ways to be able to report/show this. Of course, from the Team itself you can see related items from the home page and various tabs such as Activity, Goals and Projects as well as Kudos.

The BETA for Home Dashboards, available after enabling this for your org from the Platform Experiences menu (admin.atlassian > Apps > Platform experiences), allows all users to create dashboards which are more modern and very similar to Atlassian Analytics, and there the Team field is natively supported so you can make a dashboard with widgets of type Chart and List to visualise team work!

Lastly, Atlassian Analytics provides an even deeper look into your teams, by making it possible to list your teams with the corresponding Id, Parent Id and Parent team name, for further analysis on your team structures and related objects. I used SQL queries instead of the Visual editor to pull in the data I want to display in the charts and lists, as that can achieve what is needed for this organisation better than the Visual Editor's options, which are more focused on Metrics.

Hopefully someone learned something from this ;)

We recently integrated Google Meet and Loom, and it's really boosting our team's productivity! 🎉📄

Like • Elena_Communardo Products likes this

Last year, I created monthly and quarterly reports in Confluence using graphs made with Rovo to help teams digest and understand data more easily. I also leveraged Atlassian Intelligence to provide leadership with bite-sized summaries, making it much easier to spot trends and make informed decisions.

As a Product Marketer at a remote company, I don’t always see everything that’s happening around our apps and solutions. So I built a Rovo agent that pulls together every mention of the products I focus on and sends me a report every Friday. I review it at the end of the week to catch up on conversations I might’ve missed. It’s helped me stay more informed and collaborate better with other teams. I also documented how I set it up and shared it with the Product Marketing team so they can also benefit.

Like • Anwesha Pan likes this

Looking back on 2025 I am not sure I had any super impactful game-changer moments. I did help lead a roll-out of our company goals and core values in February 2025 which shaped the way we approached work in 2025 as an organization. I also worked with our HR team to change the annual Performance Review process to be reflective of whether team members demonstrated our core values in their work and helped the company achieve the set goals. So it was a lot of small change and tweaking that led to a different mindset and approach towards our collective work on how we service our partners and customers.

Like • Anwesha Pan likes this

As an Atlassian Advocate at my company, I was able to present Loom and create three new Rovo Agents that help Legal, Privacy, and Security Teams provide better and ready information.