Every week the role and responsibility of the Development Fairy (Dev Fairy) is rotated through all developers.
This is discussed in the weekly Slate Prioritisation meeting held each Thursday.
The support team review support tickets on a daily basis and determine the priority level and whether the ticket warrants further investigation by a developer following the below steps:
1. Identify the weekly developer who is working as Dev Fairy that week
2. Review the nominated support ticket , determine the priority relative to marketplace and issue:
| Marketplace | Standard SLA | Emergency SLA | Exception |
| eBay | |||
| eBaylink | |||
| TradeMe | |||
| TradeRunner | |||
| Catch | |||
| CatchFeeder | |||
| Amazon | |||
| Westfield |
| Agreement | Freshdesk | Example | Response time to acknowledge Issue | Resolution | Updates |
| P1 | Urgent | Whitelabel not accessable for merchants | 1 hour | 4 hours | 1 hour |
| P2 | High | Multiple retailers impacted Orders not being updated for multiple merchants Products listing but shouldn't be for multiple retailers |
4 hours | 12 hours | 3 hours |
| P3 | Medium | Single retailer impacted A merchant is unable to map products Retailer can't list products |
1 business day | 3 business days | 24 hours |
| P4 | Low | Merchant requires assistance to set up a promotion | 2 business days | 5 business days | 3 business days |
3. Discuss the tickets in Scrum as part of normal daily process
4. Set the status on ticket to 'Waiting on Dev Fairy' - this will add to the Dev Fairy queue
5. Dev fairy assigns the ticket they are actively working on to themselves
6. When finished, either set status to "Open" and assign back to the support team/originator, or "Closed" if closed
7. Handover all outstanding Dev Fairy tickets to incoming developer at the end of the week
8. Long term Dev Fairy tickets need to have the feature captured as a Trello card, save link to Trello card in the ticket and then can advise customer/close ticket