Nick Haller Atlassian Team

@Sree Kanuri - You are correct. Apologies for any inconvenience. There is a known bug with JPD templates at this time where the fields are not showing as expected through the create idea form (based on the view selected). Engineering is aware of this issue, and working on a fix. Thank you in advance for your patience.

Hi @Lisa McCann , I believe it's always been the case that a requirement for this is to be a Jira admin as mentioned in the Importing your CSV file of that documentation: Once your CSV file has been prepared, log into your Jira Cloud site as a Jira administrator to start the import process Are you noticing a different…

Finding Atlas project ID using GraphQL When viewing a project in Atlas, the URL will follow a format like this: https://home.atlassian.com/o/<org_ID>/s/<cloud_ID>/project/<project_key>/updates ^ But the project key cannot be used during the import to correctly map an Atlas project through the CSV. The project ID is…

@Brandon Aguilera unfortunately they are not at this time. Mentioned in this page.

Hi @Bill Sheboy , As far as I'm aware of, {{destinationIssue}} is dependent on a link-type between two work items, ideas, etc. I'm also unsure of whether or not there is any official documentation about this, but our knowledge base does have a handful of resources about how to use this.

Hi @Venkatesh Bojja , I configured an identical automation, and believe I followed the linking you mentioned where: * JPD idea linked to Jira delivery through idea's Delivery tab * Other Jira work item is linked to JPD idea through "Relates to" link-type But cannot seem to replicate the behavior you're describing where the…

Hi Seth, That is the newer UI, where the older one (I mentioned above) is nine squares. Under a site with the newer UI enabled, I was able to replicate this same behavior. I will get this feedback shared with engineering and product. Sorry for any inconvenience, but thank you for bringing it to our attention.

Hi @Seth Mason , If by "4 squares" you are referring to the "Your apps" icon in the top left of the UI, I cannot seem to replicate this issue. Following those step, I continue to be brought back into the same view selected in the JPD project previous to leaving. The same goes for if I am in the project's Settings, and one…

Hi @Seth Mason , Unfortunately it's not possible to edit the quarters available in a timeline view to better align with your fiscal year. Calendar quarters are only offered at this time. I'll get this feedback shared with engineering and product. In the meantime as a workaround, consider selecting the months option/scale…

Hi @Lene Riis Jeppesen , At this time it is not possible to toggle off the field's icon, but feel free to share this feedback directly with our Product team within JPD under the Give feedback tab.

Hi @Amulya Sankara , It sounds like this Question might be more related to Jira vs. Jira Product Discovery. You have opened this within the JPD Community - so do want to ensure we are providing the best possible answers. I would also like to note that if this is related to JPD - JPD only offers team-managed projects at…

Hi @Annie O_Brien , Not sure if this would help, but you could consider using a combination of field(s) and insights within a custom formula. The field could represent the customer(s), while the insights record information of each customer's problem statement/reason why each customer wants the idea. Maybe something like…

Hi @Afrothiti Manolis , Thank you for sharing that additional information. I believe JPD dates-fields are simply not supported at this time to be edited within the Filters tab like other fields. I also believe this is the case with Jira date-fields as well. This is based on a quick test, so I could be wrong on this matter.

Hi @peter dassenko , Not sure if this will help, but you can link the correlated / "child" ideas to the "parent" idea (which I believe would be one of the GMV ideas in your case). Whenever you link ideas to a "parent" idea, they increase the total number within the Linked issues field: You could then use the Linked issues…

Hi @Seth Mason , I believe the view that appears when selecting a project will be the one that was most recently accessed by the current user - so it's essentially cached. Are you hoping for a specific view to appear by default when accessing a JPD project for all users, only yourself, etc.? Let us know whenever you have…

Hi @Afrothiti Manolis , JPD global fields cannot be edited within the JPD project. It sounds like that might be the case with this/these fields you are referring to. They need to edited under the Settings >> Products >> JPD Global Fields tab:

Hi @Mike Wilk , The "Polaris issue link" should be the Implements / Is implemented by link-type which I do see in your screenshot: As for the issue related to the Score / user's permissions, I do understand the use case, as well the inconvenience it may cause - but this is more of a general Jira query than JPD, and…

Hi @Mike Wilk , Hope that Article helps! I don't believe the Polaris issue link has changed recently. Having said that, there was a time where Engineering did change the link type - but I'm forgetting what it was changed to... You could find the link type between your ideas and deliveries using the API on an idea that has…

Hi @Gary Spross , I had responded to that previous post, and did not think of a workaround until this Question. Maybe the suggesting I provided in this post will help in the meantime!

Hi @Michael Mackuliak , You are correct. Creating deliveries does require a JPD license. I think a way to essentially bypass granting additional JPD licenses is through automations - as long as the Actor of the automation has JPD permissions (whether that is the A4J user or a creator). The automation could execute when a…

Hi @Natalie Keane , If this is related to JPD, it's important to note all JPD projects are team-managed, meaning their statuses, workflows, schemes, etc. are managed within each project. A new status can be added within each project's Settings >> Workflow tab. Also important to note editing a project's Workflow is a…

Hi @Tim Sanford , An automation like the one below should work for your use case: ^ When a Jira issue is transitioned to Done, the rule then transitions any linked issues / ideas to Be Gone! Note the Scope of this rule is set to Multiple projects with both the Jira and JPD projects selected. Another thing we're noticed…

Hi @Andy Love , There is a known issue with the A4J user where they are not granted JPD product access, and that could be the case with the issue you are currently facing. As you mentioned, the workaround until this is fixed by engineering would be to adjust the Actor to a JPD user who has permission to add a watcher on an…

Hi @Andy Love , Although it may seem it's only possible to select a static user within the Add watchers condition of an automation, it is possible to enter a smart value. If you wanted to add the assignee of an idea as a watcher when the assignee is updated, you should be able to configured something like this:…

Hi @Steve Moser , Thank you again for bringing this to our attention. The documentation should now be updated and better reflect the actual experience.

Hi @Steve Moser , Thank you for the feedback. I agree the wording could be better, and might need to be adjusted. I'll share this with our team! As you have discovered, it is required a date-field is selected for both timeline view's Start date field and Target date field in order for the view to become editable.

Hi @Eric Seeley , Doesn't look like this is currently listed on the JPD public roadmap, but maybe it falls into JPR-15; Goals and Projects integration (ex Atlas). Regardless, as a workaround - consider creating a hyperlink field(s) that represent the Atlas project, goal, etc. These can be published, and do show in the…

Hi @Glenn A , Apologies for any inconvenience this has caused. There is not much of an update to provide on the fix for this at the moment. In the meantime, I do believe you should be able to set the reporter on the Jira issue, and copy the idea's reporter to the issue's reporter field. For example when creating a delivery…

@Tara_Westgate I'd assume this is a permission issue then because linking to ideas is a creator permission - and due to the user having Jira permission, but not JPD permission - could be the cause. It'd be worth testing the same scenario / workflow to see if a creator can add the link, and not the contributor.

Hi @Gary Spross , I believe this would be more of a Jira permission based on the workflow you mentioned; linking an idea from the Jira ticket. If you were to add this user(s) or group(s) to the project's Settings >> Permissions tab >> Link Issues permission, and retest - do you run into the same issue?