Nick Haller Atlassian Team

Hi @Kenneth_Johansen , Unfortunately this is a known limitation as mentioned in the Cloud-to-cloud migration section of that linked Community Article - so it's not possible to import views, configuration and insights at this time I did put together this Import Ideas Article that may help with importing ideas to the new…

Thank you again @Jade Ye for opening a ticket with JPD support. For the Community - Jade was able to identify a minor bug which relates to JPD specifically, and the issue mentioned above. In order to delete a label from your site, you can follow this documentation. But in some cases, the label will still appear as an…

@Ashleigh Hamilton , Could be an issue with the Actor (Automation for Jira), and this user not having JPD permissions. This has been an issue for some customers in the past, and a known minor bug engineering is aware of. Try switching the Actor to someone who has JPD permissions, and retesting to see if there are any…

Hi @Tim Sanford , I don't think it's possible at this time to select the delivery's default issue type, but we'll get some sort of feature request entered with engineering for this functionality. 

Hi @Ashleigh Hamilton , As @Mike Maurer mentioned, might be worth setting the issue type to Idea - even if this automation is cloning an idea from one JPD project to another JPD project: If there error persists after that adjustment, let us know.

Hi @Jade Ye , If possible, it might be worth connecting with JPD support to investigate further. You can open a ticket HERE, or within JPD under the Give feedback tab >> Get help from the support team option.

Hi @Jade Ye , I have to assume that label is still configured / entered as a value under a JPD idea(s) and/or Jira issue(s). I would do a more general JQL on the field+value to see which ideas / issues have the label. Maybe something like this: cf[12345] = "label_value" ^ Replace your label-field with your field's ID, and…

Hi @Lucia Bayly , A few features like this are on the JPD public roadman - such as the Idea hierarchies or even the Roadmaps / cross-project views - but no real ETA on when these will be released. In the meantime, you may want to leverage Jira for this, or even just link JPD ideas together.

Hi @RS , We've seen some customers run into this issue where the Slack app is not installed correctly for JPD. You will want to open a ticket with JPD support so they can resinstall the app. This only takes a few moments, but can only be corrected with their assistance. You can open a ticket HERE, or within JPD under…

@Jonathan Bron , That all makes sense. We do not want to overcomplicate your entire workflow. If you need assistance with setting up a JSM portal, feel free to open a ticket with support HERE, or through Give feedback tab >> Get help from the support team option.

Hi @Jonathan Bron , If option 3 was not ideal, then option 2 would most likely be the best moving forward. Actual JPD stakeholders (JPD role) cannot create ideas. They can simply access and review Published views. Only creators and contributors can create ideas at this time. I also see option 1 as being somewhat…

I'm not sure if this will be a creator permission in the future, but feel free to share this feedback with our engineering and product teams with JPD under the Give feedback tab. At this time a user will have to be a project admin to add watchers to an idea.

Hi @Yuliia Vyborova , Adding a watcher is a JPD project admin permission. JPD does not have permission schemes since the product only offers team-managed projects.

Hi @Aymeric Douyere , You can share your feedback with our product and engineering teams direction through JPD's Give feedback tab >> Submit feedback to the product team option.

Hi @Emily Nash , No stupid questions here! You would need to use an automation to map and/or copy fields between JPD ideas and Jira deliveries. It might make sense to use a global field for the use case since it can apply to both projects. Take a look at this article on how to map idea's fields to delivery's fields during…

Hi @Matteo Pacenti , You should be able to add rules within forumla fields like number fields, which apply formatting: Let us know if you are looking for / seeing something else.

Hi Everyone! Take a look at this Article @Tanguy Crusson just published: A (giant) update for hierarchies, issue types, opportunity/solution trees Hope this helps with what you are looking for! Stay tuned for more updates to come.

Hi Everyone! Take a look at this Article @Tanguy Crusson just published: A (giant) update for hierarchies, issue types, opportunity/solution trees Hope this helps with what you are looking for! Stay tuned for more updates to come.

Hi Everyone! Take a look at this Article @Tanguy Crusson just published: A (giant) update for hierarchies, issue types, opportunity/solution trees Hope this helps with what you are looking for! Stay tuned for more updates to come.

Hi Everyone! Take a look at this Article @Tanguy Crusson just published: A (giant) update for hierarchies, issue types, opportunity/solution trees Hope this helps with what you are looking for! Stay tuned for more updates to come.

Hi @Sue Hannan , Sorry for the delay, this got lost in my notifications / inbox. I'll address bullet 8 since the others have been touched upon. If you wanted to copy the Jira delivery's (initiative's) work-type field to the JPD idea's work-type field - when the Jira delivery's (initiative's) work-type field is updated, you…

Hi @Hariharan Y , Thank you for sharing that additional feedback, and apologies for any inconvenience / lack of functionality. We do have a feature request already entered with engineering to improve the in-app search, and hopefully have it identify fields outside only the Summary and Description. No ETA on when this will…

Hi @Tim Whittington , We've seen in the past some customers running into this issue when trying to integrate their Slack with JPD. It's a minor bug where the add-on / plugin is not granted JPD product access. You'll want to open a ticket with JPD support HERE, or through JPD's Give feedback tab >> Get help from the support…

Hi @Sue Hannan , Right now the closest thing would be through manually linking them. There is currently not any cross-project functionality as mentioned in our limitations page But on the JPD public roadmap is a feature to create cross-project views. I believe this is what you want. We're hoping this feature will be…

Hi @Hariharan Y , It should be possible to search / filter on a short text field. For example: You should also be able to use the field's ID to query on it too if that is any help:

Hi @James Frith , I don't think it's possible at this time. Vote fields are not currently supported with automations as mentioned in our Limitations page. Part (if not most) of the reason they are not supported (along with those other fields mentioned) with automations is due to them not parsing in the backend currently…

I have to assume since JPD people fields are only multi-user at this time, that's why JPD global fields only offer this option as well. But as you mentioned, hopefully this is something considered in the future.

Hi @Prashant Topiwala , After testing, I don't think single user picker fields are supported with JPD global fields at this time. I've entered a feature request with engineering to support this field type. No ETA on when that might be added, so the workaround for the time being would be to use a global multiple user picker…

Hi @Jayesh Malondkar , There should be plenty of examples throughout the JPD Community such as this one: How Hemnet - Sweden's leading property platform - moved from Miro to JPD

Hi @Sue Hannan , If you can describe the use case step-by-step, it will be helpful. I'm still unsure whether; * the Jira issue is created outside of the JPD idea, then it's linked as a delivery, and fields should be mapped during the linking * the JPD idea is creating the Jira delivery, then updates on the delivery fields…