Atlassian teams are coming to Jira Software!

[Yerbol Nisanbayev]

---

Soon we will be bringing the Team field that connects with Atlassian teams to Jira. What is an Atlassian team and how do I use it?.

When this field becomes available in both team-managed and company-managed projects you will be able to:

1. Associate Jira issues with teams

2. Search (JQL), filter, and create reports for issues by teams

3. Use teams in Advanced Roadmaps plans.
   Learn more about the changes coming to Advanced Roadmaps.

4. View issues associated with a team on the team profile

---

☀️ What are teams in Jira?

Today, you use Atlassian teams to make use of collaborative features such as mentions, shares, and assigning teams to Atlas projects and Compass components.

Soon you will be able to organise your work around teams in Jira. Unleash the potential of your team by using teams for collaboration in Jira Software.

You can use the Team field to:

• Associate a team with a work item in Jira

• Search for issues or filter for a team in JQL

• View issues associated with a team on the team profile

 

When is this coming to my Jira?

Teams field in Jira is now available for all of Free/Standard/Premium license customers and most of Enterprise customers. We are working on getting this field to the largest and most complex Enterprise customers in the following months.

🙋🏻How do I use the Team field when it's rolled out?

We will let you know when we start rolling out this field to everyone. At that time you can:

• For Company-Managed Projects, reach out to your Jira admin to enable the Team field. If you have project permissions, you can do it yourself!
• For Team-Managed Projects, ask your project admin to enable the Team field.

Learn more about project permissions

🤝 What about teams in Advanced Roadmaps?

Previously, a Shared team in Advanced Roadmaps was a concept only available to Premium customers. Shared teams in Advanced Roadmaps will be migrated and will start using Atlassian Teams in Jira Software. After this change rolls out, you’ll be able to use the same teams that are in your issues, and in Advanced Roadmaps.

No more double configurations, no more siloed teams – just smooth sailing.

Learn more about the changes coming to Advanced Roadmaps

[Hannes Obweger - JXL for Jira]

Hi @Yerbol Nisanbayev

great stuff! I already commented on Rhys' post, but just to re-iterate: It's critical to understand if and how this will affect any API integrations / the ecosystem. Right now, we (JXL for Jira), and I'm sure many others, access an issue's team via the respective Custom Field, assuming a certain data shape.

Is this data shape going to change? If yes: Can I read up on these changes somewhere? What's the exact deprecation period?

Thanks!

[Chris]

Hi @Hannes Obweger - JXL for Jira 

The current data shape of the Team custom field exposed via the issue REST API is still supported. However there will be a change to the Team custom field type. Does your app rely on some custom field type introspection? 

One additional thing that will change is that plan-only teams will no longer be exposed via the REST API. You can read more about that here:
https://developer.atlassian.com/changelog/#CHANGE-799

Regards,

Chris

[Hannes Obweger - JXL for Jira]

Hi @Chris

we're essentially doing two things:

1. Find the custom field with schema name com.atlassian.teams:rm-teams-custom-field-team within the result of the fields endpoint.
2. When we load issues (e.g. via search), retrieve the values from the fields section of an issue based on the custom field ID identified in 1., and expect a data shape of { id: string, name: string } for shared teams. (Our code already incorporates the changes in CHANGE-799 in a backward-compatible way.)

Do I understand correctly that 1. will have to be changed, but 2. should still be valid?

[Chris]

Hi @Hannes Obweger - JXL for Jira 

Yes that is correct.

We have onboarded your dev site to the early access program so you should be able to try this out now.

You should see the Team field with the new schema name com.atlassian.jira.plugin.system.customfieldtypes:atlassian-team

[Marc Roberts]

Hi @Chris we're also doing some automation with the Portfolio shared teams custom field, so would love to already start using the new teams field in our cloud instance, if that's possible?

[Nena Kruljac]

Hi,

how are these teams related to Team custom field? If not yet, when can we expect it to be connected?

Thank you, kind regards, Nena

[Chris]

Hi @Nena Kruljac 

Once this feature is rolled out, these teams will be selectable in the Team custom field.

Regards,

Chris

[Claudia Gerbersmann]

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

[Anthony Cast]

With this rollout will it be possible to associate 1 issue in a Company-Managed project to multiple Teams? These issues in JSWCLOUD appear to intersect:

