Tanguy Crusson Atlassian Team

Thanks @Brent Vierling , that's great feedback. For that, we use Atlas internally at Atlassian - but that's internal, not with end users. We aren't really tackling the jobs of communication with customers and users today. It's a good topic for us to sit down and think about for the next stages of the product. 

@Catarina Vaz Fernandes every view is just a view in the same set of ideas. so when you create a list, a board, a timeline, by default it's got the same list of ideas that you can look at from different angles (different fields, different filters, etc.) Did you delete the ideas when you were in list 1, or did you archive…

OK @Sean Sullivan in that case it's about tracking down how these 4 admins were granted product access, and to remove it from there. There are a few ways this could happen: * The users were given product access individually * The site-admins group was given access to JPD * The site-admins group was added to the…

@Erik Lau you'll need to contact Atlassian support. There should be a link to do so from the page where you tried to change the edition

OK, yes that makes sense, because when you add then to the group you are inviting them to the site, not the project. You'll probably want to send them a link to the project you want them to participate in

@Sean Sullivan if you removed product access from the site-admins group then I think what's going on is that trusted users are still there. From this article: Trusted users will count as billable users by default Trusted users (a deprecated user experience) will also use a license for all products on site. The only…

OK - this is not a link to the project but the Atlassian site, which will redirect you to start.atlassian.net. To invite people to a project, you have 2 options: * open the project, copy the URL, and send it to the people you want to join (something that looks like…

What URL are you trying to open?

Hi @Ysaac Keith , yes that's easy to do: Open Project settings > Access Change the project role for each creator to "Administrator" This will give them the permission to create and edit fields in this project, invite other people, etc. Their admin scope is limited to this project. If you just want to give them the ability…

And just to be clear: it's not only a question of licensing. There's a bit of that, but there's also quite a lot of ramifications in the UX that aren't trivial, since you're able to edit ideas in a bunch of different places in Jira Product Discovery, and now we'd need to find ways to make it clear if you can only edit your…

Thanks David. Don't worry, we heard you loud and clear 🙂 We'll need to sit down and review that one when we can catch a breath. For now we're racing on a bunch of other stuff (e.g. the stakeholder experience)

1) sure, if you find a way to do this directly in Excel, perfect 🙂 2) yes, the only way is using the API - the CSV importer does not yet support insights (we'll add support for this later though)

I can think of 3 options: * you ask an engineer to get these fields from Aha! and append them to a description that you then concatenate to the Aha! description and import into the idea * They add it as a comment to the idea instead * they add it as an insight instead of in the description. Example of using the…

Hi @David Nadri * it is all or nothing, we're trying to keep things simple for now * you are right about the pros and cons of each option. Personally I'm not a fan of the solution letting contributors create ideas directly in the project. We use a Jira Service Management queue to receive feedback (when you click on "Give…

Not at this point but we'll look at this when we next review this feature.

Also, about your other issue: you should forward this to your admins: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Read-this-if-you-re-a-site-administrator-and-just-added-Jira/ba-p/2385379

Hi @Kate Smoliakova , that's because you need to be given product access to Jira Product Discovery (aka a license). More details on how to do this here: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Adding-contributors-and-creators-to-a-Jira-Product-Discovery/ba-p/2324017

Hi, This is not possible today. Only creators can edit ideas.

Hi, you can do both. * Everyone in the same project is the only option that lets you have a cross-product view of the roadmap (views today can only include ideas from one project) * Having different projects is the easiest way to make sure each team can configure things however they like There are teams using both methods…

Hi @Oliver Murray , that's because you've given them all product access, so they're all creators (and that's what you're seeing in this screen). Instead you want to add the non-creators as contributors. More details…

OK, we havent' been able to reproduce or find where your errors come from, outside of a few network error issues that should have been transient. Could you please open a support ticket? this way we can get access to your site and investigate. In Jira Product discovery: * left sidebar: "give feedback" * choose "get help…

Hi, just create as many matrix, board and timeline views as you like and use the filters to match the filters you set up for each of the lists.

@Brian Channell give this feature a try (turn off autosave) I'm not sure I understood what you meant in #2?

Thanks @Peter Heidorn , updated!

Hi @Neville Booth , mmh, first time I see this. Let us investigate!

@Karthiga Sethuraj sorry you lost me: what tool are you migrating from? (idea portal) Something you could do is import the text fields as insights (we have an API for that) or as comments (I think you can import comments via CSV, details here)

@Sebastian Pechhold I thought it was possible to export/import issue links. Have you tried something like this? https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-in-jira-740262715.html This way you can bulk create ideas, and link them to the issue in the Jira Software project (if you want…

@Erki Tammik the only way I can think of keeping this under control is to limit who is a creator in the project to the people who can be trusted to make changes to ideas there. Or, if there are different teams with different ownership, then organize it so they work in different projects. One thing we discussed earlier was…

@Jan-Hendrik Spieth it is going to be unlikely we'll be able to provide that level of granularity in the medium term. Not to bore you with the details but the Jira permission system doesn't support that in the first place, and then we'd need to revisit every view to make sure people can edit some ideas and not others. It…

That is correct. you can use idea description + idea description templates instead today.