Feed structured Responsly survey responses into Redmine as issues, comments, or custom field updates
Redmine is the open-source project and issue management system used heavily by engineering-led organizations, especially those preferring self-hosted tools over SaaS. Responsly adds the structured-feedback input layer — turning customer and employee voice into tracked Redmine work.
For teams running Redmine, this integration closes the loop between people who report problems and the engineering workflow that fixes them.
Where Redmine and Responsly combine
Bug-report surveys
Customer-facing bug-report forms capture reproduction steps, environment, severity, and expected behavior. Responses create triage-ready issues — better context than email reports or free-text forum posts.
Feature-request intake
Structured feature-request surveys capture the problem, the user type, and the suggested solution. Responses create categorized Redmine issues that product can prioritize by pattern and frequency.
Post-resolution satisfaction
Issue-close webhook triggers a short satisfaction survey to the requester. Data attaches to the resolved issue; patterns inform support quality work.
Release feedback
Survey users after a release for structured feedback. Issues created for regressions, UX problems, and enhancement requests.
Internal support
Employee IT and HR surveys feed Redmine when teams use it for internal ticketing. Structured intake beats email-driven chaos.
Setup
- Build the survey in Responsly.
- Configure Redmine API access and key.
- Automation layer maps response fields to Redmine issue fields.
- Test with sample responses; verify tracker, priority, and custom fields.
- Add issue-close webhook for satisfaction follow-up.
Practices
Map deliberately. Survey fields to Redmine fields; avoid dumping everything into description.
Set defaults thoughtfully. Default tracker, priority, assignee for survey-sourced issues.
Auto-categorize with trackers. Bug vs Feature vs Support = different trackers.
Prevent duplicates. Check for recent issues from the same user before creating.
Close the loop. When issues close, surveys acknowledge the fix — respondents hear that their voice produced change.
Structured feedback into engineering workflow
Connect Responsly to Redmine and customer voice flows directly into the issue system engineering already uses. Bug reports get better; feature requests get prioritized; satisfaction data ties to resolved work. The feedback loop becomes measurable and auditable. For similar issue-tracking integrations, see GitHub and GitLab. For customer service metrics to benchmark issue resolution quality, see our customer service metrics guide.



















