Step 1: Export Form Responses from Smart Forms for Jira
...
Go to your Smart Forms for Jira Forms add-on in Jira.
Access the responses tab for the form you want to export.
In the More Options (•••) menu, select Export.
Choose Exel as your export format.
Follow the prompts to download the file to your device.
Convert XLS file to CSV for futher import to Confluence.
...
| Note |
|---|
The "Date and Time" field in Smart Forms for Jira Forms cannot be directly converted into a "Date" field type in Confluence Databases because it contains both date and time information. |
...
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
...
needs to track and prioritize feature requests and customer feedback
...
.
Use Case: The team creates a
...
Confluence Database to consolidate customer feedback
...
and feature requests,
...
categorizing each entry by priority, status (e.g., backlog, in development
...
), and customer impact. By connecting
...
the database to other sources (like customer interactions or product versions),
...
they can track which feedback is
...
linked to specific product improvements,
...
enabling better prioritization and roadmapping.
How It Works:
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)
team uses Smart Forms for Jira to gather feature requests and feedback, including fields like customer name, feature description, priority, and impact. The form is shared across teams to capture consistent data.
Exporting and Storing Data in a Confluence Database:
After feedback is submitted through the forms, the team exports the form responses as aAfter exporting the responses as an XLS file and
then convertconverting it to CSV
.The data is then uploaded, the team uploads the data 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
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.
Connecting Databases for a Holistic View:
The feature request database may be connectedwith fields like feature title, priority, status, and customer impact.
Prioritization and Visualization: Using Confluence's sorting and filtering options, the team prioritizes entries based on urgency and impact. Customizable views, such as table or board layouts, help them track feature requests through different development stages.
Connecting Databases: The feature request database is linked to other Confluence Databases, such as
a Customer Interactions database and a Product Versions database. By linking feedback to specific customerscustomer interactions 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.
enabling a holistic view of how feedback influences product releases.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.
...