Organize permanent feedback loops #500

Open
opened 2026-06-01 15:55:22 +02:00 by simon · 0 comments
Owner

Description

We want to collect feedback from our first users, aside of a dedicated survey and our support/info mail:
Ideas:

  • Issue tracker from openCode?
  • Different Feedback tool?
  • input directly from Mila instances?

Acceptance criteria

  • AC 1
  • AC 2

External or internal Dependencies

## Description We want to collect feedback from our first users, aside of a dedicated survey and our support/info mail: Ideas: - Issue tracker from openCode? - Different Feedback tool? - input directly from Mila instances? <!--- Describe the goal and desired output ---> <!--- Add the estimated effort as label ---> ## Acceptance criteria - [ ] AC 1 - [ ] AC 2 ## External or internal Dependencies <!-- List any dependencies --->
simon added this to the Code and Test Refactoring | TI I milestone 2026-06-01 15:55:22 +02:00
simon added the
M
label 2026-06-01 15:55:22 +02:00
simon added this to the Sprint 17: Juni 2026 project 2026-06-01 15:55:41 +02:00
simon modified the milestone from Code and Test Refactoring | TI I to Optimize CI and Dev Environment | TI I 2026-06-01 16:06:00 +02:00
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: local-it/mitgliederverwaltung#500
No description provided.