Tanguy Crusson Atlassian Team

Hi, you can use fields of type "Number" for that. Fields > create a field > Number (or rating or slider). Or multi-select fields with weighting, which now supports custom numbers as per what people asked in this post (which is a bit dated). 

Hi all, it's on for everyone above. We've also released a new Project settings / Access page that we hope makes it clearer what's going on. (We're also renaming project role - viewer --> contributor and team member --> creator but it may not be released yet) You can now make fields in the issue creation form for…

Hi @Jack Arndt , you cannot enforce this in the product today. The only thing I can suggest is telling people you expect them to do that 😅

Hi @Gadi Ben Amram , it sounds like you do not have a license to use the product. Can you ask your Jira administrator to give you product access to Jira Product Discovery in admin.atlassian.com, in the Directory section?

Hi @Jack Arndt , no only creators can edit fields. Contributors can: - create ideas (via a form) - vote - comment - add insights - add reactions

Hi @Sufian Siddiqi , it is not possible currently.

Thanks @Brock Jolet . That makes sense. I'd still be wary of exposing things like "delivery progress" to stakeholders as it focuses the conversation on the wrong aspects with them, but totally see where you're coming from. 

Hi @Stian Bentsen Sveen , this is not currently possible but is on our radar for when we revisit the insights feature.

The bug is fixed

The bug is fixed.

Hi @Brock Jolet , first off: I like your thinking: progress isn't really something that can be "computed". personally I like to use "On track", "At risk", "Off track" with a narrative instead of "80% done" (which is usually when the real work starts). You actually can create a field to something like what you described,…

👋 @Seth Mason - yes you can: search for "automation" in the FAQ: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Frequently-asked-questions-about-the-product-how-do-I/ba-p/2002378

It's a bug! we're on it

@Jack Arndt @Tere Pile Based on what you described I wonder if this solution that we're working on would work better for you after we've shipped it: https://www.loom.com/share/821ad544fbf14fc6bebb1ac892b0ecd7 What do you think? 

Quick update! It looks like we introduced a bug on that field a couple of days back actually, as we were rolling out changes to improve performance of the app (we have a team focusing on this at the moment). So you'll see this even if you don't hit the 1000 issue limit. It's going to be fixed soon. 

@Andreas Mouritsen @Chris Timms currently the calculation of the progress is done client side. That means that every time you open a project it goes and fetches all delivery tickets and their children to calculate it. Obviously that won't scale. We're moving all this to the backend in the next few weeks, which will make…

Thanks for the context, that makes sense. 

Hi everyone, we got everyone's feedback that it worked but was a bit confusing to learn, we're working on a new design, it's taking a tad longer than expected to land, so I've just turned the existing feature/design on for the people who provided their site URL above. Next step: we turn it on for everyone!

Hi everyone, we got everyone's feedback that it worked but was a bit confusing to learn, we're working on a new design, it's taking a tad longer than expected to land, so I've just turned the existing feature/design on for the people who asked above. Next step: we turn it on for everyone!

@Miriam Donath it's not hiding anywhere yet, we haven't added this yet 🙂 But it's something we know we have to get to!

Ah yes, good catch! We're on it, thanks for posting this @CC 👏

hi @Jack Arndt you are correct everything is shared in Jira Product Discovery by default. We probably need to find a different name than "pin" for this feature as the outcome is different to Jira Software and Jira Service Management. This feature is about making sure that some fields can be seen anytime anyone opens an…

ah yeah that's another workaround, thanks @Jan-Hendrik Spieth ! similar to my voting example below. Not ideal, maybe can help in some scenarios

@Len Bergman it's not possible today but it's a great idea. The only fields we have that are truly "multi-player" today are the Vote field and the Reactions field. It's a bit of a hack, but until we do that you could try using a Vote field for that: * You create the field, add it to a view * You ask everyone to come in and…

Thanks for the context @Kevin Gray and we'd love to hear how you go with your evaluation 👍

@María Ferreño Have you tried the APIs I shared above?

Hi @Sam Holdahl , this is something that is in our sights. what would need to happen: * You'd need to be able to share fields between projects * You could then create views that span multiple projects, based on these fields * We're not sure yet how we could deal with ideas that span multiple teams (e.g. one idea shared by…

Hi everyone, we're reviewing how everyone is using the integration today and deciding where to take it next. For now we're not going to turn it on for more people. Next step: we'll turn it on for everyone (after probably a few changes)

Hi @Sufian Siddiqi - it's not possible today but something that came up a few times so we'll probably look at it in the future. Probably too late for you though...

Hi @alicea I can't think of a way to do that today