Tanguy Crusson Atlassian Team

Hi @Denisa Holečková , here are a couple more details for how we recommend you do this. First things first, in Jira Cloud there is this concept of "sites". A site has a URL, e.g. xyz.atlassian.net. On this site you can add products, for example Jira Software, Jira Product Discovery, Confluence. So my advice here would be…

> And really what is the point of breaking the workflow and forcing users to work from outside of Jira especially if they are used to work with Jira? I never said we would. I just said we would share more details in a subsequent article. Please bear with us, we'll get there, and in the meantime you can enjoy the free beta…

All of this - your question and others in previous messages - I'll share in a subsequent article. We have a lot of pieces that have landed already and we're still trying to validate the final ones before we can share the details as to how this all fits together. Don't worry you'll have ample time to move from the beta…

Hi everyone, we're still working through technical spikes to validate the last bits of the pricing model, but I've just updated the page with 2 things that we can confirm today: * Yes, contributors will be able to "submit" ideas - via a form, the Chrome extension and chat apps. However they will not be able to edit these…

I see. While you are typing, the UI tries to validate your formula as you go. So, for example: "{Reach" --> invalid "{Reach}" --> valid "{Reach} * " --> invalid "{Reach} * {Im" --> invalid "{Reach} * {Impact}" --> valid We'll see if we can improve that so it's clearer.

@Terry Neff the system wouldn't let you type directly in the Expression field?

@Bill Stephens click on the value that was set (if the value is "4", click on "4"). That will unset it.

Hi @Martin , that's great to hear! There is an example for how to do that in the FAQ (under the section "How do I automatically change an idea when its delivery issues are done?')

Hi @Terry Neff , can you please share a screenshot for when you've typed the formula - what the app shows? the screenshot you shared just shows the placeholder text we have as an example for what you could type in that field. 

@Abhishek done

Great suggestion @José Carlos De Oliveira Escalona What you could do for now, maybe, is add a label "done" to the insight? It's not a perfect solution but at least could help you see which ones you've already addressed vs not.

Hi @Eugen Stolin , you are correct: the data in the project only shows if you have access to the systems that have this data. We're currently discussing how that should work when it comes to sharing 👍 In any case, it should not show what you're describing (make it look like nothing is happening) so we'll look into that

Hi @Paolo Pastorino , the date field is a hybrid field which can represent a period, e.g. "Jan-Mar 2023" which is modelled as {"start":"2023-01-01","end":"2023-03-31"}) In your case, if you are sure you'll always pick a single date, then you can always use a formula to extract it. I did an example in Google Sheets here:…

@Jan-Hendrik Spieth @Jack Arndt these fields are not accessible via JQL and the API yet (so not "true fields" in the Jira sense) - the computation of formulas is actually done client-side for the moment. We are working on moving them to the Jira backend, but it's not there yet. This applies to: formula, votes, reactions,…

Yep: add insights, comments, votes, reactions.

@Oliver Murray I spoke too soon, still need a bit of time to write this response - definitely early next week 😅 @Andy Keohane that bit I can answer already: even when contributors are able to submit ideas, they won't be able to edit them after that (that's a creator feature). If the solution works as we expect, when they…

@[deleted] done

Hi @Oliver Murray I'll answer your question tomorrow @Andy Keohane we got enough answers to the survey so we stopped it - the answer is pretty clear, so we've started a technical spike on letting contributors submit ideas and will share results soon - before we press play on the transition out of beta. 

Hi @Sylwester , same update as before - our recommendation at this stage is still to use templates. Can you please share more details about your use case / why you need that ? Thank you!

hi @Erik Lau , that's not supported yet but something we know we need to do. Thank you!

Hi @James Doyle that's coming soon - there's an engineer on the team working on this. After his change you can move ideas without losing insights, using the standard Jira bulk-move functionality. However remember that Jira Product Discovery is built on top of Team-managed projects, so bulk-move doesn't preserve field…

@Andre Groen there are thousands of customers using Jira Product Discovery today, and some pretty big instances. HOWEVER, in my opinion you should start with a pilot to test it out at smaller scale before going all in. Sometimes in very big instances there are things like add-ons etc. that can come in the way. However the…

We never communicate dates - we've been doing this for a while and as soon as you post a date in a public forum, Murphy's law hits hard, or Dementors start appearing out of nowhere. Sometimes even he who shall not be named himself. So: we're working on it, 3 out of the 4 founding engineers of Jira Product Discovery are on…

@Natalie Howell yep we're currently working on this

@Viktor Karlsson done @Raquel Cueto-Senra it's already on for you

Thanks @Amanda Barber 👏 you beat me to it

Hi @David McKee would you mind sharing more about what your challenges are? Thanks!

Hi everyone (including @Dan H , hopefully that will put your mind at ease 🙂) - we're currently doing a technical spike about how to make idea creation work for contributors. As part of this it would help to understand in greater details the scenarios in which people use this. There's actually a survey in the product at the…

Thank you @Jean-Emmanuel BANQUEY ! What you shared reminded me of the first lighthouse users we had. He wasn't a product manager but the CTO - and was keen to help the product team move away from requirements and time-based roadmaps. It worked pretty well for them, but it was a tough transformation. In my opinion "product…

> So it was meant more as a compliment, than criticism ;-) don't worry that's how I took it :)