nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

📣 Product update: You can now use Atlassian Teams in Jira Product Discovery!

Hermance NDounga

As a part of our ongoing improvements in fields management, we are thrilled to introduce a new requested feature: the integration with Atlassian teams!

Starting today, you will be able to find the “Team” field in all your Jira Product Discovery projects.
This means you are now able to:

Add the Team field to a view
Assign a Team to an idea
@-mention any Team in the description, comments, or insights
Find ideas on your teams profile page

Uncover The Revenue Potential of Our New Rewards Program (2).gif

The Team field is a global field, consistent with the rest of Jira projects.

To add the Team field in one of your views:

Click Fields
Toggle on the field Team

You can check the full demo, for users and admins

If you prefer to not use the Team fields across your projects, you can also remove it from the available fields list

> Products > Global fields
Find the global field Team (under "Jira fields")
Click on the column “Projects” and remove it from projects

We hope you enjoy this improvement and as always, leave us any comments and feedback below!

Cheers,
Hermance, Sr. Product Manager

Comments

Yong Yang

Cool Update!

It seems the previous customized team avatars were overwritten by the new versions of team avatars, which looks like a bug 🤦🏻‍♀️

Hermance NDounga

@Yong Yang Could you please share some screens of discrepancies you've noticed? We will redirect them to the Teams team

Tomislav Tobijas

Right one time for one of our projects 😄 Nice 1 and thanks!

Yong Yang

Thanks.

The below 2 tickets are related to this issue and I will communicate through them:

https://community.developer.atlassian.com/t/atlassian-s-teams-avatars-are-still-egress-but-not-atlassian-hosted-avatars-now-load-by-default/90371/4?u=yy1

https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-61408

caspero

This is great news. We are exploring the teams functionality across our instance - perfect timing!

charles_c666q8

Awesome feature, perfect timing for us 😗👌🏻 — thanks!

Mike Villis

Love it! Any plans to offer the ability to track multiple teams against an idea?

Some of our ideas are quite big and we manually populate a custom field with our teams to tag which if any would be involved with the effort to deliver.

Adam Risser_0vdcpz

@Mike VillisSame. We use a custom teams field that is global and shared across all JPD boards. It would be great to drop that custom field since we also use Atlassian Teams in other places. We'll hopefully wait for a v2 that allows multiple to be selected.

Troy Cope

Just some initial feedback here...

An Idea is generally a big problem / initiative to solve (at least in our company), and will likely impact many teams as it transitions over to delivery. We currently have a custom field for Team/s in JPD, and it's a multi select field so users can assign 1 or more Teams that are likely to work on that Idea once it transitions to delivery in JS.

So for now, we can't use this new global field, as it only allows you to assign an Idea to a single Team.

We have therefore unassigned this new field from all of our JPD projects.

Is it possible to look into this enhancement for future features in your roadmap?

RADIX-LEROY, Sophie

Hello,

we're really intersted in this new feature!

Indeed, we already have a custum filed in our ideas in order to join them to teams.

And that's where we have an issue with the new feature of Teams in JPD: we can only add one team to an idea. In our case we often have an issue that concern several teams.

I see that the last comment says exactly the same thing. We're definitly not the only ones that nedds to be an N/N relation! ;-)

Is it a possible upgrade of this feature?

Sophie

Vedant Kulkarni_Trundl

Useful feature!!

Nathan Mackenzie

Yea this is great... Would love to see it be a multi team picker 👌🏻

Hermance NDounga

Hello everyone!

The goal with this integration is to be consistent with the rest of Jira. The Team field in Jira is a single select and is the one we are integrating with in Jira Product Discovery. So it cannot (and will not!) be different from the one you'll find in Jira or Jira Service Management, as we are trying to address your feedback mentionning that Jira Product Discovery does rely on different feature than Jira to achieve the same things.

However, both the Team & People team and the Jira team are aware that this evolution would be useful for all Jira users, and as they are working on improving the whole Team concept, they may also upgrade this field and if that's the case, then you'll also benefit from it in Jira Product Discovery.

Best Regards,
Hermance
Sr. Product Manager @ Jira Product Discovery

flavien_3poquk

Nice feature but in our case, adding an internal team is not so useful. Just sharing our use case:

Each time we create an idea, we link the feedback
However, we want to understand all the clients who reported that feedback + add their MRR (or key metrics), this would help understanding the impact of a release.
Other metrics could be useful such as: The sales team reports a feedback and says "this is critical for the deal and the deal will bring us this amount". For now, Product discovery doesn't allow that and that's where the real issue is (in addition, we can't transform data from hubspot for instance to add extra info on clients who reported some feature requests.

These could help so much our processes and prioritization (instead we are looking for extra tools that could help us on this aspect which is a shame cause everything could be centralized in JIRA)

Matteo Nicolich

When dealing with a big initiative we might have multiple team working on it. We would like to be able to assign multiple teams for an Idea

gianmarco.spiga

+1 For extending this field to a multi-select. Any big idea involves multiple teams

Marc HINTON_a90i8g

+1 also indicating that it would be great to have the team field expanded for multi-select.

Paul Goujon

"+1 For extending this field to a multi-select. Any big idea involves multiple teams"

indeed. And this field being a single select thus prevents using it / forces the "creating another multiselect" workaround

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

announcement

jpd

new-feature