Gary Spross Community Champion

Thanks @Tanguy Crusson!

@Tanguy Crusson, has this issue been addressed because I'm getting reports within my instance of this happening as well.

Yes, JPD is currently only available in Cloud.

Oh, yeah... A detriment of the Team-managed style project implementation of JPD. This hurdle being the case, I think you will need to do a comparison of the 2 dates to ensure the "End date" is after the "Start date": https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-compare--- Then,…

For the date fields, I'm not sure how "greater than" & "less than" will function... Can you share a screen capture of your "If" conditional check component? You should have options of "is before" & "is after" that you can utilize.

The "Affects versions" & "Fix versions" are system fields. The values provided within these fields are based on the "Releases" (aka "versions") within the project they are associated with. Note: Archived releases will not show in either field.…

You want "Cross-project Views". That's a feature in the Premium version of JPD which is currently in early access: https://www.atlassian.com/software/jira/product-discovery/premium.

@slmorton, Atlassian has an EAP for the JPD Premium version. This is the version that will include "View Permissions". I'm not sure what that means exactly, but I'm imagining something like your describing. The main issue is obviously that this will be a feature available only in the Premium version, so if you don't…

@Phillip Jones, the answer to this question may help guide you. https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Copy-value-of-the-reporter-creator-field-into-a-custom-people/qaq-p/2726412

I received the following response from Atlassian support: "LLMs can still generate different output from the same sources. Confluence AI Answers is probably using a different prompt than VA AI Answers and this alone can generate significantly different answers. The scope of the available pages is also very different…

@Nick Haller, the Delivery Progress & Delivery Status values are showing again for us. I haven't received an update on our support ticket though. Any idea what the issue was and how it was addressed?

Same for us (although we only noticed them missing as of yesterday). We had opened a support ticket with Atlassian, but still haven't received an answer. As of this morning, the values for those fields appear to be displaying again. I'm awaiting a response on our support ticket to find out what the problem was exactly.

@Nick Haller , we opened a support ticket about this issue earlier and are still awaiting a reply. https://support.atlassian.com/requests/JST-1024295/

I completely agree that the Contributor role is overly restrictive. I feel that editing a ticket that was created by you should be allowed for Contributors. I was thinking that having manual triggered automation rules would be a workaround for this, but unfortunately it appears that JPD still doesn't support this.

I'd love to see JPD get the ability to be created as Company-managed projects. This would solve for this issue, as well as the problem we are seeing in our instance with a ridiculous number of duplicated fields. Many of these fields come OOTB when you create a JPD project, so regardless of having a process in place for…

In the "Knowledge Base" section of the project settings, where the Spaces are added, I had to set the "Who can view" option to "All logged-in users". Before I changed that setting, I was getting the same "please rephrase" response every time.

Received a response from Atlassian. @ mentions do not currently work in Confluence automation. There is this ticket, although it doesn't specifically reference Confluence automation. I was told my support ticket would be added to the suggestion ticket. As a workaround, instead of utilizing the "Add Comment" component, the…

Hey @Rodney Dsouza _Atlassian Certified Expert_, I did open the support ticket, but haven't gotten an answer yet. I received a response that they were able to replicate the behavior and have escalated it for review. They will reach back out regarding whether this is a bug and if there is any sort of workaround. Will update…

Ugh. Thanks for the double check. I'm going to open a support ticket with Atlassian and see if they have any guidance. I'll report back with what they say!

I think you need to set the field using the "Additional fields" section (under "More options"). Not sure of the exact syntax (and this is untested), but below is my first thought: { "fields":{ "customfield_10061": "{{issue.reporter}}" } }

Thanks for the response @Nick Haller! Looking forward to an improved idea creation experience in the future.

@Tanguy Crusson , Can you give a timeline for the following? Are these things even on the JPD roadmap? * JPD Create dialog consistency* Create screen from inside a JPD project is different than Create screen accessed outside a JPD project * Ability to customize JPD Create screen by fields as opposed to aligning to a view *…

I don't know how I overlooked that. Thanks for pointing that out. What doesn't make sense is, if you open the "Create" dialog from outside the JPD project, it shows basically all the fields, including the Assignee field. If you populate the Assignee field and create the idea, it works and the Assignee field is populated as…

VOTE! https://jira.atlassian.com/browse/JRACLOUD-36740 and this one! https://jira.atlassian.com/browse/JRACLOUD-71967

Within the JPD project, you need to set yourself to the "Administrator" role. Navigate to "Project settings" -> "Access". Click "Add people" button.

@Anne Saunders, what do you attribute the drop off in interest to? Is it similar to my thinking that users would feel that it was "just another thing requiring updates"?

Well, that's disappointing to hear, but at least it tells me that I'm not crazy! Thanks for the response! Hopefully this is something Atlassian can address sooner rather than later.

@Morgan Watts, Atlas is being rebranded as "Platform Experiences". It seems, based on this post, that many of the Atlas features are going to be inclusive within Jira projects. This, to me, makes for a much more seamless experience. We have not begun using Atlas because when I researched utilizing it, I knew there wasn't…

Definitely not a fan of the inconsistencies between creating an idea inside vs outside of the JPD project. Upvote for: "Engineering is aware of these inconsistencies and will hopefully have a fix and/or improved experience soon."

"why leave it to the Market Place to address" This... It is maddening how often there is an issue or something that cannot be performed within an Atlassian product and the go-to solution is to utilize an app from the marketplace. The cost of the products themselves are high. To then be told you have to pay more money to a…