Tanguy Crusson Atlassian Team

Hi @Pintu Sethi , to do that you'll need to create different views (one for each stakeholder group). Could you share more about why you use different dates so we can inform how we improve this going forward? thanks!

HI @Brian Pearcy I wasn't able to reproduce this - if the error is still happening for you can you please raise a support ticket? We may need access to your site to investigate. To raise a support ticket: * From JPD: top right of any view > Feedback * Choose: "get help from the support team" * In the text box: "Tanguy…

Thanks for getting back to me, and glad it worked!

@Daniel Gaviria can you please check what shows in the "fields" menu in the view? Do you see 2 fields there: "initiatives" and "initiative"? 

The rollout is going to start very soon - expect an article from @Olga Springer with the details

Hi @André it looks like we have a bug there - but even after we fix it, you'll still need to do something so your contributors can get the info they need from that view. Context: to be able to see the "Teams" object (Atlassian platform object) someone needs to be a paid user of Jira on the site. It's not available to…

if they didn't, you might have to contact Atlassian support

I can't help you with that - I don't have access to the systems that manage subscriptions and billing. Did the instructions above not help you? 

@Matt Hadfield yes connections work in published views. 

Hi @Freyr Gudmundson , you're the first person to ask actually! We missed that one, I've added it to the roadmap. currently we're working on:

Update: the team started working on it this week!

Nice one, thanks for sharing!

Hi there, thanks for reporting this, we're investigating!

@Thea Paar yes that is a current limitation of the solution that we plan to improve (it's on the roadmap) - currently the form only works if opened from the space

Hi @Peter Scobie , it's not planned yet but we've received that feedback a few times. Right now this is actually a technical limitation that we've only managed to overcome in board views (with a very hacky solution) - currently all rows in timeline and list views need to have the same height. We're going to reopen that at…

Hi @Can Peskersoy , I'm not able to reproduce this problem. I wonder if this could be tied to the specific workflow configuration in your space. To know for sure we'd need to get access to your site and investigate a few things. Could you please raise a support ticket? From Jira Product Discovery: * From any view >…

Hi @Edward McCluggage , you're right, these are your options today. That's why we're currently working on a new experience to deal with feedback and insights. here's a preview: Feedback app hero shots

Hi @Tere Pile , one thing I can think of it: what issue are you running this rule on? It would have to be on the linked delivery epic, not the idea itself.

Hi @Caleb Brunel I just checked and it looks like you're on Jira Premium but Jira Product Discovery Standard. That would explain why you're not seeing the feature. 

@Chris Lloyd it should work the same for all projects 🤔 The behaviour will depend on the field type: * Fields of type Rating, number, slider, etc. will return a valid value * Formula fields won't return a value (they're still calculated in the front-end) If you're seeing different values depending on the project, are you…

Gotcha - we'll let you know when this ships! I just chatted with the team and it's not a big change. We'll prioritise it. 

It would end up looking like this: 

@Jarmo Valli here's how it works today and how we're planning to change it: * You give access to a user for a space. If you add someone to a space they have access to all ideas within that space * You can then restrict which views users in a space can view and edit. But this permission is for the view object, not the ideas…

@Patrick Chen @Gary Spross @Joni Johnson I'd like to step back and describe a bit more where we're going with this: * How it works today: * JPD is built on Team-Managed Spaces. This means the configuration of each space is separate - fields, views, types, workflows * We've built support for Global fields - meaning you can…

@Charles Jamison I hear you. But I'm sure that as a fellow product builder you can appreciate that it's a tad more complicated than that 😅 I've been working on this product for a few years now and I can easily name 30 features that someone (or many people) would consider table stakes and we don't support yet. But in the…

> it is not Jira ticket due date I want to synch with, but the actual date the linked dev ticket went live. okay, that's where the problem is then. This feature was designed for when you use dates in Jira as due dates. So you can put your original high level estimate manually in JPD, but then it gets overridden by the new…

Hi @Tatiana Torset , Kamila and I were just discussing this and we're not sure we understand what's missing. can you please have a look at this and let us know how your set up differs? Thanks! https://www.loom.com/share/cbf92201cd5c4d19aad8baa294fe306d

Hi Tatiana, I can think of 3 ways: 1. Filter to only show Tasks, group by Goals. Con: the same Task would appear multiple times, not solving for "I would rather avoid creating false impression of doing more work that we actually are." 2. Create a board, filter to show Goals, add Tasks as a field It's the same as #1, except…

Hi there, it's definitely supposed to work. Can you please check this out? https://www.loom.com/share/a60ed017b75e4874abccbb489f511f2f EDIT: It looks like we have a bug - but although there's weirdness in the configuration UI the feature is still working as expected:…

Hi @Tatiana Torset , We're currently exploring something like this, so you can do exactly what you're asking for: For the moment, your options, as far as I know are: 1. Group by goals, and filter to only show the tasks (meaning: you can't see start/end dates for the goals on the view per se, but you can see all the tasks)…