Export Form Responses to Confluence Databases

Step 1: Export Form Responses from Smart Jira Forms

1. Go to your Smart Jira Forms add-on in Jira.

2. Access the responses tab for the form you want to export.

3. In the More Options (•••) menu, select Export.

4. Choose Exel as your export format.

   

5. Follow the prompts to download the file to your device.

6. Convert XLS file to CSV for futher import to Confluence.

Step 2: Upload Data to Confluence Database

1. Create your Confluence Database where you want to store the exported form responses.

   

2. Click the More Options (•••) menu in the top-right corner of the database.

   

3. Select Import and upload your CSV file.

   

4. Map the fields (e.g., customer name, feature request, priority level) to your database fields.

   

5. If your form has Jira issue fields you can connect it to your Database fields.

   

Why Export Form Responses to Confluence Databases?

• Centralized Data Repository: Consolidating form responses within a Confluence database creates a single source of all data you needed.

• Enhanced Data Analysis: Confluence databases often provide advanced querying and reporting capabilities, enabling you to slice and dice your form data to uncover valuable trends and patterns.

• Improved Collaboration: Storing form responses in a Confluence database fosters collaboration by making the data readily available.

• Long-Term Data Retention: Confluence databases offer secure and reliable long-term storage for your form responses.

Use Cases:

Product Ideas and Feature Requests

• Scenario: A product development team collects feature requests and customer feedback that must be tracked and prioritized.

• Use Case: The team creates a database that consolidates customer feedback, feature requests, and ideas into a single location. Each entry can be categorized by priority, status (e.g., in development, backlog), and impact. By connecting these entries with other databases (such as customer interactions or product versions), the team can track which feedback is tied to specific product improvements, allowing for better prioritization and roadmapping.

How It Works:

1. Collecting Feedback Using Smart Jira Forms:

   • The product development team creates a form using Smart Jira Forms, designed to collect customer feedback and feature requests. The form might include fields like:

     • Customer Name

     • Feature Request Description

     • Priority Level (Low, Medium, High)

     • Impact on Product (Minor, Major, Critical)

     • Feedback Source (e.g., customer support, survey, user group)

   • The form is shared with customers, support teams, and internal stakeholders, ensuring that all feedback is captured in a consistent and structured manner.

2. Exporting and Storing Data in a Confluence Database:

   • After feedback is submitted through the forms, the team exports the form responses as a XLS file and then convert it to CSV.

   • The data is then uploaded into a Confluence Database, where each feature request and customer feedback entry is displayed in a structured format.

   • The database is designed with fields such as:

     • Feature Request Title

     • Priority

     • Status (e.g., Backlog, In Development, Released)

     • Customer Impact

     • Date Submitted

     • Assigned Team or Developer

3. Categorizing and Prioritizing Entries:

   • The team uses Confluence Database’s built-in filtering and sorting options to categorize feature requests by priority, status, and customer impact. This allows the product team to see which requests are most urgent or which have the greatest impact on customer satisfaction.

   • Using customizable views (e.g., table view for a list of feature requests or board view for prioritization tracking), the team can visualize the backlog of feature requests, organize them based on the stage in the development process, and track their progress.

4. Connecting Databases for a Holistic View:

   • The feature request database may be connected to other Confluence Databases, such as a Customer Interactions database and a Product Versions database. By linking feedback to specific customers or product versions, the team can trace which customer requests influenced which product releases, and ensure they are aligned with customer needs.

   • For example, the product team can link a feature request to customer feedback, providing context for why a particular feature is important. They can also connect the feature request to the relevant Jira issues that track development progress.

Other examples:

Customer Feedback Form

• Example: "Product Feedback Form" or "Customer Satisfaction Survey"

• Purpose: Collects feedback from users about your product or service. Useful for storing responses in Confluence and analyzing trends over time. Fields might include ratings, text feedback, and suggestions.

Event Registration Form

• Example: "Conference Signup Form" or "Webinar Registration Form"

• Purpose: Gathers participant details for events. Once exported, the data can be uploaded into a Confluence Database to track attendees, preferences, and other logistical information.

Bug Reporting Form

• Example: "Software Bug Report Form" or "Technical Issue Form"

• Purpose: Allows users to submit bug reports with details like steps to reproduce, priority, and affected areas. After collecting this information, it can be stored in Confluence for product management and development tracking.

Employee Onboarding Form

• Example: "New Hire Information Form" or "Equipment Request Form"

• Purpose: Collects information about new employees, including role details, equipment needs, and access requirements. This data can then be stored in Confluence as part of your HR or IT documentation.