Gary Spross Community Champion

I agree with this sentiment, but I also understand that the software Atlassian provides is very complicated with a lot of "tentacles". That said, I don't approve of this as an "excuse" for poor implementation communication though. I would like to see Atlassian provide a personalized "Product updates" feature. I would also…

@arajah , I'm referring to areas such as the "Issues" settings. Wondering if more consistency will be added to these screens. Example of inconsistencies/incorrect placement (in my opinion): * Actions* Most places have ellipses you click to see actions * Other places the actions are listed without the ellipses * Inactive Vs…

@arajah, thanks for the follow up. Are the UI changes just dealing with navigation or will the configuration menus be getting updated as well? By this I'm referring to the Issues setting area.

@Tanguy Crusson , But I like getting AND eating the cake! ; ) That statement makes me sound like a true customer, eh? We have been utilizing the Global fields feature for JPD. I do think it's intuitive and easy to navigate. I'm just not a fan of having different areas of the UI to navigate to in order to perform different,…

@Tanguy Crusson , I appreciate the transparency, as I've been asking about JPD having a Company-managed alternative at some point. That said, I do have to ask why the decision was made to go with what is essentially a "Team-managed hybrid" approach? I appreciate the introduction of Global fields, but it would be so much…

I would love to see JPD projects be company-managed style! Pretty please with a cherry in top!

I hear you @Jason Tatum! Several of the features that appear destined for the Premium version are things that we are in desperate need of and have been waiting for. Seeing the fact that Premium will be $25 per head compared to the $10 per head cost of Standard caught me by surprise. Making the decision to go premium is…

I'm really hoping this is something Atlassian is working on. We have 9+ JPD projects that we need to have a holistic view of for our ELT. Having 9+ different views just isn't feasible. We considered combining into a single project, but that would be overly cumbersome for the users working within each solution. Hoping…

As far as I'm aware, currently, it's all (like @Rob Mkrtchian _CAIAT_US_ indicates) or nothing with regards to required fields on idea creation. I would hope that there is something on Atlassian's JPD roadmap (although I don't see anything....).

This will make ALL of the fields in the "Create Idea" form required. Some fields aren't supported (and therefore aren't shown on the form), like in your example screenshot.

JPD (Jira Product Discovery) projects are team-managed style. Field Configurations are not applicable to team-managed style projects.

Hey @Benavides_ Fernando, Thanks for this response. I had come across this solution and it did work, but I forgot to come back to this post and update it to let anyone else who comes across the same issue know.

You are using the Component "Transition issue" to transition the issue AND edit fields (in this case the "Stage" field). Either you don't have a transition screen defined on the transition to your "Not Now" status or, if you do, you don't have the "Stage" field on the transition screen. To avoid the error, you have 2…

Unfortunately there isn't any workaround that I'm aware of. You can utilize a "team" field created within the JPD project, but you won't be able to associate users to the "team". It's really just a glorified label to help organize ideas. I guess you could create an automation rule to send an email to specific users when a…

I think the question being asked is if the Atlassian "Team" field can be utilized within JPD projects. Currently, the "Team" field (which is of the type "Team Picker") is not supported in JPD Global fields. Based on this documentation, the only supported Global fields types are: * label * text * URL * select * multiselect…

Almost a year later. Any update on the availability of the org chart?

Good thought! I'll look into writing a script to parse out the necessary data and then be able to put that directly into the Confluence document. Thanks!

Thanks @Ste Wright! After creating this post I found that feature request and voted for it. It's only 3 years old, so maybe there's hope! I figured it would end up being a manual process, so I guess I'll get started! Thanks for your suggestions on how best to document.

@Paul Northup, a feature called "Global Fields" is currently being beta tested. Although I still believe Atlassian needs to make it so JPD projects can be of the Company-managed style (along with the ability to utilize the normal custom fields interface), I do think this is a good compromise for now. It's good to at least…

https://jira.atlassian.com/browse/ID-7151

@Hermance NDounga, thanks for the response. Is it on Atlassian's roadmap to give the ability for JPD projects to be created as Company-managed? Outside of things like this example of contexts and schemes, there is also the more prevalent reason of having standardization in general. We are planning on standing up several…

There should absolutely be a way, especially when Atlassian considers users in these scenarios to be billable for Atlassian Access. VOTE: https://jira.atlassian.com/browse/ID-7697

"It's not available OOTB because it's a security concern." "Pay for this app and you can do it no problem!" WTH...

I'm glad this works for you, but I see 2 issues: * Contributors will be able to edit ANY idea, not just the ones they've created * Atlassian could make a change that undermines this work around, especially since it is indicated that the edit permission would need "Creator" level access Personally, I'd like to see Atlassian…

@Tanguy Crusson I just added the JPD Chrome extension and at first was not seeing any projects. I found this thread so I visited a JPD project, closed and reopened the extension and then that project showed up. I did the same thing after visiting another JPD project and then that project showed in the list as well. I hate…

I did a training/configuration session with a colleague yesterday and this question came up. I was surprised that there was not the ability to nest sections as there is definitely a use case for this. @Tanguy Crusson, tagging you for visibility on this one. Is this per chance something that is on the JPD roadmap? If so,…

Follow up! Support was able to get me going. Apparently the Forms API is "experimental" and requires 2 things I wasn't doing: * Add the header "X-ExperimentalApi" with the value "opt-in" * The URL format is: api.atlassian.com/jira/forms/cloud/{cloudId}/issue/{issueIdOrKey}/form/{formId}/action/submit * The URL goes to…

Hey @Bill Sheboy! Here's the rule as I've laid it out. The initial web request is pulling in the forms existing on the issue (there could be 2). The initial if condition is because, eventually, I want to do this for each form separately depending on the status the issue is transitioned into. The branch is to cycle through…

Premium plan. Appreciate you're help directing me to that API. I'll reach out to Support and see what they have to say.

Unless I'm overlooking anything, I don't see any hints. (Sent as an image because it kept complaining when I copy/pasted the text in.)