Atlassian teams are coming to Jira Software!

[Sergei Gridnevskii]

I guess business analytic should work on epics. Teams work on stories, tasks and bugs.

[David Meredith]

For JSM in particular users have been forced to create their own methods of team assignment using custom fields and linking to groups. There are marketplace addons that do this better but paying for what I consider basic functionality really gets under my skin.

I appreciate that Teams are being looked into but I don't feel like the current implementation is fit for purpose... I don't want users to be able to decide they want to be added to a Legal or HR team. I also don't want users to be able to decide to remove other users from that Team. Without these basic controls I'm struggling to see what the use case would be that would be better than creating a custom group field? Maybe creating a Team for signing up to an open beta?

I recall speaking with a product lead about this before but I would suggest that if you are going to create a group of users then you should be able to assign it a purpose:

• Open group
  • Current implementation of Team field... Anyone can join / manage
• Closed group
  • As above but with controls I guess
  • Could be used for resource forecasting etc.
• Assignment group
  • Managed by a manager owner, can be used as an escalation point
  • Can be assigned tickets
  • Maybe restrictions on what projects should be able to assign to this group
• Distribution list
  • For notification purposes
• Approval group
  • For approval purposes
• Permissions group
  • For ensuring that a specific group of people have permissions to do or be forbidden from doing a thing

This would require more of a re-work around how groups operate and interact with every other part of the system... But I think it'd be worth it.

I really hope that this Teams field continues to be worked on and fleshed out but in it's current form it doesn't appear to be much more useful than any other custom field.

[Joni Johnson]

Absolutely right that one team works on the stories, tasks, or bugs for their fixes. Multiple teams have the stories, tasks, and bugs to support the Epic issue type. We are using the multiple team assignment for planning and tracking at the higher levels. Trying to see if there's functionality without the tool without looking for a add-on.

[Mark Dodrill]

What is the impact for Jira Align and integration with Jira SW?  More details are needed to understand if/how this affects that integration.

[Elvira Kan]

@Hailin.Zhang this is exactly the change that is coming. Shared teams from Advanced roadmaps will be migrated to become a part of Teams in the menu you are mentioning and all of them will be available for selection on Jira issues. You can read about it in https://community.atlassian.com/t5/Advanced-Roadmaps-articles/Teams-in-Advanced-Roadmaps-What-s-changing-and-what-you-need-to/ba-p/2259096   

[Elvira Kan]

@Sergei Gridnevskii this change combines the Shared teams in Advanced Roadmaps with the Atlassian Teams in Jira Software so you will be able to use the same team in both places, more on it here: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/Teams-in-Advanced-Roadmaps-What-s-changing-and-what-you-need-to/ba-p/2259096 

[Sergei Gridnevskii]

So technically speaking Teams was a custom field and now it is a standard Jira field. Correct?

Also it would be nice to add Teams as Customers to Service desk projects. E.g. Backend team as organization. This would help us not to bother about newcomers and those who left team in millions of places.

[Esther Strom]

@Yerbol Nisanbayev as a site admin, is there any way for me to delete teams created by users who are no longer with the company? Or at the very least, reassign ownership of them to active users? The list of teams has gotten unwieldy and we have no way to clean them up that I can see.

[Yerbol Nisanbayev]

Hi @Esther Strom , yes there is. You need to join those teams as a member and then you can delete those teams. 

To re-assign - those active users will need to join the teams. Hope this helps.

We also have this open feature request asking for this, feel free to Vote for it and watch it for updates! https://jira.atlassian.com/browse/CONFCLOUD-75009

[Yerbol Nisanbayev]

Hi @Elaine McMillan , yes you will be able to do that too!

[Yerbol Nisanbayev]

Hi @Chad Jackson , yes it will work with JSM, it will be rolled out on the Jira platform at the same time to both JSW and JSM.

[Yerbol Nisanbayev]

Hi @Dianna Bucher , I am afraid not, in the dropdown you will be able to find all the teams in your org. 

I've created a feature request here https://jira.atlassian.com/browse/JRACLOUD-80845 , please feel free to vote for it and follow it. 

[Yerbol Nisanbayev]

Thank you for the question @Daniel Dolinov , not right now. We are thinking of connecting teams to permissions, but it will not be possible when this feature launches. 

I've created a feature request here, please vote and watch https://jira.atlassian.com/browse/JRACLOUD-80846 

[Yerbol Nisanbayev]

