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; } } }

Known limitations of Jira Product Discovery

Hermance NDounga

As we collect more and more feedback from you, we wanted to share the current functional limitations (and their eventual workarounds) in Jira Product Discovery:

Importing ideas has limitations

You can import ideas into a project using a CSV import, however:

Field settings, views and project settings won't be brought over through this method
You can’t yet import insights alongside ideas this way

We do not recommend using the Backup/Restore method with Jira Product Discovery projects as we are aware of multiple issues affecting the ideas and the project.

Project Automation is only partially supported

You can use Project Automation in Jira Product Discovery projects, with the following limitations:

Some fields aren't supported in automation rules, in particular:
- Formula fields
- Vote fields
- Insights field
- Delivery progress/status fields
- People fields
Project Automation doesn’t support triggers or actions for an idea’s Insights

Check out our article regarding Automation to learn some best practices

Cloud-to-cloud data transfer

You can now migrate Jira Product Discovery spaces from one Atlassian cloud site to another! This long-awaited capability empowers organization administrators to transfer Jira Product Discovery spaces - including their custom fields, configurations, and core data between cloud sites.

This first milestone migrates your key data, with some fields (votes, reactions), insights, and views to follow in future releases. Check out more details on what data can be migrated for Jira Product Discovery.

An Idea may look different based on where you open it from in Jira

Jira Product Discovery introduces new field types (delivery progress, vote, formula...) and concepts (insights, comments on views...) to Jira. Fields can also look different to the rest of Jira (colors, emojis, etc.) These new items have been built outside of the Jira legacy platform to bring more flexibility to Jira Product Discovery, but support for these hasn’t been added in all the places where you can open an issue in Jira

When creating an idea by clicking on the blue Create button in the top navigation bar, the idea’s fields are going to look different. We recommend using the "Create an idea" buttons in Jira Product Discovery instead
When opening an idea from the advanced issue search (Filters > Advanced issue search > search for the idea and open it) the idea will look like any other Jira issues, and you won’t see formatted fields, insights or the delivery tab.

Notifications

It is currently not possible to receive notifications for mentions in a view's comment or an idea's insight.

Support for Marketplace apps and API

Atlassian Connect, Forge / Marketplace apps aren't working in Jira Product Discovery projects yet, and the API for Jira Product Discovery artecfact isn't public.

Contributors who are also Jira admins cannot access JPD projects and ideas

Users who are both in the jira-admin and contributor group cannot access JPD projects. This is a known issue, affecting only non-licensed users.

Workarounds include:

Assign users to only one group, based on their role's priority.
Alternatively, since Jira Administration and Contributor roles are non-billable, you can create separate users for each group and switch between them as needed.

Comments

Erin Mihalik_ioq69y

I think the Team-Managed is a blessing and a curse. Yes, it sucks that the fields need to be duplicated for the fields that people are traditionally sharing. I'm assuming that is things like "Client/Customer" or "Product" or "Team".

The blessing right now though is that a Product Manager can come into the project and create their own field for prioritization metrics without the need for an admin.

For example, maybe the person managing a specific mobile app broke down the company OKRs further and on their filtered list, they want to add a "Mobile App Goals" field to use or maybe they just want to add a goal to it.

It would be awesome if JPD could maintain that all the "unique" prioritization metrics fields could still be created and edited by admins of the JPD project. Then have some sort of way for site admins to choose which fields are "shared" from the company managed "custom fields". Best of both worlds.

Aaron Mosny_w8h588

A few questions:

Are there plans to allow company managed discovery projects?
Is there a roadmap of planned features or changes?

The timing of the beta release has helped our organization so much! We cant wait to put it into practice on all of our teams!

Bill Sheboy

Hi @Hermance NDounga

Thanks for openly sharing this information!

You seem to describe that Jira Product Discovery (JPD) projects are instances of Team-managed projects (TMP). When this suggestion to share custom fields between TMP projects is implemented, will that automagically apply for JPD also? https://jira.atlassian.com/browse/JSWCLOUD-20905

