Form2Task: Transform External Input into Actionable Tasks
Form2Task bridges the gap between external stakeholders and your project workflow. Create customizable web forms that automatically convert submissions into tasks—collect bug reports from customers, feature requests from users, support tickets from clients, or feedback from beta testers without giving them direct project access.
Why Form2Task Exists
Every project eventually needs external input. Customer feedback, bug reports, feature requests, support tickets—all valuable information that typically lives in emails, spreadsheets, or separate ticketing systems disconnected from your actual workflow.
Form2Task solves this by creating a direct pipeline from external submissions to your task board. When someone submits a form, it becomes a task automatically. No manual copy-paste, no context switching, no information lost in translation.
Use cases that make Form2Task essential:
- Bug Reporting: Give users a structured way to report issues with specific fields for reproduction steps, expected behavior, and environment details
- Feature Requests: Collect product ideas with priority fields and use case descriptions
- Support Tickets: Create customer support workflows that feed directly into your sprint backlog
- Beta Feedback: Gather structured feedback during testing phases with categorization
- Client Requests: Allow clients to submit change requests without project access
The Form2Task Interface
Access Form2Task from your project sidebar. The main view displays all submitted forms converted into tasks, organized in a clean table format.
Submission Table
The central table shows every form submission with essential details:
| Column | Purpose |
|---|---|
| Task Title | The title generated from submission (based on your mapping) |
| Description | Content from the form's description field |
| Status | Current workflow status assigned to the task |
| Created At | Timestamp showing when submission arrived |
| Meta | Additional form field data captured in submission |
Each submission represents a task in your system. The table paginates automatically—navigate between pages using Previous and Next controls at the bottom.
Header Actions
Two primary actions control Form2Task functionality:
Settings: Configure form appearance, field mappings, and templates. This defines what information you collect and how it maps to task properties.
Add Form2Task: Manually create a form submission when you need to add external input yourself (useful for phone calls or offline feedback).
Configuring Form Settings
The Settings modal controls everything about your form's behavior and appearance.
Form Display Settings
Customize how the public form appears to submitters:
Form Main Title: The heading visitors see when accessing your form. Default: "Create a new task"—but customize it to match your use case:
- "Report a Bug"
- "Submit Feature Request"
- "Request Support"
- "Share Your Feedback"
Task Title Content: Placeholder text for the title field. Guide submitters on what to enter:
- "Describe the issue briefly"
- "Name your feature idea"
- "Summarize your request"
Task Description Content: Placeholder for the description field. Set expectations:
- "Provide detailed steps to reproduce"
- "Explain how this feature would help"
- "Give us full context"
Template System
Templates define the custom fields on your form beyond title and description. This is where Form2Task becomes powerful—you can collect structured data specific to your use case.
Selecting a Template: The dropdown shows all available templates for your organization. Each template displays its name and field count (e.g., "Bug Report Template (5 items)").
Applying a Template: Click "Apply Template" to add that template's fields to your project's form. The fields appear immediately in the template items table below.
Field Types Available
Templates support various field types to capture different data:
| Field Type | Use Case |
|---|---|
| Small text | Short answers—version numbers, browser type, feature name |
| Long text | Detailed input—reproduction steps, use case description |
| Checkbox | Boolean options—"Is this blocking?", "Tried clearing cache?" |
| Selectable options | Dropdowns—severity level, category, priority |
| Date | Timeline info—"When did this first occur?" |
| Date and time | Precise timestamps—incident time, deadline requested |
Managing Template Items
Once a template is applied, view and manage individual fields in the template items table:
- Name: The field label visitors see
- Type: The input type (text, textarea, checkbox, etc.)
- Each field can be modified or removed as needed
Creating Manual Submissions
Sometimes you need to add submissions yourself—phone feedback, meeting notes, or in-person requests. The "Add Form2Task" modal handles this.
Add Form2Task Modal
Title: Enter the submission title. This becomes the task title.
Description: Provide detailed information. This maps to task description.
Click "Create" to generate the task. It appears in your submission table immediately and follows your normal task workflow.
Form Distribution
Once configured, your form needs to reach submitters. Form2Task provides two distribution methods:
Public Link
Share a unique URL that opens your form in a standalone page. Perfect for:
- Email signatures
- Support documentation
- Customer portals
- Beta tester communications
The link works without authentication—anyone with the URL can submit.
Embed Code
Get HTML code to embed the form directly in your website. Ideal for:
- Contact pages
- Support sections
- Documentation sites
- Product landing pages
The embedded form maintains full functionality while matching your site's context.
Workflow Integration
Form submissions don't just create tasks—they integrate fully into your workflow.
Automatic Status Assignment
Submissions receive an initial status based on your configuration. Typically this is your "backlog" or "new" status, but configure it to match your triage process.
Meta Data Preservation
All custom field data travels with the task. When you open a converted task, you see the complete submission including:
- Every custom field and its value
- Original submission timestamp
- Form version used
Task Properties
Converted tasks behave like any other task. You can:
- Assign team members
- Set due dates
- Add to sprints
- Apply labels
- Track time
- Link to user stories
The submission origin is preserved, so you always know a task came from external input.
Practical Implementation Examples
Bug Report Form
Template Fields:
- Severity (Selectable options): Critical, Major, Minor, Cosmetic
- Browser (Small text): Chrome 120, Firefox 115, etc.
- Operating System (Small text): Windows 11, macOS 14, etc.
- Steps to Reproduce (Long text): Detailed reproduction instructions
- Expected Result (Long text): What should happen
- Actual Result (Long text): What actually happens
- First Occurrence (Date): When the bug first appeared
Form Title: "Report a Bug" Title Placeholder: "Brief description of the issue" Description Placeholder: "Any additional context"
Feature Request Form
Template Fields:
- Category (Selectable options): UI/UX, Performance, Integration, New Feature
- Business Impact (Long text): How this would help
- Priority (Selectable options): Critical, High, Medium, Nice-to-have
- Deadline (Date): When you need it by
- Willing to Beta Test (Checkbox): Yes/No
Form Title: "Submit Feature Request" Title Placeholder: "Name your feature idea" Description Placeholder: "Describe what you want and why"
Support Ticket Form
Template Fields:
- Issue Type (Selectable options): Account, Billing, Technical, Question
- Account Email (Small text): For lookup
- Urgency (Selectable options): Blocking, High, Normal, Low
- Tried Solutions (Long text): What you've already attempted
- Best Contact Time (Small text): For follow-up
Form Title: "Request Support" Title Placeholder: "Summarize your issue" Description Placeholder: "Full details about what you need help with"
Best Practices
Form Design
Keep it focused: Collect what you need, nothing extra. Every field is friction.
Use appropriate field types: Don't use long text for simple choices. Dropdowns speed up submission and ensure consistent data.
Clear placeholders: Guide submitters with examples, not instructions. "Chrome 120" works better than "Enter your browser name and version".
Logical field order: Start with the most important fields. If someone abandons mid-form, you want the critical data first.
Workflow Management
Regular triage: Form submissions can accumulate. Set a cadence for reviewing and prioritizing new submissions.
Status clarity: Create a clear status progression for external submissions. "New → Triaged → Planned → In Progress" tells submitters their request is being handled.
Response expectations: If you share the form publicly, be prepared to respond. Silent forms damage trust.
Template Maintenance
Version templates thoughtfully: When you change a template, existing submissions keep their original data. New submissions use the new template.
Test before deploying: Submit a test entry through your own form. Verify the task created matches your expectations.
Document template purpose: Name templates clearly. "Bug Report - Product v2" beats "Template 3".
Pagination and Navigation
Large volumes of submissions paginate automatically. The bottom bar shows current position ("Page 2 of 15") with Previous and Next controls.
For faster navigation with many submissions:
- Use filters if available
- Export to spreadsheet for bulk analysis
- Archive processed submissions to reduce clutter
Security Considerations
Public forms accept submissions from anyone with the link. Consider:
Rate limiting: The system prevents spam through built-in rate limiting, but monitor for abuse.
Spam handling: Automated submissions happen. Triage accordingly.
Sensitive data: Don't collect information through public forms that requires protection. No passwords, no payment details.
Link rotation: If a form link is compromised, generate a new one.
Integration with Other Features
Form2Task works with GitScrum's broader feature set:
Kanban: Converted tasks appear on your board in the configured status column.
Sprints: Add form submissions to sprints during planning. External requests become part of your velocity.
Time Tracking: Log time against form-submitted tasks like any other.
Reports: Include form submissions in productivity reports. Track how much effort goes to external requests.
Discussions: Use the task's discussion thread to communicate internally about submissions.
Keyboard Shortcuts
Navigate Form2Task efficiently:
| Shortcut | Action |
|---|---|
S | Open Settings modal |
N | Open Add Form2Task modal |
← / → | Previous / Next page |
Esc | Close open modal |
Troubleshooting
Submissions not appearing: Check that the form is active and properly configured. Test with a manual submission.
Missing custom fields: Verify the template is applied to your project. Template changes don't retroactively update.
Task status wrong: Review your default status configuration in settings.
Form link broken: Ensure the project and form are both active. Regenerate link if needed.
Form2Task transforms external feedback into actionable work without exposing your project internals. Configure once, share widely, and watch valuable input flow directly into your workflow where you can actually act on it.