• https://jira.atlassian.com/browse/JSWCLOUD-19633
• https://jira.atlassian.com/browse/JSWCLOUD-21046

[Elvira Kan]

Hi @Anthony Cast 

No, there is no change to this - only one team can be assigned on issues. 

Regards,
Elvira. 

[Todd Thomas]

Oh, no! We currently use the Components field to associate different teams to an issue because there are times when multiple teams need to work on something, but would like to switch to using the Team field except for the limitation of only one team.

How would Atlassian recommend handling circumstances where multiple teams need to be involved in one issue?

[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.

[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.

[Erin Quick-Laughlin]

@Chris  I have a few questions about impact:

1. When this community post says "Shared teams will be visible across all Jira sites in your organization (even if we use multiple sites)" can you confirm this is Jira only?  We have a public-facing Confluence site that we may want to restrict editors from picking/adding a team to a page.  
2. When the same post says "Atlassian will automatically add the new Teams field to all issues in Jira, replacing the existing one if needed",
   1. Does this mean the customfield ID changes? Thinking about Jira Automation impacts. 
   2. If not,  can we assume that if we already have Team[Team] added to our issues, there's no change?
   3. Can we assume that there will be no changes to Tempo's Team field?
3. Based on the gif above in this post, It looks like the ID of a Shared Team is going to change from an Int to a GUID after migration. Is that true?
   1. If so, will we still be able to access by the legacy ID?
   2. If not, will Atlassian help us avoid breaking existing Filters and Jira Automation in some way, like performing the conversions for us, or will we need to update anything that used the old ID?

[Gregory Kremer]

@Erin Quick-Laughlin All very legitimate questions. I would love to see them answered ASAP. The March 20 is fast approaching.

@Chris Can Atlassian address these and other similar questions please? It is critical for us to know how new Team field will behave. Not knowing it will cause huge problems to most of us, who have been using Advanced Road Map.

[Chris]

Hi, to share some answers:

• Atlassian teams are visible across the organisation, even at present. So if a team is created in Jira, it will be visible in Confluence as well. When we convert the Advanced Roadmaps teams to Atlassian teams, they will follow this model.
• The Team custom field ID will not change so if your automation uses the Team field ID, it will continue to find the field
• If you have the Team[Team] field added to your issue screens, it will continue to be there with the Atlassian team field
• We are not changing the Tempo team field
• Yes the team IDs will change, but we will still support legacy IDs in existing saved filters or Jira Automation rules. (However new filters and automations should use the new IDs)

[Meital Adir]

Hello @Chris, 

When will you convert the Advanced Roadmaps teams to Atlassian teams? since we are using shared teams and I don't want to have duplicates if I'll create now Atlassian teams.  

[Belinda Baker]

Hello @Chris and Atlassian, 

Just wanted to clarify "Atlassian teams are visible across the organisation, even at present. So if a team is created in Jira, it will be visible in Confluence as well."

Did you mean on a Site level rather than an organisation level?

We have an Enterprise customer who has different Teams across separate Sites and have not seen Jira Teams from Site A listed in the Jira Teams for Site B.

The language around these changes has mentioned organisation but it seems to implied it is shared at a Site level rather than Organisation level, the clarity is needed to confirm if we need to de-dupe Teams across an org level or just a site level.

Kind Regards,

Belinda

[Belinda Baker]

Hi @Yerbol Nisanbayev

Could  you confirm the above please? It's quite important for Enterprise customers.

Kind Regards,

Belinda

[Yerbol Nisanbayev]

Hey @Meital Adir

Advanced Roadmaps teams are planned to convert to Atlassian teams in the upcoming months. If you want to avoid duplicates, please hold off on creating Atlassian teams now or you could create them but you would need to delete the duplicates in the future.

Hi @Belinda Baker this works on the organisation level. Can you please verify, they should be seeing teams from all sites in all sites. 

[Gregory Kremer]

@Chris 

We did a lot of work to navigate Team field's shortcomings. The announced changes will cause us a lot of headaches. That being said here are my questions:

1. Will we be able to control who can create a Team in the new setup?

2. We have a large number of reports, based on Team field. Currently, as everyone knows, we have to use team number in order to extract relevant data. Will team numbers be still available and will remain the same in the new setup? This is crucial for us to know, as all the reports would need to be re-written in case team numbers are changed or completely gone.

I will greatly appreciate your prompt reply.

[Chris]

Hi @Gregory Kremer 

Creation of Atlassian teams is more open than Advanced Roadmaps shared teams. When we convert the Advanced Roadmaps teams to Atlassian teams, they will follow the Atlassian team model. The Advanced Roadmaps shared team management permission will no longer be applicable.

As to your reports, generally speaking we aim to keep backwards compatibility with existing integrations. For example fetching data using the legacy team ID. But I might need a bit more information on how your report use case works to understand if it would fit in with this backwards compatibility support.

[Collista Lewingdon]

@Chris I was going to give you kudos for your thoughtful and very thorough answers on this topic but the kudos system won't pull you up as an option in the system since there are several dozen Chris's in the system. 

[Monique vdB]

@Collista Lewingdon you can always go directly to the person's profile and give kudos on the Kudos tab.... if they are enrolled.  Looks like Chris hasn't opted in yet. 

[Collista Lewingdon]

Thank you for the response @Monique vdB , I checked again this morning and he has opted in now, so I was able to give him the kudos. 

[Elaine McMillan]

Can this be used in JSM as well for assigning tickets to teams?

[Yerbol Nisanbayev]

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

[Jason Selby]

How do you assign a ticket to a team. I have enabled the field, and when i try to type the Team name it comes up with "plan-specific teams can only be selected through a plan"

Any ideas on this?

[Megan Ferguson]

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

[Chad Jackson]

We are looking to build out a Assets Object Teams to manage teams for Jira Service Management. Will this new  Team field work cross platform with JSM. If so when?

[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.

[Dianna Bucher]

Will we have the ability in the Teams dropdown in Jira to filter to only see the Teams that are applicable for the specific Jira project versus all teams in our company instance of Jira?  (Similar to the Sprint dropdown.)

[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. 

[Daniel Dolinov]

Will we be able to use teams when providing access to Jira projects?  In other words, adding Teams to project roles the way I can add individuals and groups?

[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 

[Daniel Dolinov]

Is there a way to sync teams with Active Directory/Azure Active Directory?

[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

[Walter Buggenhout]

Hi guys,

While I do welcome the change, how come a selected team in JQL is not simply displaying the team name, but an impossible to read hash?

We see the same with the Advanced Roadmaps team, but there it is a number that is being displayed. It would really be very valuable if that could be fixed before rolling out the change it self, and ideally be made more consistent across standard and premium plans.

Apart from that, looking forward to the new functionality!

[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

[Iain McCarthy]

We are really looking forward to more intuitive, visible teams. Currently we manage everything via Jira's access groups and API updates. Atlas' updates have been, to date, not quite what we need. When this lands in Jira we would like this to be:

(a) sync'able with our IdP via Atlassian Access or other route (currently I think only Okta is supported? We need Google). Having another isolated team directory would be a nightmare for stale data and maintenance load. 

(b) centrally managed - we really need this to be controlled by admin. Free-form teams is really not compatible with reporting and security/issue visibility requirements. 

Hoping we can address both of these!

[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

[Rick Westbrock]

Any idea when the Team field will be available in the Edit Issue action of Automation rules?

I am currently using advanced JSON to set the field however when I use what I thought was the team ID found in the URL of the team page I get an error for ID not found. It would obviously be more user friendly if we could set the field using team name instead of ID but since that isn't the case how do I find the correct team ID?

[Rick Westbrock]

Does this require that we have the Advanced Roadmaps feature? I added the field to a screen but when I try to edit the field I just get this message “Plan-specific teams can only be selected through a plan”. Our Jira Software plan is Standard but we do have Jira Service Management on the Premium plan.

I did some searching and ran across how to make a team shared but that was only in the context of advanced roadmaps. We have four teams defined and none of them show up in the Team field, just that error message.

[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.

[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.

[Hailin_Zhang]

Hi Atlassian,

We have a Team menu item on the top of Jira screen sitting with dashboards and Plans, while team created there cannot be selected as an option of team field.  Only shared teams created in advanced roadmap are selectable. 

So what is the team menu item used for?

[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   

[Joni Johnson]

Is there a way on the Epic Issue type or the issues you can define in Advanced Roadmaps to assign multiple teams? We want to use it to know what teams are working on the Epic issue type.

[Sergei Gridnevskii]

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

[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.

[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?

[Joni Johnson]

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

[Sergei Gridnevskii]

Another Team. We already have a bunch in Advanced Roadmaps.

[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.

[Yerbol Nisanbayev]

Hey @Sergei Gridnevskii ,

No Teams will stay a custom field but it will be better integrated with the rest of Atlassian platform. For example you would be able to @mention the team across Jira and Confluence, see who is the team comprised of instead of just seeing the team's name and more.

[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.

[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. 

[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.

[Yerbol Nisanbayev]

Hey @David Meredith , that's true there is a huge divide between teams and groups right now. How to best connect the two is one of the area that we are thinking of for teams right now. We will be introducing some of the functionality available for groups  to teams in the near future. When we get closer to specifics, we will share the updates on the community :) 

And please feel free to vote for a related ticket here https://jira.atlassian.com/browse/CONFCLOUD-73457

[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.

[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.

[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.

[Yerbol Nisanbayev]

Thank you for clarifications @Mark Dodrill  Currently Teams is not available on Jira Align, we don't have  a short term plan to add it to Jira Align. 

We will need to gather more feedback to understand the need and priority of this ask, currently it is not a high priority on our roadmap. 

Here is a feature request I created for this, feel free to vote and watch: https://jira.atlassian.com/browse/JRACLOUD-80852 

[Kyle Foreman]

Hi Mark,

To add to Yerbol's comments, we (the Jira Align team) are currently investigating support for the Jira Team field in our Jira connector. Today, you can map a Jira custom field, but not the new Team field. We hope to add this soon and then will look into further integrations with Atlassian Teams. 

Let me know if you have any follow-up questions!

-Kyle

[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

[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.

[Yerbol Nisanbayev]

Hey @Sergei Gridnevskii

That is an excellent observation. We often notice that teams tend to configure their projects to encompass all of their work. Our products provide remarkable flexibility, as evidenced by instances where teams create a new Jira project for each real-life project. In some cases, a single real-life project may be divided into multiple Jira projects. Additionally, teams frequently collaborate and take ownership of tickets in projects managed by other teams, demonstrating the myriad use cases.

To accommodate these diverse scenarios, we are incorporating the team concept into Jira, streamlining the process of tracking team work across various Jira projects, regardless of how the work is set up for any particular team.

[Collista Lewingdon]

At my employer we have many cross department and cross team projects, so I see the incoming team field as a great opportunity to assign tasks to the team that will handle it and let them decide who on their team will be the assignee to handle the task. 

[G subramanyam]

Pretty interesting update and eager to explore.

[Laura Friedman]

What is the anticipated timeframe for formal release?

[Yerbol Nisanbayev]

Hi @Laura Friedman 

We are working on getting this to the customers as soon as we can, but I am afraid we do not have a timeframe to share at this point. We will keep you posted when we have a more specific timeframe

[Sandra Axelsdottir]

This is great news and I'm looking forward to this being ready and rolled out to everyone.

However, I have a request @Yerbol Nisanbayev

At Team '23 I got a demo of Jira Product Discovery and there Atlassian is introducing a new team. Can you please make the team function in Jira Product Discovery align with what you are doing here.

[Laura Friedman]

Agreed. @Yerbol Nisanbayev , synchronizing this feature across Atlassian products is critical for our purposes.

[Yerbol Nisanbayev]

Thank you both for this great feedback and I hope you enjoyed Team 23, we will look into JPD. We are working on synchronising teams today across all of Atlassian products.

[vivekgupta_hsc]

It would be must to integrate teams with user groups. We must have option to add users in team using user groups. Please confirm is it planned and coming.

[Yerbol Nisanbayev]

Thank you for this suggestion @vivekgupta_hsc I have captured it in this feature request, please vote and watch.  https://jira.atlassian.com/browse/JRACLOUD-80976

[vivekgupta_hsc]

Hi @Yerbol Nisanbayev

I also want to add that team can populated from project roles as well. Please consider.

Thanks.

[Yerbol Nisanbayev]

Hey @vivekgupta_hsc 

Can you please expand on this and explain what you would like to be implemented exactly and how does it help with your work?