And, there are known reporting issues when trying to consume information from both Company-managed projects (CMP) and TMP ones. For example, the design choice to have multiple story point fields. What, if any, limitations are known for JPD when trying to link to and report on issues from different types of source projects, CMP and TMP?

Kind regards,
Bill

Hermance NDounga

Hello @Aaron Mosny @Bill Sheboy 👋🏽

To answer your first questions, we don't plan to integrate company-managed projects in the Jira Product Discovery supported templates currently, but we are discussing how users could reuse configurations or fields across projects. We are indeed in contact with the team in charge of the feature request to see how this feature could be beneficial for us/ integrate with Jira Product Discovery projects.

Regarding limitations towards reporting on Jira Product Discovery issues, the same would apply then for regular team-managed projects, but when it comes to reporting in Jira Product Discovery, I would emphasize more on the "unique" field types that we've created for this product such as formula or vote etc... that wouldn't be available in Dashboard Gadgets for example.

We'll definitely update the community when we will have more clarity around this feature, but we don't have a pre-defined roadmap or release schedule since it can change quickly according to the feedback we receive from users, here or in-product.

Cheers,

Hermance

David Moore_wk72g0

Hi @Hermance NDounga , I just want to check if its possible to create an Idea via an API yet? You mention above that Connect, Forge Marketplace apps is not currently supported, but the status of the API wasn't mentioned...

If it is not supported, would there be any rough timeline to when that might be possible?

Thanks!

David

Hermance NDounga

Hi David,

We haven't exposed the Jira Product Discovery API publicly yet, however, the regular Jira Cloud API should work with Jira Product Discovery (for the commands that aren't for company-managed projects only). So in your example, you could use the Create issue command to create ideas in a Jira Product Discovery project.

Cheers,

Hermance

Ka Silveira

Hello guys! I've try to use a Discovery Project for manage ideas in my upstream proccess and generate the child epics but I have a big problem to manage my Jira Plans. We need to fix the hierarchy of ideias in Plans because today it is wrongly as Story Level. When ideas are displayed in the plan, they appear with the same level as standard issues but we need them to have the same level of an initiative (higher than epics).

Aaron Mosny_w8h588

Ka, I believe that this is intentional. Ideas are meant to exist along side or in parallel to any type of work, be it something as large as an initiative or as small as a story.

Forcing the hierarchy would break this concept.

Ka Silveira

Aaron... I understand that the idea can be something as big as an initiative or as small as a story but currently Atlasian forced the minimum hierarchy (Story) and this breaks the basic concept of discovery. I don't have the flexibility to configure the hierarchy and have forced minimum granularity. Within the Discovery Project there is a shortcut to quickly create children epics but they cannot be displayed like that in Jira Plans.

Erin Mihalik_ioq69y

@Ka Silveira The Ideas in Product Discovery are not part of the hierarchy at all. You link Initiatives, Uber Epics, Epics, Stories to the Ideas but they do not fall in line with the hierarchy. The way the "Deliver" section is configured, you are only creating or linking an issue, not nesting them below or above any level.

Matt Lane_ii5ifz

@Hermance NDounga @Tanguy Crusson

Hi Team,

I know configurations of fields etc are currently confined to an individual project, cannot be shared.

But wanted to confirm if this is the case for the new Idea Template feature, and if you will be looking to allow for sharing of Idea templates across multiple JPD projects in future?

Thank you.

Matt Stobo_br8jwb

Hi,

We are currently trying to implement Jira Product Discovery for managing a portfolio of work.

One outcome we want to achieve is roles with specific permissions. Those are:

- Create issues and edit only my own issues
- Manage all available issues, including comments, edit other people's issues, but NOT transition issue between statuses or modify views in the LHS menu.

At present, both of these roles seem to be possible to create via the existing permission set, but both roles are unable to create ideas at all.

Any advice on workarounds or possible solutions? If not, is there any current ETA on the JPD specific permissions?

Hermance NDounga

Hi @Matt Lane ! For the moment, there is no cross-project shared configuration, however, this is something on our roadmap. The templates could be part of this feature

Another idea we have would be to enable the creation of custom JPD projects templates, and reuse them to create a new project.

