Hermance NDounga Atlassian Team

Hello Template: You cannot edit the out-of-the-box ones :( So you can create your own using the "Create template" button from the form or from any idea description (1) Fields: The fields that will appear on the form are the fields that are on the view you will select (2). You can simply create a new view called "Form" and…

Hey Sundeep, Are you referring to the Asset field from Jira Service Management? If yes, then its not possible to use a field from another product in Jira Product Discovery. We will explore later on this year how we want to reference other fields in Jira Product Discovery. If you are referring to something else please let…

Hey Omer, It's not possible, the reaction field is really "free" and you can't limit it - I'm noting the suggestion in our JPD project tho ;) I have two workarounds for you, the first if you have a few specific stakeholders from who you need a clear opinion, second if you have a large audience and the "who" isn't too…

Hi Jessica, as mentionned by Gary, Cloud to Cloud migration isn't yet available for team-managed projects, hence not available for Jira Product Discovery. For the moment the only way to migrate would be to export your ideas in csv :…

Hi Omar, The Description field is a *shared* field , so it's the same between Jira Product Discovery and other Jira products. For custom fields - unfortunately I'm not an advanced user of Automation for Jira - you might need to open the "More options" JSON editor…

Hi Stefan! Based on your screenshots, it seems you have the right to create projects (at the level of the site) but you don't have been granted a license for Jira Product Discovery - as I see your product role is "Contributor" and not "Creator". In that sense, you have the "project-level" rights on this project you've…

Hi Karla, Sorry for the unconvenience, there has been some intermittent incidents across the platform that should be solved now. You can track them down on status.atlassian.com Cheers Hermance

Hello Lexi, I am guessing your devs primary tool is Jira Software. In that case they don't need to be creators on Jira Product Discovery. They can simply update their epics and story and it will be reflected in the delivery section for the PMs. And if sometimes they need to link an epic to an Idea, that can also be done…

Hello Rachael, Indeed we've just implemented this new warning so at least it doesn't get lost, but that could be our next iteration on it :) Cheers, Hermance

Hello Sabine, As Jira Product Discovery projects are team-managed projects, any fields you create in them are self-contained, and we don't prevent you to reuse the name of another field that exists in another project. We are aware that team-managed fields do not surface well in the global Jira functionalities (advanced…

Hey Karin ! 1. As soon as you click "create" a pop-up will apear to ask you to fill a value for the required field :) 2. Jira Product Discovery and Jira Software are two different products, if you need 30 creators in Jira Product Discovery you will need to license your Jira Software also in Jira Product Discovery. But…

Hi @Kevin Cocco , No it is not possible at the moment. Both your creators or contributors will have _access_ to all views when they have access to a project, you can only restrict what they can do in them. What you are looking for is the "Stakeholder role" which hasn't been released yet -…

Hi Peter In terms of formatting, I thought I could create a rule saying that "Date is overdue by xx days" but I just realize that with the overdue rule you cannot specify a number of days, unlike the "date is in xxx days" - so I'm actually adding that as an improvement suggestion 😅 On the other side, I've created an…

In this specific circumstance, while the bug is on Jira Product Discovery fields, it happens in the Jira Software interface (and we haven't tried, but it might happen for other Jira products. Your support ticket will be accepted, especially since we need to investigate this issue :) 

Hey Barry, Thank you for reporting this issue. Since I noticed you are in the new issue search experience, I went and tried myself and I have the same issue, not only with rating fields actually, and not following any specific pattern. The only workaround I could find was to go back to the "old" experience (it depends on…

Hi Barry, Indeed, filters in Jira Product Discovery aren't as complex as regular JQL ones. To do what you're looking for you would need to go on the advanced search of Jira, where you could write this JQL. I think for your use case (Project = XXX AND (Description is Empty OR Goal is empty OR Effort is empty), you can use…

Hi Benedict, At the moment it is not possible to "visualize" dependencies between Jira Product Discovery issues the same way you would on Advanced roadmaps for example. As suggested by Timothy, you could build a dashboard gadget per idea to see which ideas are linked to it, and I am not familiar enough with the Asset…

Hey @andrew.furness , That's actually a great suggestion that i will add as an insight both for our Chrome extension improvement, and our Confluence integration improvement :) Thanks for sharing this feedback ! Cheers, Hermance Product Manager @ Jira Product Discovery

Hey Omer, It's great to hear this solution could be a good workaround! The behavior you describe seems faulty, but moving ideas between projects is a "platform" feature, so regarding this one, you can definitely open a support ticket, so our Support Engineers can eventually investigate your instance to see why you get this…

That's a good point, we could surely improve the contributor experience in a self-service way. As the feature is just few weeks old wewill definitely look at feedback for a first round of improvement

We will be exploring better solution to move ideas in the future, yes. Oh! The merging solution would indeed be an awesome alternative to my "hybrid" idea. So you'd select the imported issue, merge it with the moved issue and keep the values and desc from the imported one. And the insights and delivery items of the moved…

Hi there, On my community post Automation for Delivery, I am giving example of rules, but the automation tool is powerful and every rule can be modified according to your use case. For example, the rule for linking 1 idea to 2+ epics, can easily be modified by removing the condition on the epic, and it becomes a rule to…

Hi Omer, The two ways you describes are indeed the only ways, and I would say that they can either be suitable according to your use case, but none is perfect cause they have limitations. * Moving ideas: The "Move" feature does not retain the values for team managed projects. As Jira Product Discovery projects are all…

Hi Robert, I've added your sugestion as an insights in our project, we already had similar feedback and we will take them into consideration when we will explore improvements around the board view.

Hello Dean ! Indeed attachements have their own permissions. Maybe in your project, you have created custom roles that aren't able to add attachements ? If you are a project admin, can you check that this permission is checked for the users who have noticed the attachement is greyed out? 

Hi Jing, For the moment, the contributors can only use the "create an idea" button that we can see on your first screenshot in the left panel, and it's in this one they would see your template. The top Create button is only for creators, and to be fair we would even recommend the inline idea creation over using this…

Hi Robert, Jira Product Discovery doesn't have an approver's role, as usually Product managers prioritize their ideas based on feedback they receive from other teams and customers, are the one making the idea progress during discovery, and are the ones creating Jira Software tickets when an idea is ready to move on to…

Hi Ohyoon, Indeed, Jira Product Discovery is very flexible and the fields that we provide you at the begining are simply examples, so you can tailor the project as per your needs. @David Carnes comment is on point - and thanks for sharing screenshots that show how you can customize a Jira Product Discovery project ! 1. You…

Hi Pete! The answer from Bill is the best to achieve this at the moment - unfortunately the NOT operator cannot be expressed in the JPD UI at the moment ... but we are planning to improve it so you won't need to switch to the advance search to do such filtering ;) 

Hi Sufian, Linking two tickets together shouldn't be an issue, I tested it on my site and a contributor/viewer in my Jira Product Discovery project, who has the permission in the Jira Software project to edit issues, can link an idea and an JSW ticket together. Can you please tell me via which interface they are trying to…