Nick Haller Atlassian Team

Hi David, Custom people-fields allow you to configure displaying either the users' avatar, or full name with avatar on ideas. The Assignee is a system-field, and system fields cannot be edited - which is why this flexibility might not be offered at the moment. I know the functionality also differs from List to Board view -…

Hi @David Nadri , Thanks for clarifying! That makes more sense. At this time I don't believe it's possible to display both the user's name and avatar in a Board view. But I also believe this is by design due to this type of view being more compact so it's compacting this field/assignee as well. Feel free to provide this…

Hi @David Nadri , Users' avatars and full name should display when selecting an assignee: But only creators can be assigned an idea, while custom-people field(s) can be assigned to any contributor or creator.

Hi @Andy Keohane and @Mari-Ann Eriksen , It's currently not possible to add attachments to a JPD idea at creation. The workaround is adding them after which we know is not ideal and requires an additional step - but both creators and contributors can do this. There is already an open ticket for this entered with…

Hi @Violeta Tamašauskienė , It sounds like there might be some sort of Filter set that is "removing" some of the ideas from appearing in your timeline view:

Hi @Karla Garcia , No updates on this feature request at the moment, nor an ETA on when this will be released. In the meantime the workaround is adding the attachment(s) after the idea is created. We know it's not ideal since it's an additional step, but contributors can add attachments to ideas even if they do not have…

Hi @Mari-Ann Eriksen , As mentioned above, that is related to your A4J (Automation for Jira) user not having the correct permissions to preform rules within JPD. Not entirely sure it's a bug, but we're aware this has been happening with customers lately. If you open a ticket with JPD support - they can assist with granting…

Hi @Michelle Kha , It sounds like you might be trying to use the existing archive template, but if that's not the case and you are unaware - there is an already existing template within each JPD project to easily configure an automation that archives an idea when it's transitioned to a Done status: The error you…

Hi Bruno, Thank you for sharing that. Testing in Postman with the same body shared above, I created an alert as expected with the details (extra properties) added as expected: One thing I would suggest also reviewing is the create alert action being used for this alert in the API integration. Maybe the action is wiping the…

Is there any chance of sharing the actual JSON and not just the structure? If not - I would suggest reaching out to Opsgenie support so they can take a deeper look into your instance and review why the details are not being added through the alert API.

Hi @Bruno Willian Conke das Neves , The JSON body (which looks correct) you shared compared to the screenshot looks to be a for different alert? I would check the Logs tab to see if the request was received by Opsgenie. If the request was received - but an alert was not created - then this Community post should help…

Hi @NAYANA , This other Community post might help with enabling your contributors to create ideas: Letting contributors create ideas in a Jira Product Discovery project As well this doc; Add a user as a contributor - which outlines how a user is considered a contributor: Contributors must meet one of the following…

This doc should help: How to find any custom field's IDs

Hi @Dan W , JPD is available for all customers, but only offers a Standard (and Free) subscription at this time. You can view this on our pricing page. Releasing a Premium subscription is on our roadmap, but no firm ETA on when this will be released.

Hi @Michaël BELVAL , As @Tanguy Crusson , JPD date-fields use a custom format which is essentially a date range. So in order to import an idea (or ideas) into JPD, the dates will need to follow a similar formatting to work as expected. For additional context - if you were to run a JQL within the Filters tab of your…

Hi @Kim Steele , It's not currently possible to use date-fields within custom formulas, but we do have an open feature request for this functionality already entered with engineering. JPD FRs are not publicly available to follow, watch and vote for like other Atlassian products, but that ticket for reference is:…

Hi @Andrew Cetinic , Thanks for your feedback. Engineering is aware of this - as we do already have an open feature request for this functionality. Although JPD feature requests are not public to follow, that ticket for reference is: JPD-118; Ability to add attachments on the idea create screen

Hi @Martijn ten Caat , Thanks for your feedback, we'll be sure to share it with engineering. Feel free to share it as well within your JPD under the Give feedback tab. As for some sort of a workaround (since required-description part of the vote field option cannot currently be disabled), you could create some sort of…

You can connect with Opsgenie support for assistance. They will be able to review your instance, logs, etc. - and provide suggestions. It will also prevent you from having to share any information or screenshots here you do not want publicly available.

I would suggest reviewing the Logs tab to see if the date is parsing in a field or the payload so it can be extracted into the alert. Typically we see customers leveraging string processing or regex to extract fields / data into alerts.

Hi @Taha Husain , My suggestion above is only related to the Email integration. Are you using an Email integration, or another integration? If you are using another integration - then you would need to review the Logs tab to see if there is a date field that can be extracted from the payload. If yes - then you may want to…

Hi @Roeland Schoppers , It's currently a known limitation - with the workaround to use an automation to copy the idea's description, attachments, etc. to the delivery ticket when created. You can find that configuration at the top of this other Community page: Product demo: Automation for Delivery - but it might look…

Hi @Joel Tan , Creators can add other Watchers to JPD ideas if permitted. Managing Watching is a global permission under the Permission schemes tab: If a creator does not have this global permission assigned to their role, group, user, etc. - they will not be able to add watchers other than themself on an idea.

Hi @Joel Tan , As @Tere Pile - modifying reporters is a global permission under the Permission schemes tab: but only Creators can modify the Reporter (if permitted). Contributors do not have this permission regardless of whether this permission is enabled or not.

Hi @Holly Holbrook , JPD does not have an out-of-the-box solution for this currently. Having said that, we see some customers leveraging automations as a workaround to create JPD ideas when a feature request is raised in a JSM project. This rule might look something like this: * WHEN: Issue Created * and IF: Project = JSM…

Hi @Mélanie Liguet , We've noticed other customers encounter this problem in the past and receive the same error, “App doesn’t have write access“ while integrating with Slack. Please open a ticket with JPD support here: https://support.atlassian.com/jira-product-discovery/ We should be able to assist with getting this…

Hi @Solaiman, Raouf , I've gone ahead and created an internal feature request. For reference, that ticket is: * JPD-146: Ability to customize quarters within timeline view JPD feature requests and bugs are not publicly available like other Atlassian products, so we do suggest following our Community for updates and…

Hi @Andy Nortrup , I've gone ahead and created an internal feature request. For reference, that ticket is: * JPD-146: Ability to customize quarters within timeline view JPD feature requests and bugs are not publicly available like other Atlassian products, so we do suggest following our Community for updates and releases…

Hi @Carlos Garcia Navarro , It's only possible to group ideas by one field per view at this time. I believe this is by design with the logic being - if it were possible to group by more than one field, there could be contradiction of ideas grouped, or overlap. Can you explain the use case a bit more? My guess is you might…

Hi @Shawn_Giese , After some testing, I don't think it's possible to limit Slack to only having select fields available when creating an idea with /jira create like it is with JPD templates / Customizing an idea form. I'll get some sort of feature request entered in the meantime.