Atlassian teams are coming to Jira Software!

[Yerbol Nisanbayev]

@Erki Tammik 

Thank you for this suggestion, currently we are not planning to add a visibility setting per team. When one searches or mentions a team we have smarts that limits the results of the teams that you will get to the ones you use more often and the ones that match your query that should help with limiting the number of results you would get. 

I've logged your ask here https://jira.atlassian.com/browse/JRACLOUD-81677 
please feel free to vote and watch.

[Yerbol Nisanbayev]

Yes we will, we are currently integrated with OpsGenie for new customers and new dashboards and we are planning to integrate with existing customer in the first half of the next year.

[Yerbol Nisanbayev]

Hi @Ryan Retting 

Thank you for your suggestion, we don't currently have this ability to connect boards with teams on our roadmap. But I have logged your ask here https://jira.atlassian.com/browse/JRACLOUD-81678 

please vote and watch to help us prioritise it among other items we have planned for teams. 

[Rick Westbrock]

@Yerbol Nisanbayev  roughly when was the integration created for "new" customers? I ask because we are relatively new to OpsGenie (2022 Q4) and I don't know if that means we are "new" customers in this context.

[Yerbol Nisanbayev]

Hey @Rick Westbrock thank you for following-up, in this context new means customers that started now - new as of August 2023.

For this particular integration - you will be considered an existing customer and will be integrated next year. 

[Dirk Ronsmans]

@Yerbol Nisanbayev ,

coming back to this question, will the list be limited based on the permissions within the project by default? Otherwise you might mention teams that have nothing to do with the project.

Preferably this would be done using a (new) permission within the scheme .

[Yerbol Nisanbayev]

@Dirk Ronsmans 

We have a separate feature request that aligns with your ask of limiting the teams based on permissions, please follow it here: https://jira.atlassian.com/browse/JRACLOUD-80845 

Right now the list is not limited and shows all teams from your current organisation. 

[Tammy West]

We began using the Team field today in Jira Service Management and noticed that when Team is assigned to a ticket all of the subtasks also show the same Team.  We were expecting that we could assign subtasks to different teams.  Is this working as designed?  If it is, I will have to come up with another solution.   We need to be able to assign subtasks to different team than the parent ticket.

[Yerbol Nisanbayev]

Hi @Tammy West , thank you for your questions.

I am afraid it is working as designed and the subtasks will inherit the teams assigned to the parent task. A workaround could be using an epic as the parent tasks and assigning issues to different teams. 

[Todd Thomas]

@Elvira Kan - Has this philosophy changed from only being able to assign one team per issue? If not, how would Atlassian recommend handling circumstances where multiple teams need to be involved in one issue?

Having a dedicated team field is wonderful, but without the flexibility of having multiple teams, report on it, etc. it will be much less useful than alternatives today.

[Megan Ferguson]

We are having the same issue. Did you ever figure this out?

[Joerg]

Is there now a time frame to share for this feature?

[Yatish Madhav]

Hi - thanks for this post @Yerbol Nisanbayev  - it seems to a be a great move in the right direction. I have not seen comments but here is some feedback/questions:

• is this going to be manageable through the Cloud REST API?
• how is this differant to User Groups and then Customer Organizations too ... I feel like all of them is just 'bundling' a bunch of users so I would assume they should all be managed the same or at least have some sync between them?
• to that point, can we auto link teams to schemes like permissions, etc?
• to see if Teams is rolled out to out instance, would it suffice to check if the Teams field exists or is there other things to check too?

[Hope Man]

On our product updates page it says: 

Status
GENERALLY AVAILABLE

but the teams field only let's us use Roadmap Teams it seems.

So I assume it is not generally available and is still being rolled out?

[Yerbol Nisanbayev]

Hey @Joerg  and @Hope Man 

This is being rolled out right now. Whether you have received this feature will depend on your license tier, we have rolled out to most customers all tiers but Enterprise at this point. We are planning to cover all customers by the end of the year.

[Yerbol Nisanbayev]

Great questions @Yatish Madhav 

- Today we already have a cloud REST API for teams, more on that here  https://developer.atlassian.com/platform/teams/components/team-public-rest-api/ 

- Teams are different from groups as groups are admin controlled and are very strictly managed, usually used for permissions. Teams are meant for collaboration and can be created by any users. We have received feedback on syncing the two and we are considering a couple of ways of how we could build this soon.

- Not today, but we are working on a way of surfacing teams in permissions

- Yes, if you got to project custom fields and see Teams as a field you can add -> you've been migrated. If you have advanced roadmaps, you can check if your shared teams have been migrated. And lastly if you are not on Enterprise license you most likely have been migrated.

[Yatish Madhav]

Thanks @Yerbol Nisanbayev  - the API helps a bit. But it makes us do a bit more work since we now need to manage Teams, Groups and Organizations :) :(

Yeah, I understand the strictness and the scope of where groups would be used but I do think often times it would be nice to reuse/automate teams or groups so that it is not seperately managed but it still allows for the individually managed for colab ...

Great thanks for those points

Thank you again

[Yerbol Nisanbayev]

Hey @Yatish Madhav , Yes I understand, the structure and hierarchy can get a bit complex. We are looking for ways to align teams with groups in the long term.

That is feedback we do hear time and time again, so it helps us to look more deeply into the connection between teams and groups.

Cheers!

[Yatish Madhav]

OK thanks @Yerbol Nisanbayev  - cheers

[Bert Dombrecht]

It would be nice if our users could also include the Team field in their Notification Scheme.
So all Team members involved in an issue get related notifications. Is such a feature being considered?

[Shankar Rishikesh]

I am wondering if we could send notification to "Team" field directly when updated or using any automation !I tried using it in Automation 'Send Mail', it does not recognize it as email field. If you have some options to send a mail to a 'Team' field, please explain here as well. If not, please add it to your feature list, this is most wanted if we start using this field in coming projects. Thanks.

[Omer Meshar]

Does the Team field work with Automation? I couldn't find it in a condition or an edit issue action.

[Gregory Kremer]

It doesn't. There were no "real" changes to the way you can use this field - it is still "Locked". Whatever changes Atlassian implemented made it worse - now anyone can create a team without admin control, that's about it. You still need to use an ID when querying, you still can't use it in the automation. I've asked many times of many people to give me a single positive thing this change offered us. Nobody came up wioth anything yet.

[Yerbol Nisanbayev]

Hi @Bert Dombrecht 

Thank you for highlighting a need for this feature. 

Yes we are considering this improvement for the Team integration in Jira, along with other ways we could improve the experience.

[Yerbol Nisanbayev]

Hi @Shankar Rishikesh ,

Thank you for this suggestions, we are considering an improvement to notifying Teams along with other things, your feedback helps a lot, please keep sharing if there's anything else we could improve.