I'll make sure to include your piece of feedback around template as an insight for these ideas 👌🏽

Cheers,

Hermance

Hermance NDounga

Hi @Matt Stobo
When configuring a custom role, you can specify that the user is able to create issues, without giving them the right to transition issues.

Screenshot 2022-08-04 at 11.04.15.png

However, views are specific to Jira Product Discovery. Because we are reusing Jira Software permission scheme at the moment, unfortunately, it is not possible to assign permissions specifically to views management. This is one of the aspect of Jira Product Discovery we are planning to improve soon

Cheers,

Hermance

Ram Iyer_7tdio6

Hi @Hermance NDounga ,

Further to @Matt Stobo's issue above, here are some more details of the issue we are facing.

I log in as a person who has the following permissions:
- Create <ProjectName> Issues
- All permissions on "Collaborate on <ProjectName> Issues"
In the "All Ideas" view, I click on "Create an Idea"
Enter the "Summary", and hit "Enter"
I get an error saying "Something went wrong"
The idea shows up after refreshing, but I am unable to edit any of the other fields after that.

So with this permission, all I am able to do is, create an idea with the "Summary" (with the error message appearing) and am unable to enter any additional details.

Hermance NDounga

Hi Ram,

Indeed, after Matt raised it, our engineers did some more research and were able to identify that it was currently a bug.

When you notice this type of issue (error messages etc) don't hesitate to click the "Give feedback" button (we can see a little bit of it in your screenshot ) You'll have a direct line with our support engineers

Cheers,

Hermance

Robert Di Falco

Can you make any of the fields in Idea mandatory? Or can you only add optional fields. Also, it looks like there is no way to remove fields from the Idea form, is that correct?

Hermance NDounga

Hello Robert,

Currently, all fields are optional (except for the summary) primarily because of the inline editing of the list and the board view, which is the preferred way to create ideas in Jira Product Discovery.

The fields on the idea form are controlled at the level of the instance, so you can decide which fields to see on the form (Show fields > Custom fields) but it will impact the form creation for other projects - as they will also need to select the fields that are relevant to them, instead of relying on the default "all fields".

We are definitely considering an improvement regarding the idea form to make it more suitable for Jira Product Discovery.

Cheers,

Hermance

Screenshot 2022-10-03 at 09.44.35.png

Leshia_r1fzbo

A follow-up question for @Hermance NDounga response to @[deleted]question. I created custom fields that I wanted to add to the Idea ticket form but they do not appear under the custom fields option when I make a new ticket as an option to select them. How do I create a custom field and then add the field to the ticket?

hroy

1. Can we query on the Product Discovery space and build dashboards on it?

2. Is there a way to create tabs for templates that are used in the Product Discovery Ideas?

3. Can we use a Product Discovery Idea to become an Initiative that we can track using Advanced Roadmap?

4. Can we see a Kanban board across Product Discovery Board Ideas and the Initiatives we are working on in Jira software?

hroy

When is the GA version of Product Discovery coming through?

Adam Gardner_ldslq9

Hi there @Hermance NDounga . Just stumbled upon JPD from one of our vendors and are using it in its Beta state.

Few questions:

The Stakeholder Feedback option, any clues to when that might be heading to beta? It's such a key part of what we do internally, our organization would love to be early adopters if there is such an option.
Also, HROY mentioned a go live for a GA version and I was curious as well.

Thanks for being so responsive to all of the questions!

hroy

When does Product Discovery become an Company managed team in Jira?

Manuel Schneeweiss_53gfd5

We would need an issue collector. We want to embed that into our website, so stakeholders can report ideas via webform and issues for new ideas get created automatically.

Thanks, Manuel

Sarah Green_o0swk2

When I'm creating an insight, I'd like to be able to associate that insight with a specific customer. This can sort of be accomplished based on where the insight was created from, but it would be much more useful to add a customer's information as fields on the insight.

Is this planned for GA?

Ben Gallant

Not sure if it helps:

We've been using JSM TM as the "intake form" for our insights, using a form in our customer portal tied to a request type called "Submit an idea." We collect the details of the insight, engage with our customer on the request they submitted, and gather more details to let them know we're listening.

