Can you create power automate flow from MS forms to create Jira Discovery Idea?

[Joric Gonzales]

I know it is possible to create a Jira software issue from an MS forms response using power automate. I wonder if it would be possible to do the same, but this time, instead of creating an issue for JIRA software, it will be posted as an Idea in JIRA Dscovery. 

[Nick Haller · Accepted solution]

Hi @Joric Gonzales ,

At this time, JPD does not have an integration with MS Teams, so I don't believe MS forms would be possible directly with JPD.

As a workaround, you could continue leveraging Jira in the meantime as an intake, and use an automation to clone the issue as an idea in the JPD project.

Might look something like this:

1) WHEN: Issue created

2) IF: Issue Type = Feature Request (option component)

3) THEN: Clone issue into

• Select JPD project
• Select Issue type = Idea
• Select which fields to set (copy from Current issue or set your own values)

4) AND THEN: Link issue to (option component)

• is cloned by Most recently created issue
  • ^ can select different link-type as well

Note as well, the Scope of this automation is set to both my Jira and JPD projects. Hope that helps!

[Olha Yevdokymova_SaaSJet]

Hello @Joric Gonzales 

Yes, it’s possible to achieve something similar in Jira Product Discovery (JPD) using Smart Forms for Jira While add-ons like Smart Forms aren’t directly available within JPD project views, you can set up form submissions to create new ideas in JPD with mapped fields and track the responses effectively.

Here’s how it works with Smart Forms for Jira:

1. Create New Ideas with Field Mapping: With Smart Forms for Jira, you can configure a form to create a new Idea in JPD upon submission. Simply map the form fields to JPD’s Idea fields (like Title, Description, etc.), so that when the form is submitted, an idea is created with content directly pulled from the form responses.

2. Pre-Fill Form with Idea Fields: Smart Forms also offers pre-fill options, so any existing data in JPD Idea fields can automatically populate into the form, making it easy to update or expand ideas based on form responses.

3. Responses Tracking: Each form submission will be stored in the Responses tab within the Smart Forms for Jira add-on, allowing you to review, organize, and analyze form data independently. This makes it easy to view submission history and track input beyond the basic idea creation.

Using this setup, the idea is created with mapped form fields, allowing you to see form responses directly as part of your JPD idea content.

[Joric Gonzales]

Thanks for this!

However, we'd like to limit licenses as users that will be filling out the forms are not necessarily members of the organizations, or would not need access to the Discovery boards. So I'm looking for a way to make the form in MS Forms or similar.

We already have a Power automate flow from using MS forms to create JIRA Software ticket. What I wanted to know specifically is if the same can be done for JIRA Product Discovery? Is it just a matter of providing the correct API key in Power automate?

[Olha Yevdokymova_SaaSJet]

With Smart Forms for Jira, you can enable everyone—even external users without access to your org—to submit forms and create Jira Product Discovery (JPD) ideas.

However, if you’re using Power Automate, it might need a different setup I am not sure about it. There are great copilot in Power Automate maybe it will be able to set this up 😅
Alternatively you can move existing issues from Jira to JPD, you can do so with the bulk move option in Jira.

Bulk Moving Issues from Jira to JPD

To bulk move issues into JPD, ensure that your JPD project is set up first. Then follow these steps:

1. Go to Filters > View all issues.
2. Search for the relevant issues.
3. Select the breadcrumbs button (...) in the top-right.
4. Choose Bulk change all N issue(s).
5. In Step 1, select the issues to move (you can select “all” using the checkbox in the title row).
6. In Step 2, choose Move issues.
7. In Step 3, select your JPD project and the relevant issue type (e.g., Idea).
8. On the next screen, map existing statuses to new statuses.
9. Populate or map required fields in the fields screen.
10. In Step 4, check the mapping, then press Confirm to complete the move.

Additional Notes

1. During Step 9, some fields might be marked as mandatory, but you may be able to skip them by pressing “next.”
2. Since JPD projects are team-managed and don’t use global fields, certain fields (like Story Points, Components, etc.) may become NULL after the move. You might have the option to map these fields, depending on the field type.

Optional: Export and Import for Unmapped Fields

To preserve data in fields that may not map over, you could:

1. Export all issue field data prior to the move.
2. Move the issues to the new JPD project.
3. Re-export the data.
4. Map the field data to the new issue keys based on Issue ID.
5. Re-import the field data into the new fields post-move.

Note: While issue keys will change during the move, the issue ID remains static and can be used to link data across projects. For more details on CSV imports, refer to this help page on CSV imports.

This approach ensures that your ideas in JPD retain the relevant data from your original issue.