Tanguy Crusson Atlassian Team

As a general policy we don't communicate timeframes for features. 

Thanks Eric, that makes sense. If we could do this easily, we would, but it's going to have to be a pretty heavy lift, technically speaking (inline comments are not part of the platform @ Atlassian, they're a Confluence feature). So we're prioritizing this alongside other big features (like the ability to share views with…

Hi, it's a popular ask and something we're likely to address a bit later down the track. The app was built to help you with prioritization and roadmapping, but many teams have adopted it as their home to track delivery and status too - which introduces different needs the app is currently not optimized for. We're reviewing…

Hi! we've recently improved this so you can do this directly from the Jira Product Discovery UI: https://www.loom.com/share/8a5d24322c0248a8be6758a5f47a9244?sid=56c74c09-645b-4380-aa61-483e78429427

Thanks for the feedback @Yong Yang 👍

Hi there, yes, we do plan to support that (using the same custom field in several JPD projects) and the team is currently investigating how it can work for Jira Product Discovery. 

Thanks for the suggestion @[deleted] . It's not something we've added yet as there are a bunch of complications. E.g. if you have ideas that have a single date, others with a month, others with a quarter - and you group by that field, then it needs to make sense and there are a bunch of corner cases. We've put it in the…

Hi Eric, thanks for the feedback. It's not something we have on the short term roadmap yet, but I've logged your suggestion. Our recommendation for that is still to either comment on the idea, or link to a Confluence document from the idea's description. 

Thanks for the feedback @Alex Tsai , I completely understand. We're not able to prioritize this right now, but you can watch the community for updates (if and when we do, we'll make an announcement here). 

@David Laine it does it at the epic level (basically if you have 2 epics, one in progress, one done, it's 50% in progress, regardless of the number of issues in each epic)

Thanks @Matt Richards , I've replied to your comment there to explain both how / why we got there and where to from here. Hope that helps. 

Hi @Matt Richards , to be completely transparent here's a bit more about this: When we moved JPD from beta to GA we looked at different billing options. One of them was: everyone pays (at a lower price), or only some users pay. We settled on the latter after research. We then built that. The target solution for this would…

Thanks for the suggestion @David Nadri . We're starting to dip our toes there, starting from the basics (and building the infrastructure for it). Can't share much more at this stage, but we're definitely going to experiment with this, things like "summarize what people are asking for based on what's in the insights…

Hi @CC and @Gary Spross , that is correct, it's a current limitation: the issue creation experience is tailored to JPD when you are in the product, but when you're in other parts of Jira it still uses the classic Jira creation experience (and some things don't work great with JPD there yet). We do plan to clean all this…

Thanks for your time today @Carlos Chacon ! If someone else is facing this issue, where the number of billed users is higher than what it should be, here are 2 things: * Check out this video that explains how to check who is getting billed for Jira Product Discovery and common reasons why that number is higher than you…

@Carlos Chacon I sent you an email, should hopefully be an easy fix 

@Jan Kühne there are a few reasons why you may have more users with access. I've tried to cover the different cases here: Check out this video That being said, usually it's because product access was added to the wrong group, for example if you added product access to the jira-product-discovery-contributors group

@Lexi Sprague could you please check if this would help you? It's not from Atlas, but from Jira Product Discovery though: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Upcoming-product-improvements-Atlas-integration-ready-for-early/ba-p/2195274

OK the issue should be fixed now

OK that should be fixed now

@Jack Arndt We've reimplemented all this, and we're about to roll this out in the next couple of weeks - it won't have this limit

@Selena Brown @Teal Nissley sorry! the form is now open for all

Yes, it should have been fixed shortly after this message

Tagging @Rachel Lin from the Atlas team for this one!

@Mark McPartland you're right, we don't support tagging customers to an insight yet, it's something we plan to add in the future. The insight shows as coming from the person who's added it to the idea.

Hi @Jaime Laird , you are right about #2, it's a limitation. As for #1, they can add the insight after creating the idea.

Hi, just confirming that this isn't possible currently. Thanks for the feedback!

Hi all, it looks like this issue's been open for a while and it slipped through the cracks, we apologize! Basically this happens because you are trying to assign an idea to someone who is not a creator (doesn't have a license for Jira Product Discovery). You can only assign ideas to licensed users (it's deep in the Jira…

Hi everyone, we apologize, it looks like this issue's been open for a while and it slipped through the cracks! Basically this happens because you are trying to assign an idea to someone who is not a creator (doesn't have a license). You can only assign ideas to licensed users (it's deep in the Jira platform, not something…

Hi @Mia Appleby , that's what a contributor is (you either need to have a Jira license, or if you don't, then you need to be added to a special user group) Details here: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/The-different-types-of-users-Creators-Contributors-and/ba-p/2378354