If the idea is new (there is NOT an existing idea in our JPD board), then we use Elements Copy and Sync with a recipe to "Send new idea to JPD project" - the recipe sends over the Summary and Description. You can choose to sync those fields so the reporter can see any updates to the Summary and Description from JPD back to JSM, and just use the comments to keep track of your thoughts around the idea in JPD to keep them away from the customer.

If the idea is not new, (there is an existing idea in our JPD board), then we navigate to the ticket in JSM, and use the JPD Chrome Extension to add this ticket to the idea. Be sure to select the text in the description that best captures that person's contribution to the idea! What a cool feature. Don't sleep on the screenshot feature either! Very useful.

We then move these JSM tickets into a done status called "Captured" (I'm sure there's a better name 😅) which updates the reporter, and makes them feel super good that their ideas are being taken into consideration!

From JPD, we start thinking about future work, and we use JPD for what it does best: help us know what to do next, and communicate that clearly to all of our teams.

We then create Epics within the JS board for our software team, and the JWM board for our business tasks.

We use wallboards and dashboards to communicate to our executive team.

We are investigating the use of Structure from ALM to gather more detail around capacity and long-term strategy so we can keep track of all of the work that is still to be done.

Here's a little picture of this workflow for your viewing pleasure. It's a work in progress and we're always tweaking it.

Any suggestions on how to efficiently track the Epic progress to ALM Structure to clarify capacity, would be much appreciated. Still digging through that one.

Mauricio Heberle_x42e0d

Please, add the possibility to copy a project and its structure (similar when we create a Software Project with shared configurations). Also, if we could use the fields we create with other projects would be so good.

Hermance NDounga

Hello everyone!

I will address the questions from this past month in this post since we have few updates;

GA/Pricing: We've recently posted an update regarding our future pricing model as well as GA announcement. There will be more to come, but we wanted to share already the few bits we had with our community as it had been requested many times. Don't hesitate to leave your feedback on that post.
Gathering feedback: As part of our future user model (contributors/collaborators) we are currently exploring the best experience to receive feedback or let users submit their ideas. Still on the post above, you'll see comments explaining their use case, and we are definitely taking them into account to work on this functionality.
Integration with Advanced Roadmaps: Currently we see Jira Product Discovery and Advanced roadmaps working hand in hand rather than one replacing the other. From one Jira Product Discovery idea can be created multiple Jira Software artifacts (initiatives/epics/story or any other custom type you have implemented). On Advanced Roadmap you can plan these stories amongst developers and have a granular view of which tickets is blocked by another, for example. On the Jira Product Discovery side, thanks to the delivery progress bar, you can have an overview of this progress, on a board, timeline or list view. We've detailed our vision in this article.
Company-managed projects: Jira Product Discovery projects will remain team-managed projects, at least in a near future, but we will be exploring ways to have shared configuration (fields/templates) even for this type of project.
Customer management: When using an integration (with Salesforce, Jira Service Management, or Zendesk) it is possible to surface the customer (as long as it is a property on the original link) on the insight panel in Jira Product Discovery. However we know the management of Key Customers in the product, via a column, for example, isn't ideal at the moment. Going towards GA, we will focus on the aspects described in this original post, but this one is definitely part of our roadmap.

Cheers,

Hermance

Clemens Grave_vy71u9

We are just starting to use Jira Discovery across teams. I am very impressed how intuitive and simple it is to use. We have decided to use separate projects for each team as it helps the PM to remain focused and only has to see all their ideas.

However, I would love to create alignment between the teams to uniformly view at roadmaps. For this a company managed feature would be incredibly useful, so I can define standardized Workflows and template views.

Overall a great tool thus far though

Erin Mihalik_ioq69y

@Clemens Grave - Does using views within one project not also achieve the desired goal? That is how we configured it. The idea is that a PM won't really ever be looking at or working from "All Ideas" view. They would only be looking at and working within their Views folder and can have multiple views. They can stack rank per view, filter and use their own custom metrics field per view. All the while, you can still maintain company level metrics and a company level roadmap view via an unfiltered "All Ideas" page.