Thank you for the question @Daniel Dolinov , there is not today. We are considering that feature for our future releases.

I got a feature request here https://jira.atlassian.com/browse/JRACLOUD-80847, please vote and watch

[Yerbol Nisanbayev]

Hey @David Meredith , thank you for this detailed feedback. We have a feature request that is tracking closed teams here https://jira.atlassian.com/browse/JRACLOUD-75130, feel free to vote for it and watch it. 

We are planning to continue improving teams and making them more flexible for our customers use cases. 

[Yerbol Nisanbayev]

Hi @Walter Buggenhout 

Thank you for your feedback, I am afraid we will not be able to do that in time for the release.

I logged this ask here to help generate more support for this ticket and help priorities it, please vote and watch https://jira.atlassian.com/browse/JRACLOUD-80848

[Yerbol Nisanbayev]

Hi @Iain McCarthy 

Thank you for the feedback. Please vote for and watch the feature requests below to help us prioritise these asks

https://jira.atlassian.com/browse/JRACLOUD-80847

https://jira.atlassian.com/browse/CONFCLOUD-75009

[Yerbol Nisanbayev]

Hi @Rick Westbrock 

This feature will not require Advanced roadmaps. Right now Advanced Roadmaps offer their own version of Teams for Premium and above customers. 

This Teams field will be available for everyone including Free and Standard licences.

[Yerbol Nisanbayev]

Hi @Mark Dodrill 

Thank you for the question, can you please clarify what aspect of the integration concerns you the most? At this point we don't envision significant impact for Jira Align.

[Rhys Christian]

Hey @Joni Johnson

It's not possible to assign multiple teams to an issue in Advanced Roadmaps. That will not be changing with the unification of Advanced Roadmaps teams and Atlassian Teams. 

However while you cannot assign multiple teams directly, in Advanced Roadmaps you can get the visibility you are looking for from the roll-up of Teams assigned to child issues. Here's an example (applied to Initiatives here, but it's the same principle for Epics):

 

To enable Roll-up for data in the table, go to "View settings" and select this checkbox:

 

Does this work for your use case?

[Sergei Gridnevskii]

The more I think about it the clearer it is for me that the whole idea of Teams is artificial. And can be easily implemented using idea ONE PROJECT = ONE TEAM.

E.g. business analytics and stakeholders have a Planning project that contains Epics only. They can move them in time, set priorities, have dashboards and graphs.

Project managers/team leads can have Stories which are children of Epics. Each story belongs to a team that implements it - a dedicated project for the team.

Stories have story points and are a part of a weekly sprint. By collecting status of stories and story points business knows how much it costs to deliver a feature and when it will be delivered.

Each story has linked tasks and bugs.

That's all. Each team has a project, independent sprints and can plan it's work without interacting with other teams.

[David Meredith]

Hey @Yerbol Nisanbayev ,

Thanks for taking the time to respond I really appreciate it. I've watched and voted for closed teams.

I do think there needs to be more work into this feature for it to be as useful as a group however. It would have probably been less work to start with a group and then expand on that?

Atlassian Team field can't but Groups can be:

• Synced with IDP
• Controlled by admin for user membership
• Used to include multiple groups (not for assignment)
• Used in automation rules
• Used in project roles
• Used in project permissions
• Used in workflow

Groups can't but Atlassian Team field:

• Has a nice team page
• Can display members in the mouseover (handy)
• Can be used for resource forecasting in Advanced Roadmaps

I am looking forward to this feature devloping to a point where I can just use it to replace the assignment structures I've had to put in place, it just feels like it's a while off.

[Joni Johnson]

I will try that and see if that gives us what we need.

[Mark Dodrill]

I am wondering if there will be a common set of people/Teams that will work with both Jira SW and with Jira Align.  Will individual people and the teams they are on be defined in one single place, and used by both Jira SW and Jira Align? 

If so, what does that look like, how will that work, and what changes will be necessary in those tools to take advantage of this new functionality?

If not, then it sounds like there will be no changes in how people/teams are defined in Jira Align, specifically.  Then, I would ask, what is the plan for how this new Teams functionality will be enabled for Jira Align, and what timeframe is that going to happen?

There are many Atlassian partners who need this information, so we can be informed and advise our clients, and we haven't seen it yet.

[Rick Westbrock]

Thank you, I guess I will have to submit a Support case because I added the new field to one of my projects but when I try to enter a team it doesn't recognize any of the half dozen teams we have in our organization.