Atlassian teams are coming to Jira Software!

[Todd Thomas]

@Yerbol Nisanbayev Could you address how multiple teams could utilize this new field in the future?

[Yerbol Nisanbayev]

Hi @Todd Thomas ,

Thank you for your feedback, we currently don't have specific short term plans to add support for multiple teams per Jira issue. It is something we are thinking of, and your feedback will help prioritise this ask in the future.

[Yerbol Nisanbayev]

Hey @Omer Meshar 

The field does not currently work with automation, it is on our roadmap and we will make it available in automation in the future.

@Gregory Kremer there are several things we hope this change helps our customers with:

- it eliminates different disconnected concepts of teams across Atlassian products, previously we had ~4 "Teams" across our products that were completely disconnected and duplicated each other. This and a few other changes create a single concept of teams that can be used everywhere.

- Teams in issues previously was only available to a subset of customers. Today we rolled it out to all of our customers, enabling them to assign work items to teams and search for them in JQL.

- Today when work is assigned to a team, user can find more details about the team in the product, previously it was a random field that did not provide much context about the team.

Hope this helps

[Gregory Kremer]

@Yerbol Nisanbayev All you did with this change is made it more complicated for us to manage teams, especially after we had to deal with Teams in ARM and made a lot of customizations to work around shortcomings. No one asked you to combine Team in collaboration tool with Team in ARM, because they served, and still do, different purposes. By combining them, you took away Admins capability to control Team creation, since anyone now can create a Team. So what happened afterwards? We had multiple teams with the same name. Team field is still not acting as a "normal" Jira field (no JQL, no Automation). So please explain to me again, why would you consider this as an improvement? Sorry to say, but I still don't see any benefits, and your reply didn't change my mind. And I think that my colleagues in Jira Admin world would agree with me. In order to fix this, first thing that needs to be done, is to limit Team creation to Admins only. Second, make this field act like a "normal" Jira field. Third, make it a multi-select field, because issues could be assigned to multiple teams. That would be a good start. Otherwise, it's just something you did for yourselves, not your customers.

[Claudia Gerbersmann]

Can't wait - I need to rite an automation assigning a team!

[Brian Selewski]

When will the feature be available to search for teams using Basic Search?  

[Fahad]

Hi Team, I just created a team but it's not visible under Teams. 

[Darrel Jackson]

Can this article be updated please? I've just noticed my Jira Premium bundled release has this scheduled for March now. I was told many times it was due by December and we have someone doing lots of clean-up work in preparing for the change. Can we get more information around scheduling of the change for Jira Premium customers with AR?

[Yerbol Nisanbayev]

Hi @Darrel Jackson 

Most of Premium customers should be migrated by now. Can you please email me your organisation name and jira url to ynisanbayev(at)atlassian.com and I can verify the rollout status for you.

[Yerbol Nisanbayev]

Hi @Fahad Abbasi ,

Please email me a screen recording or a screenshot of what you are seeing and I will help you to troubleshoot this issue. ynisanbayev(at)atlassian.com

[Yerbol Nisanbayev]

Hi @Brian Selewski 

Thank you for your question. Teams is currently in the plans to get added to basic search along with other fields. We expect that it may land there some time in 2024.

[rob_jeal]

Is there a way to restrict the team activity stream in "teams" to only show activities related to issues that are assigned to the team? We are trying to use teams specifically in a project but they don't need to see team members activities on other projects.

[Gary Spross]

When a "Team" is set within the Team field on a ticket, is there a way to notify the "Team"? I just tried and no notification goes out. I checked in the notification scheme and there is no way to specify that the "Current Team" should receive notifications for an event.

[Fahad]

HI @Yerbol Nisanbayev thank you for your reply.  As you can see the team exist, but I can't search it in team.  Also, when I 'm trying to assign a story to the team, this team doesn't appear under teams. 

[Yerbol Nisanbayev]

Hey @Gary Spross ,

Thank you for the question. That's one of the improvements we will be  working on for the Team assignments in Jira. Today it is not available but it is something that we have planned for the future. 

[Gary Spross]

Hey @Yerbol Nisanbayev

Thanks for the response. Any idea how far in the future this might be? In the meantime, is there an alternative means to do this manually? For example, is there a way to utilize the Team field within automation to transmit an email to the individuals that comprise the Team?

[Yerbol Nisanbayev]

Hi @rob_jeal ,

I am afraid there is no straightforward way to do this today. Thank you for your suggestion, we will add it to the list of things we want to improve for teams. 

[Yerbol Nisanbayev]

Hey @Gary Spross 

We don't have a specific timeline that we could share at this point, but your feedback helps us prioritise this feature among other improvements we have planned for teams. 
I am afraid after checking with the team I found that we do not have an alternative way of configuring this today. 

[Yerbol Nisanbayev]

Hi @Fahad Abbasi ,

Thank you for sharing the screenshots, could you please email me the URL of the team profile for team AWP-Teaming, that will help us investigate further. My email is ynisanbayev(at)atlassian.com

[Brian Selewski]

I tried adding this field to a Sub Task, but it is not showing.  Is it not available for Sub Task issue types?  

[Brian Selewski]

Is it possible to limit what teams will show in a project?  As in, when creating a team, pick which projects they will be working in thereby limiting which teams show in the dropdown?  

[Yerbol Nisanbayev]

Hi @Brian Selewski , thank you for raising this. Subtasks today cannot be assigned their own team and inherit a team from the parent issue. 

[Patrick Spitzner]

So far, so good. Is there a way to create a JQL query along the lines of: "Show me all issues currently assigned to a member of Team X"?

[Paul Heath Armengol]

tl:dr?

Summary of FAQs to date:

1. is there a possibility to add a search features in JQL something like team = Currentuser(team)?
   not supported
2. Is it possible to restrict a Team to see only tickets associated with them, in a Service project (company-managed)?
   not possible
3. is it be possible to use the membersOf function for jira teams?
   no
4. able to search user fields by team, example: assignee IN memberOfTeam(team)?
   no
5. available for Sub Task issue types?
   Subtasks today cannot be assigned their own team and inherit a team from the parent issue.
6. add visibility settings options for the "Teams" field?
   not planning to add a visibility setting per team.
7. Will it be possible to have a Team default for a Board in the near future?
   don't currently have this ability to connect boards with teams on our roadmap.
8. can we auto link teams to schemes like permissions, etc?
   Not today, but we are working on a way of surfacing teams in permissions
9. include the Team field in their Notification Scheme?
   no
10. send notification to "Team" field directly when updated or using any automation?
    no
11. Does the Team field work with Automation?
    It doesn't.
12. will the feature be available to search for teams using Basic Search?
    it may land there some time in 2024.
13. Is there a way to restrict the team activity stream in "teams" to only show activities related to issues that are assigned to the team?
    no straightforward way to do this today
14.  Is there a way to create a JQL query along the lines of: "Show me all issues currently assigned to a member of Team X"?
    no

[Gregory Kremer]

I've asked this question several times on this forum. Let me ask it again. What were the benefits of this change? I'd say this change brought us only headache with no positives. What say you? The more we will point this out to Atlassian, the better chance we would have to force them to do something to fix the situation.