Tanguy Crusson Atlassian Team

Hi, I think you're describing this feature which is part of the Premium plan: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Feature-update-Hierarchies-in-Jira-Product-Discovery/ba-p/2983037

@Shalini Devi yes, groups should definitely work for this use case 👍

Hi @Nicolas David we've managed to reproduce a bug on this today - we're currently investigating to see how it appears. We might need your help to troubleshoot this on your site, if so we'll get back in touch. Thank you!

@Shalini Devi perfect. We're actually not going to support public views (anonymous access) for publishing views from Roadmaps for exactly that reason: figuring out what data to show / permissions is way too tricky

Hi, is this what you're trying to do? https://www.loom.com/share/0b25e28e9de640c288b469709b843f55?sid=3098e4a1-7efb-4666-bda9-3d6af70421d3

Hi @Shalini Devi - the team's currently working on supporting publishing views from Roadmaps. Question: what do you mean by "public facing view"? Did you want to publish it so that anyone on the internet can access the view without logging in (anonymous access), or just people from your company or people you add via email…

I'll share a Loom tomorrow to demo how that works and why you shouldn't lose any data or connection

OK that's why I was keen to confirm the impact you had: Connections are based on issue links, and these issue links stay even if you rename the types. All you need to do is to associate the connection field with the new type name and everything should be exactly as you left it. No need to migrate any data, no need to…

So actually this is incorrect: there is no need to "restore connections" - connections are based on issue links, and these issue links stay even if you rename the types. All you need to do is to associate the connection field with the new type name and everything should be exactly as you left it. No need to migrate any…

Hi @Freyr Gudmundson , just checking first: as soon as you updated the connection field to point to the new type name everything was back to working, correct? If so then I think we'll need to insert that warning before you confirm the renaming :) 

Hi @Stacey Steiger you are right, we've been kind of playing 3D chess on all this 😅 We're currently working with the Cycle team on envisioning what the future looks like for feedback and intake, and how that integrates with the rest of JPD (including hierarchies). And that's based on everything we've learnt when building…

The only way to show 3 levels is like this: * Level 1: Group by: Opportunity* Level 2: Filter the board to show: Type = Solution (those will be the cards on the boards)* Level 3: add the "Iteration" field Which gives you something like this: 

@Yuliia Vyborova I just checked what happened here and we had one bug last week where the connections tab was showing in the project settings > types and workflows tab. But even if you tried to use that you wouldn't have been able to go very far since the rest of the feature was unusable on Standard. We've since fixed that…

Hi, have you tried using the "Jira Software Cloud" Zapier connector? It should with JPD ideas (which are Jira issues in the backend)

What @Jeremy Drexler said! Connections are based on issue links. Here's a demo: https://www.loom.com/share/e4d9d28d168a43879807fbf7b1a4e675?sid=7593a9b3-f1b9-4e81-b7b1-7aa9cc992d83 The JQL I used: issue in linkedIssues("P2-728") and type=Solution

Hi Alec, correction, it's not people with Jira licenses but Atlassian accounts Atlassian accounts are user accounts and they're free. You can just send everyone you added (using their email address) a link to the published view and they can follow the prompts to create their account, or they can first create it by going to…

Hi @Antoni Abella Vendrell can you please share a screen recording for what's happening to tcrusson@atlassian.com ? that's weird, it's not supposed to work like that, and I wasn't able to reproduce your problem

@Maggie Cameron that looks like a bug! We're fixing it now, thank you

Hi, you'll need to contact support to resolve this - they have access to all the tools to troubleshoot situations like this

Correct: go go Project/Space settings > Types and workflows

Hi, that should work. Can you check instructions here? https://support.atlassian.com/jira-product-discovery/docs/import-existing-jira-issues-into-jira-product-discovery/

Hi there, here's what I can suggest: https://www.loom.com/share/2333d7f77fd94e6f963224c57a6c5fd8

Hi @Moses Dwaram , here's where to set this up: It's actually at the field option level

Hi, that is because you've selected this field as a highlighted field for Ideas To remove it, do this:

The team says they're hoping to start to get it out next week, but the usual disclaimers apply :) 

Hi, I think that's partly misleading. * There's definitely no need to recreate items with the new idea type. Just bulk select all the ideas and update their type and voila. * If you use a custom field to represent hierarchical things you can simply use bulk updates to change that to use a connection field instead (Demo:…

Hi @Nick Loe-Startup , we're currently working on supporting different configurations for the idea creation form (including the description template) per Type, which should hopefully solve your concern.

@Ellen Mowinckel Daleng not yet but we're working on it. 

Thanks for the feedback @Freyr Gudmundson - I think you found all the relevant pieces we have today in the solution, and current limitations. We'll look at your feedback as we evolve the feature

Thanks Bill, I couldn't have said it better !