Thanks for the detailed explanation of your use-case. That does sound like something that can be fulfilled by this Teams functionality. Unfortunately, we are primarily focused on cloud products, starting with JSW cloud. So we don't anticipate shipping this to Server or DC anytime in the near future.
Thanks for the detailed feedback. Please find my responses inline.
How will teams come closer to groups?
Great question and yes, intermixing permissions is a slippery slope. We are currently working on ways to bring interoperability between them but its still in the early stages. As of now, the teams functionality we are delivering as part of this EAP will not deal with permissions in any way (Please note that in this EAP, you cannot use Teams to manage permissions to Team managed projects in Jira). In the EAP, you can assign a Team to a issue and search using Teams in JQL
Who can create a team?
Anyone in your site/organisation can create a team. Teams are decoupled from permissions: Being part of a team does not automatically grant any permissions to the members.
I like that you add this to Advanced Roadmaps as well, so if you could just add resource management to AR as well, then I might be able to convince some companies to get back to Premium again :)
Will definitely take this as feedback and share with the team
Also, what are the plans for Teams moving forward? It already looks like you plan a team space type of setup, but will that be taken even further? Are there plans for team based boards/dashboards or perhaps even connection to team spaces?
Yes, we are currently working on improving the Team profile in order to surface the teams work from across Atlassian products. Regarding Team dashboards, in JSW, as part of this EAP, you can set up Team dashboards. Besides that, we are in the early stages of figuring out some permissions use-cases -> like granting permissions to a jira project/board/issue to a team. We are also working with JSM to figure out how to rollout Teams in JSM.
Just curious this "Teams" is it using the similar concepts we see in Jira Advance Roadmaps?
I have teams in our instance that want to use their Team they have created in JAR in their Standard Jira projects but I can not see the needed link. This new feature will it assist in this?
As stated in the post, during the EAP it will be a separate field and only available in JSW free and standard but we are currently working on unifying this with the team concept in Jira Advanced Roadmap, which will be rolled out at a later point. Thanks
This field is not yet designed to work with Jira Align. We are currently working on integrating it into Jira Advanced Roadmaps and unifying the team concept present in Jira premium. Once that is done, we will roll the functionality out to premium and enterprise customers. Thanks
I'm a developer associated with the dev work of this EAP. The field is a regular managed customer field, nothing special about this one. So it should appear in any place that other custom fields appear.
I would be interested as more teams within our organization are moving towards using Adv. Roadmaps. We also want to use Team Central so when the Adv Roadmaps Teams and the Team under people get unified, it will eliminate a some of confusion.
I would really like to join this EAP for Team field. I have build this from scratch in the past but now that I am in a new roll as admin it would be super helpful to add this to our site.
We already have too many 'team' fields in Jira. Advanced roadmaps, Tempo, and other plugins introduced team fields which are locked so we can't get rid of them. There are also some team fields which we created, can't get rid of them either. Plugins usually bring in their issue types and fields. I'm not sure how this feature will help or consolidate all these teams into one?
95 comments