Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
The MVP and after MVP requirements are good for us.
We do share the same concern as @Jared Schmitt about changing a name will break automations, JQLs, AQLs, CQLs, and such.
We will most likely end up using the after MVP APIs to update Team names as they are updated in our HR system, and it would be a great burden to manually update all automations and queries every time that happens.
Circling back to this - I'm back from leave and am happy to report that our team is currently working on this. We expect an MVP to be available by end of June. It may be available earlier if you're happy to test it out earlier - let me know if you're interested in this.
We're building it in two milestones:
1. You will be able to rename Managed Teams from the team profile page (by end of June).
2. You will be able to rename Managed Teams from Atlassian Administration itself in-context (by early July - will get back to you on clearer the dates).
Appreciate the great feedback! It's the least I can do knowing this is blocking your teams. Thanks you for helping with this :)
I know from a lot of components in Jira that the name is basically the primary key - that means if the name changes, other dependencies break (rename a workflow status, a request type -> you need to fix every automation rule afterwards). What could this upcoming renaming functionality potentially break?
It doesn't break anything native - renaming Teams is existing functionality that flows through to other components/features downstream today. The only thing I could think of is custom automation with JSON, but this uses the team ID, so it should be fine (unless for some reason, you're using team name), which is unlikely.
When the MVP doesn't incorporate an API endpoint and event logging, how likely is it that these get added afterwards and aren't just left out? ;)
They will both be worked on after the MVP. From now on, we're making it a prerequisite that event logging and API endpoints are built for all events. I'm speaking with my team about timelines and will get back to you on more refined dates.
We've started rolling out the ability to rename your managed teams in the team profile page. Appreciate you all going out of your way to provide feedback - that has helped us get this prioritised.
I made a post about the new feature in this community group here. It's not in other public forums as it's still rolling out and currently at 5% of customers. It'll be 100% next week onwards.
If you don't see it and need it urgently, let me know and we can turn it on for you earlier so you can test it out. Would appreciate any feedback 🙏
@April Chi have you all thought about a way to allow additional members to be added into a Managed Team by non-admins that is connected to a Group?
We have some Groups that are SCIM syncing and others that are just in Jira and both of those may need to be a Team and also may need to have non-admins edit them (maybe SCIM synced can just add people outside of the group and only remove them too).
We have a lot of needs around Teams...
search for membersOf in JQL to build filters/dashboards/automation/alerts on
have people add people to their own Teams (and in some cases remove people)
set the Team on work items
share requests in the JSM portal so everyone can see every request from their Team by default
filter user fields to a subset of Teams
only show certain Teams in the Team field itself for each project (contexts)
workflow/project permissions/roles by Teams
and more that I am probably not thinking of right now
Essentially, right now we need every feature from Groups, Teams, and Customer Organizations to be aligned because each of those things are slightly different groupings of people that need all of the same things in different scenarios. We use them for incorrect purposes just to hack together a particular feature.
Team seems to be the new user grouping that is getting the newer features, but will it soon level up in some of these areas?
I realize I just asked for a lot, but once I was thinking about one aspect, I started thinking about all of it.
have you all thought about a way to allow additional members to be added into a Managed Team by non-admins that is connected to a Group?
Are you asking whether there is a way for non org admins to connect Teams to a Group?
Also acknowledging the need to level up Teams - would you be free for ~40 mins to talk about the all features you need the use cases? I can tell you we're already looking at some of those and would love to share some concepts and news with you but also make sure we're on the right track.
@April Chi yes, I can sync up. In regards to that question, I was wondering if there could be a concept of a blended Team.
That way, a team could have people added and removed automatically from group changes (I am thinking mostly about the Active Directory sync into a group here keeping certain members aligned in the Managed Team). But then the same Managed Team can also have other members added manually into the Team that would work in the same way that a non-synced, "normal"Team does. That way, a Team could be a combination of a group and other people that are helping with items within the same work in Atlassian.
Essentially, it could be good if a Managed Team could have 3 configurations: fully locked/synced like now, Open, and Closed
Ideally, we can let existing Team members or a "manager" of the team add people into their Managed Teams so that they can take advantage of people helping temporarily, always have new hires syncing in, leverage the JQL searches and other automation around membersOf("<group>"), assign work items to all of those people by setting the Team as a field, leverage the Team page and other new functionality, etc.
But maybe if normal Teams can just have all of the same functionality of Groups and Customer Orgs, it isn't as needed to blend them (still could have some use-cases though).
I haven't published an official post yet but thought to let you know that we've started rolling out the ability to rename your Managed Teams in Atlassian Administration itself i.e. in AdminHub and not just in the team profile page.
To use it, follow these steps:
1. Visit Atlassian Administration
2. Go to 'groups'
3. If you have a Team connected already, in the 'connected team' card, click the meatball menu, and click 'edit team name'
4. You can now change the team name to anything (the group name will not change)
As of today, it's available to 50% of customers but you should all see it by the end of the week. We built this based on your valuable feedback - please do let me know if you use it and have any thoughts/suggestions/bug reports 🙏
33 comments