Tanguy Crusson Atlassian Team

@Lindley Tam we just looked at your screenshot: is it possible that you've added a value for the storypoint field in the epic?

Could you please send a screenshot that includes the whole screen (tcrusson@atlassian.com) - I'd like to check what's going on. Thank you!

Okay, that'll be "Discovery issue link"

Hi @Oliver Stutz , Yep, we had a bug which was faced by 73 customers. It should be fixed now. However the current project you've created won't work - but you can create a new project and it should work Projects > create a project > product management > product discovery

@Robby Keefer that's what I see. What do you see? Maybe a Jira admin deleted the issue link type? In this case, I think we automatically recreate it when you create a project or when you add a delivery ticket to an idea.

What a story! Thanks a lot for sharing @Tomislav Tobijas 👏 Let's launch "Jira Home Designs" 😉

@Joel Neutzner here's a demo for what we currently recommend: Idea intake in Jira Product Discovery We are going to look at this again once we're done with current commitments on the roadmap (idea intake). For the moment the solution is not great for that if you just use Jira Product Discovery. 

Yep, the team is currently building this - however note that the plan is currently to include it in an upcoming Premium edition for JPD. 

Good catch @Stephen_Lugton that was the feedback from the JPD engineering team as well - if you add them twice they're going to be counted twice

if you scroll all the way to the bottom you should find it (searching for it in the dropdown doesn't work for some reason...)

Yep empty field = 0

Hi Robby, I tried a few different things and found one way to make it work with manual work. Basically you need to first import the ideas, and then import the issue links separately: * First import the ideas into Jira Product Discovery via a CSV import * Then prepare the file to import the idea issue link in the delivery…

OK, cool. Have you tried giving a value to "Confidence" for one of the ideas?

Hi @Michelle same answer as last week: https://www.loom.com/share/c354fdfd133247d0b87c61f825bc61a7

That shouldn't be required unless there are spaces in the field names e.g. Reach * {Goal impact} * Confidence / {Forecast effort} would work

Hi ! First things first: do you have 4 fields called Reach, Impact, Confidence and Effort in the project? Maybe if you could share a screenshot with a view that contains these 4 fields and the formula that could help to troubleshoot what's going on

Hi @Abdalrahman Shatou can you please share a screenshot of what you're seeing? I suspect it's just about navigating to the right project (so it's not the Jira Product Discovery one another team must be using) - it'd going to be clearer based on that screenshot

Hi Robby, you should be able to do that: when you add a delivery ticket to an idea it creates a link between those 2 Jira issues with a a specific link type "implements/is implemented by" You can import those via a CSV import: https://community.atlassian.com/t5/Jira-questions/Linking-issues-from-a-CSV-import/qaq-p/2579648

yep, here's how we do it in the Jira Product Discovery team: Demo: a roadmap with 2 levels

OK, I think there's an option for you, but I'm not sure it's going to work - here goes: By default, the rank of ideas is scoped to the project - if you change the rank of an idea in a view, it's reflected across all views, the same way as field values work. However we've added an option so you can "detach" a view from that…

Hi @Gary Spross , I hear you, we can't have it all! That being said, you should check out the global fields experience for JPD: We plan to keep adding global admin options for things like fields, views and project templates but in team-managed projects while focusing on ease of use for the UX - I don't see us moving away…

Hi @Angie Adams we only show “DONE” if it’s only one item. We could also show the "DONE" label if all children are done - just a design decision. but arguable it shows less information then

Hi there! Jira Product Discovery is going to stay on Team-managed projects, however we're going to progressively make it so you can share configuration between projects - e.g. global fields, global views, project templates.

Great question @Atul Patil The way we've been doing this in the JPD team is moving the bigger idea to the Now section (as in: "we are committed to this"), and explaining what we're working on exactly in the description. Then, when we're done iterating, we either move it back to "next/later" or create a new idea "e.g.…

Hi @Yael Kropsky @Karina Caverly , today this is how it works: https://www.loom.com/share/c354fdfd133247d0b87c61f825bc61a7

Hi everyone, we're wrapping up the "productization" of the Atlas integration and are going to roll it out in the next few weeks. 

Ah yes, we need to improve the matrix view: click on the bubble with the 4 ideas then from the right sidebar you can drag and drop ideas somewhere else (Dammit I thought that would work!) --> Click on the bubble with 4 ideas, then from the right sidebar you can click to open the idea you want to move, change one of the 2…

The solutions are quite flexible, but our recommendation for this is more like: * Atlas Goal* JPD Idea* Atlas project * JSW Delivery ticket (epic)* story* task * subtask I quite liked this image from this LinkedIn post: 

Hi @Jason Tatum you should be able to do this in JPD. We do have an integration with Atlas, it's still in early access (but not for much longer, we're productizing it and it should be done in the next month or so) - you can see a demo here and ask for access there (2nd video in the post)…

Yep we do what @Rob Mkrtchian _CAIAT_US_ suggested in the Jira Product Discovery team. We use: * Jira Service Management for inbound feedback (when you send us feedback in-app) * Dovetail for user interviews * Slack for questions from customer facing teams * This site (community.atlassian.com) for discussions Here's a link…