Guidelines
Common Tickets
Common tickets communication
The ways of working and collaborating between the UK and EU app teams are agreed by both parties and documented on this page
- Future tickets - decide if a ticket will be for UK and EU or only 1 region
- Each team creates separate tickets and they need to be linked
- To add label: UK/EU and appropriate labels for the team
- The tickets should use same epic, if possible:
- e.g. UK & EU | General enhancements
- Share the ticket in the comms Space for joint tickets between UK and EU
- To get confirmation from the other region if they also plan on implementing the ticket or not
- If yes, share info on implementation
- If no, flag the ticket that it is only for 1 region and add feature flag on the code
- To share the tickets that could be potentially for both apps after Sprint planning in chat
- To discuss the decision of the tickets on the weekly chat between UK PO and EU PO
- For any bugs affecting both apps - 1 ticket to be created
- If there is any exception - the teams will agree on separate tickets
- Use the ticket’s comment section to tag EU team’s: QA and Scrum master / Delivery lead or UK team’s: QA and Scrum master / Delivery lead - so both teams know what needs to be done or tested
- Any tickets that need testing from both teams
- Use the ticket’s comment section to tag EU team’s: QA and Scrum master / Delivery lead or UK team’s: QA and Scrum master / Delivery lead - so both teams know what needs to be done or tested
- Get confirmation from the other team once the ticket is tested - add the results in comment