gitlab-trello-meeting-1.md

Decisions from 1st DevLeads Meeting regarding migration.

• All cards on Trello on Backlog or ToDo will be turned into Issues on GitLab. Checklists on Trello will be synced as checklists in Issue on GitLab.
• Assignment on a card or issue gets synced.
• Estimation will be handled in the name of an issue on GitLab. Synced from and to Trello.
• Automatic generation of Milestone triggered by assigning a label to the latest Agenda card.
• Doing is a label on GitLab that triggers a move to that list on Trello. The automatic assignment of this Label has to be discussed further.
• Client and design requirements blocking cards will be informed by Labels on GitLab and will generate changes to be defined on Trello.
• When an issue is ready to tested, it is closed on GitLab (moved to To Be Tested on Trello) and a related QA issue is created on GitLab.
• If an issue is encountered during QA, the QA member will re-open the issue associated to his QA, comment on whatever caused him to reject it and then close his own QA issue.
• If a QA issue is closed and its associated issue is closed, the issue is considered Approved (moved on Trello) and deployed.
• If a QA issue is closed and its associated issue is open, the issue is considered Rejected (moved to Backlog on Trello).
• How the client will be able to affect this QA process from Trello has yet to be defined.
• Effort -> Automatic syntax “#effort 3” in commit message and/or using comments in an issue. Triggers an update to Trello with the effort.
• QA or team member finds an issue, creates it in GitLab, the card is created on Trello.
• Client or team member adds a card on Trello in the Backlog or ToDo, the issue is created on GitLab.