Jira Product Discovery - views and the fields

[Boleslaw Nowak]

Hey everyone, first of all we really enjoy the piece of software that the Product Discovery brings to the table, and how it helps to manage things on the product side.

Wanted to ask about few things though - the field structure is not really clear to me, and their configuration:

How do I define those fields, is there a way to add/remove those from this view? It looks pretty similar to Jiras View configuration for issues, but I couldnt find the setting anywhere.

Secondly I'm creating a custom view - which is aimed for less tech-savy ppl which I wanted to be pretty basic, and simple to use as of reportin their ideas but when I would want to have a pretty simply flow within the view so the user creates an idea - adds its title, 2nd step I would want is to add the description which I try to add as a column in the view:

but I can't really add a description to it, I can only add something that's called `Public description` and `Short description` which both are those hidden "other" fields, and they don't correspond to the main description - which I don't quite get the logic. 

thanks for help in advance!

[Rohan Swami]

hi @Taronish Pithawala the App Selector shows which products you have a licence to, and we hacked together the Contributor role to get it out fast and the workaround is that it's not properly a role that's attached to JPD. 

But we're working on improvements to this! Contributor will be a real role that can be configured in site admin the same way you can configure a creator, and then you'll be able to see it in the App Selector. I'm not certain about whether that URL will work though, we'll find out as we get closer to release!

[Taronish Pithawala]

Hi @Rohan Swami

Thank you for your reply! I'm not sure if the release is imminent, but if not, do you have any recommended workarounds? How have you seen other organizations solve this challenge in the interim? 

[Rohan Swami]

@Taronish Pithawala actually I haven't come across this use case before. We've had customers try and get their contributors to a single project, not to a list of projects. But we'll keep your use case in mind for the future, thanks for sharing it with us.

[Taronish Pithawala]

@Rohan Swami to explain more fully...

We are a large enterprise with several products and product lines. Our product teams have created JPD projects specific to a product or product line. 

Our Contributors include sales and support staff that are not Jira Software users, or paid JPD users. Contributors need to be able to submit Ideas and Insights into the relevant JPD project. Our sales and support staff are not organized into teams that are specific to a product or product line... they engage with customers using a slew of our products and therefore come across feedback and insights for all our products and need an easy way to provide that feedback to the correct product team.

Going to a single place, where they can navigate to the appropriate JPD project is critical to a simple Contributor user experience.