Tanguy Crusson Atlassian Team

@Nick Sweet done

Hi @Seth Mason , I think the issue here is that an issue link type always has 2 sides (e.g. "implements" vs "is implemented by"), so I'm guessing that for these 2 link types the 2 sides probably have the same name. Maybe the rest of Jira manages this differently and hides duplicates when that's the case? I need to check

Hi @Jack Arndt , if you are talking about 20 product teams and growing to 10, I would definitely recommend splitting into multiple projects. We have quite a few customers in that configuration. The main issue you'll find otherwise is people are going to start making changes that clash with each other in the configuration…

Unfortunately it's not possible to copy a project configuration yet but it's definitely something on our radar!

Hi @Sako Shimohira , it's not possible yet but we're currently adding an option to let you write any number you want there (instead of the 1-5 scale)

@[deleted] I don't think we'll create a specific "problem" concept. We talked to quite a few product managers and there all use different ways to navigate it. The most common ones I've seen: * Problem/Solution * Opportunity/Solution * Problem/Opportunity/Solution * Opportunity/Solution/Hypothesis * Idea/sub-idea Instead of…

Hi @Jan-Hendrik Spieth , the way you could approach it using the tool as it works today: * Create a "problem" vs "solution" idea type. * Copy insights from the problem to the corresponding solution. Rate them based on how important the problem is in the problem ticket, or how good the solution addresses it in the solution…

@Saulo Vallory done

@Josh Barron it's not a public thing, it's part of internal tooling at Atlassian. It enables us to switch the Jira UI to a feature branch in Bitbucket. We also have another one to turn feature flags from LaunchDarkly on/off. All of that only works in our staging environments. It's pretty handy!

@Ákos Botos We're currently building support for JQL, which would enable that. It's still going to take a bit of time before it lands.

It is not view specific, it a number of votes to spread across ideas. 

Hi @Dave Nicholson it's not supported yet but definitely something we plan to do at some point. We still need to figure out where these are supported in the overall UI. It depends what you're trying to do, but if it's to make sure people can describe different aspects of an idea we've seen teams use description templates…

Fields > create a field > field type: Votes

@Sarah Green think of it as a way to seek input: "If you had $10, how would you allocate it among the following ideas?". We found this to be a pretty effective way to get input from leadership or stakeholders. Voting for 10 ideas isn't the same as saying it's $6 for one idea, and then $1 for four other ideas. The way this…

@Luis Plaza we don't yet support a field type where multiple people can vote 1-5 for the same idea. instead we have a "vote" field where you can give everyone a budget (e.g. 10 votes) to allocate across a list of ideas. "if you had $10, where would you spend it?" Fields > create a field > field type: Vote Then you can just…

Hi @Charu Takkar , today there is one use case for which it's possible for users to get access to Jira Product Discovery without being assigned a product access, and that's for projects who have the project access setting set to "Open". Anyone on the site with access to another Jira product (e.g. Jira Software) is able to…

One not-so-great workaround I can think of - it really depends on how many options you have - is to create a separate field of type "checkbox" for each aspect. E.g. lyrics: checkbox field, usability: checkbox field That way you can do a filter on "lyrics:checked and usability:checked" The way the filters currently work is…

@Haddon Fisher it is not supported on sandbox. However you can create a new site to play with the app. https://www.atlassian.com/try/cloud/signup?bundle=jira-product-discovery (option: start a new site)

@Kevin Gentry done

Thanks for the feedback @Aaron Mosny . We're currently reviewing how the integration with Jira Software works. We're starting with fixing a bunch of issues in terms of how it scales first though - so we won't get to things like this in the short term yet. 

And happy new year to you too!

Hi @Ben Arundel - these embeds are currently not interactive, but we're currently reworking that whole area of the product (so you can share views with people with or without a Jira account and let them provide feedback in the form of comments, votes, insights). I'll make sure we review the Confluence embed as part of…

Thanks for the feedback @[deleted] 

Hi @Ivan Kovalov we don't have an importer for insights yet. But we have an API to create insights, if you want to go down that path. If so let us know and we'll share the details.

@Amanda Ward done

@Cory Smith would you mind sharing a bit more about what you use these labels for? Thanks!

yep @Cory Smith that's in the list of improvements we want to make. Chop chop team 😅 

Hi @Cory Smith it's a limitation of the beta but something we plan to fix before GA (general availability)- the ability to export insights. 

@Jeny Stoeva I think it may be worth us chatting to understand a bit more what you're trying to do. What we suggest you track in Jira Product Discovery is high impact ideas/opportunities/solutions - something that would be at the epic level or above in Jira Software speak. Basically: boulder-sized investments that you can…

Hi @Kamil Imański : 1. Yes 2. We can't share dates, but it's going to be in the next few months 3. We do not have a public roadmap. What are you after?