New Features: Custom Field, Rovo Skills, JQL improvements and more!
Hi Teams community đź‘‹
We’ve been listening closely to your feedback, and we’re excited to share a bunch of new features and Rovo skills designed to make Atlassian Teams even more powerful and easy to use. From smarter automation in Jira to AI-powered cleanup, here’s what’s new.
Improve your workflow with Team custom fields
We’ve taken your suggestions and improved Team custom fields with three new capabilities available now.
Scope custom fields to Team Types
You can now scope a custom field to any Team Type when you create it. This allows different teams to have unique configurations. For example, you might want your engineering teams to have a Lead field, while your on-call teams use a Point of contact field.
Sync managers to Team custom fields
When you configure your HRIS syncing, you can now sync the manager field to a Team custom field. This ensures all synced teams automatically have their manager information updated and visible.
Team Custom Fields in Automation
Save time and improve workflow accuracy in Jira by automatically assigning issues to Person based on Team’s custom-field data. Use the Assign issue action in the Automation rule builder to assign an issue to the user stored in a single-cardinality People custom field on a team, such as an On-call field.
How to get started:
-
Go to Space settings, then Automation.
-
Create a new rule or edit an existing one.
-
Add the Assign issue action to your rule.
-
In the Assignee dropdown, select Role-based assignee.
-
Choose the specific People custom field that contains the team information.
-
Select Save to update your action, then Turn on rule.
Clean-up-Teams Skill
Over time, team directories fill up with inactive, duplicate, or forgotten teams, creating noise and slowing everyone down. The new /clean-up-teams skill for Rovo takes care of this for you.
Rovo analyzes your teams using real activity signals - connections to projects, issues, and other work to surface a curated list of teams that may no longer be active or relevant. You stay in control: review the recommendations, archive what you don't need, and dismiss anything that should stay.
Ways to use it
-
Both regular users and org admins can trigger it anytime using a button Clean up Teams by going to the Teams directory and clicking the Clean up Teams button in the overflow menu (see screenshot below) or by directly using the /clean-up-teams command in Rovo
-
We’ll also give you a proactive nudge in your teams directory when cleanup is recommended if a user has permissions to manage a few teams
-
Regular users can clean up teams they are a member of. Org admins can clean up all teams.
The more you use it, the smarter it gets - your feedback helps refine the recommendations over time
Clean up teams button in the overflow menu
Clean up teams nudge
Diagnose Teams Permission
Not sure why you can’t see a team? add someone to it? or create a new one? Rovo can now help you understand what may be blocking you.
Ask Rovo about a team permission problem in your own words, or use /diagnose-team-permissions when you want to explicitly invoke the skill. Rovo checks relevant team visibility, membership, and permission signals, then gives you an evidence-based explanation and clear next steps.
You may also see a helpful Rovo nudge when you search for a team in the Teams directory but can’t find it, or when you land on a Team not found page. It’s read-only, so it won’t make any changes to your teams or permissions.
Diagnose team permissions nudge
Access via invoking the skill in Rovo Chat using the slash command /diagnose-team-permissions
Ways to use it
-
Ask Rovo: “Why can’t I see this team?” or “Why can’t I add someone to this team?”
-
Use /diagnose-team-permissions to explicitly invoke the skill
-
Follow the Rovo nudge after an unsuccessful Teams-directory search or from a Team not found page
Autocomplete for teams in membersofJql function
We’ve made it easier to filter work by your favorite Teams. You can now use the membersOf() function with an autocomplete dropdown, reducing the manual effort of finding and typing team IDs.
As people join or leave the Team, your filters update automatically, so your boards and reports stay accurate with less manual maintenance.
Previously, membersOf() only worked with groups and for Team with a delimiter as id:<team-id>:
assignee in membersOf("jira-administrators")
OR
assignee in membersOf("id:team-name")Now you can also target a Team by simply searching with the team name:
assignee in membersOf("team-name")
Benefits
-
Reduced effort: No more hunting for a Team ID in a URL. The autocomplete dropdown handles the identification for you.
-
Simplified maintenance: Save time on manual filter updates. When Team membership changes, your JQL results update automatically.
-
Flexible queries: Combine Team filters with other JQL parameters to include or exclude specific people or groups.
How to use it
Earlier, this only works when you use id:<teamId> in your JQL.
To find your team’s ID:
-
Open the team’s profile page. The URL will look like:
https://home.atlassian.com/o/<your-org-id>/people/team/<team-id>?<site-id> -
Copy the <team-id> part from the URL and use it in your JQL: membersOf("id:<team-id>").
You’ll know it’s correct when the team name appears as a lozenge in the field.
But now, you do not have to figure out the team id. Simply invoke the membersOf function and start typing the team name inside the membersOf function quotes
-
See work items assigned to members of a specific team:
assignee in membersOf("id:<teamId>") -
See work items assigned to members of a specific team, group, or users:
reporter in membersOf("id:<teamA>") OR reporter in membersOf("id:<teamB>") OR reporter = jsmith -
Include a team, but exclude specific people:
assignee in membersOf("id:<teamId>") AND assignee not in ("John Smith","Jill Jones")
For all the above mentioned scenarios, earlier you had to find the team id. Now, this will be taken care of automatically from the Autocomplete dropdown Team selection
Team Settings redirection from Adminhub
Faster access to your Team settings
We’ve made it easier to manage your Teams in Atlassian Administration. You can now access your settings directly from the Team directory with a single selection.
What’s new?
Previously, navigating to your settings required multiple steps: selecting a Team, going to the Team profile, and then finding the settings page.
We’ve simplified this journey by adding a Team settings button directly to the directory. You’ll find it right next to the Create team button, giving you one-click access to the settings for your current organisation.
How to use it
-
Log in to admin.atlassian.com.
-
Select your organisation.
-
Select Directory, then select Teams.
-
Click Team settings button and you’ll be redirected to Team’s page where you can access and control team settings like HRIS Connections, Team types etc.
This update is part of our ongoing effort to help you get to your work faster and stay in your flow.
Was this helpful?
Thanks!
William Pan
5 comments