Nick Haller Atlassian Team

Hi @Alex Shaw , Opsgenie’s Standard and Enterprise plans (or Jira Service Management Premium and Enterprise plans) each get get one incoming call integration / number included in the plan. Every additional line is $10/month. All mentioned in the plan pricing page. If you need a specific US area code or country code such as…

Hi @secutechconsultingservices , Exporting JWM issues, then importing them into JPD would create new ideas completely independent from the JWM issues - meaning any changes on the newly created JPD ideas would not affect any of the previous JWM issues (and vice versa). We would suggest following these steps to import your…

If an alert was created, there would be a log such as the one below (1) that shows the alerts tiny ID and "Alert created": Notice logs 2-5 - those are for deduplicated alerts/requests that increase the count of an already existing open alert. Maybe your request is being received and rolling into another alert. I would run…

Hi @Thierry BLOCH , It's not possible to delete the prebuilt offered create idea templates at this time, but you should be able to create your own (below), then apply it to your create ideas:

Hi @Ben Hart , At the bottom of our LogicMonitor documentation includes a Troubleshooting section that I would suggest reviewing: Troubleshooting test alerts These informational alerts denote that incoming data is for testing purposes only. Since testing data could differ from the expected data, we create an alert without…

Hi @Arnab Deb , This can be managed under each project's Settings >> Access tab where a user's role can be assigned - including the project-admin role: As you are aware, only project-admins can create, edit and delete fields.

Hi @Edouard Parison , I believe that should be possible with editing the Workflow of your project. Below I've configured one to what I believe you are asking with relation to the stages and statuses mentioned: Within the workflow you'll notice I've added three transitions after Discovery is selected so the idea can be…

Hi @Persio Simoes , It might make sense to create a field for both the Tribes and Squads, and individual Tribes / Squads for the values of each field. Then you could create a roadmap and/or timeline view that filters on the Tribe field, while also including the Squad field to be displayed in the view for better visibility…

Hi @Jira Clupik , If you are working in a board view, the color selected for each value should color the columns of the view like so: If you are working in a list view, you can enable the highlight option that will display the color selected with the value: For more on JPD views in general: Jira Product Discovery views…

Hi @Garrett Olsen , The order in which your ideas are shown would all be dependent on how they are being sorted, filtered, etc. - which you can control here: In the screenshot above, the ideas are sorted by the key in descending order - so all newer ideas would appear at the top of the view. If you have some sort of…

Hi @Mari-Ann Eriksen , I believe you need to escape the quotations so it might be something like this: { "fields": { "customfield_10034":"{\"start\":\"2021-04-01\",\"end\":\"2021-04-01\"}" } }

Not sure what parameter you are using in the URL, but can you try running a GET on the tiny ID of that alert to see if you have the same results? Your URL would be: https://api.opsgenie.com/v2/alerts/87312?identifierType=tiny This should return the extra properties in the details of the JSON body, and I'm assuming you…

Hi @Rakesh Panchal , I can't say for certain those aren't the same alerts, but the top screenshot in Opsgenie shows the alert being a P3, while your Postman screenshot shows the alert being P4 - which leads me to believe those are not the same.

Hi @Antonio Carvalho , That's a good suggestion. I'll relay this to engineering, but feel free to also share this within your JPD under the Give feedback tab - which also goes directly to engineering as well.

I don't believe it's possible to return the extra properties on a List Alert API. There's a sample response in the documentation and not shown in it is the extra properties (aka the details) of the alerts. So you would need to run an individual GET on each alert to return the extra properties, or create some script that…

Hi @Rakesh Panchal , If you are running a GET on an individual alert, the extra properties should return in the JSON body without any sort of query needed under the details of the alert: If you are trying to run a GET on alerts that contain extra properties, you would need to query on these using the details since this is…

Hi @TJ Baier , If a voicemail is left, it can be found in the notes of the alert:

Hi @Susie Barber , You should be able to manage this through each JPD project's Settings >> Features >> Create ideas tab: As you can see above, I've select the Simplified Template View which is a list view in my JPD, and the fields selected in this view will appear in the Create Idea form when a contributor is creating an…

Hi @Andy Nortrup , I believe engineering changed the location of the repo, which can now be found HERE. Hope that helps!

Hi @Monica Arun Kumar , You can export your data / JPD ideas by following these steps: Export Jira Product Discovery data to CSV, Excel and GSheets Personally I would suggest following the Export data to Excel with the native app steps, and exporting via the Filters tab where you can select the all fields option:

Hi @Monica Arun Kumar , You can export your JPD data / ideas by following these steps: Export Jira Product Discovery data to CSV, Excel and GSheets I personally would suggest following the Export data to Excel with the native app steps where you export the ideas via the Filters tab, and select the all fields option:

Hi @Penny Schenkkan , I unfortunately don't think the use case is currently possible since Formula fields are not support with automations as mentioned in this post: Known limitations of Jira Product Discovery Project Automation is only partially supported You can use Project Automation in Jira Product Discovery projects,…

Hi @Florian , As @Dexter de Vera mentioned, there are some limitations to which field(s) can be published at this time. This is mentioned in our documentation here: Publish views There should also be a warning like in the screenshot below of which field(s) cannot be published:

Hi @p_geremia , We may need additional clarification on the issue you are running into. When filtering on the Status of ideas, you should be able to select which appear in the view like so: There's also the option to Group by Status which may be more helpful. No checkbox needs to be selected and instead, all ideas will…

I would switch the Actor of the automation to yourself (or someone that can create the Epic), then retest. If that is successful, then it's most likely an issue with the A4J (automation for Jira) user, and them not having JPD permission. You'll have to open a ticket with the JPD support team to enable this user /…

Hi @Furkan Akduman , You should be able to find a similar preexisting automation template under each of your JPD projects' Automations tab for this exact use case. You'll just want to select which Jira project the delivery is created under, as well the issue type (such as an Epic):

Hi @Tatiana Torset , The fields that show on the ideas' cards will depend on the fields selected within that view. For example: Having said that - if a field does not have a value entered it may not display on the card until a value is entered (such as the CF1 field in the screenshot above - this shows for one card because…

Hi @Mohamed Kadi , If you reach out to JPD support, they should be able to help with exporting your ideas' insights.

@Yuliia Vyborova - Correct. At this time, in order for any user to be a Contributor (comment, add insights, access ideas), they will need to be added to your Org. When the Stakeholder role is released, users will only need an Atlassian account to comment, add insights, access ideas (when shared) - and will not need to be…

Hi @Yuliia Vyborova , At this time, Contributors can create ideas - as well add comments, insights, etc. That is outlined in our documentation here: Manage your teams product access Also mentioned in that doc. explains who is considered a contributor: Contributors must meet one of the following criteria: * Have product…