Triage Team

During this hour we'll review the incoming issue and PR backlog, and triage accordingly.

Where there's time we'll then focus on reviewing older issues and determining if they're still valid, and trying to find folks to work on them.

Attendees

• Mauricio Etcheverry
• Tosin Akinbowa
• Dirk Spannaus
• Ruth Cheesley

Text Blocks:

• "Hi there, please post your issue over at https://forum.mautic.org/c/support as Github is for reporting bugs with Mautic whereas the forums are for getting help if you encounter problems :)"

Product Team:

• only support for v5.x (not 4 anymore)    

Rules:

1. 4.x? Please test it with 5.1 https://gitpod.io/?autostart=true#https://github.com/mautic/mautic/tree/5.1 (documentation: https://contribute.mautic.org/contributing-to-mautic/tester#the-easy-way-using-gitpod)
2. ...

Flow:

1. self assign ownership while triaging, then after that remove yourself
2. check environment https://www.mautic.org/download/requirements
3. could that be related to the user being logged in into Mautic while testing?
4. can it be reproduced with the documentation provided?
5. is there maybe a PR for that already? 
6. label the issue: remove "needs-triage", add tags that are relevant
7. could the reporter maybe fix it herself? suggest to create a PR

Links:

• open "needs-triage" issues: https://github.com/mautic/mautic/issues?q=is%3Aopen+is%3Aissue+sort%3Aupdated-asc+label%3Aneeds-triage
• least recently updated: https://github.com/mautic/mautic/issues?q=is%3Aopen+is%3Aissue+sort%3Aupdated-asc

 Open Questions:

1.  How to handle grapeJS related issues?
2. Tag and discuss in Slack within the #grapeJS-builder channel
3. Other plugin related issues?
4. Will be handled in the upcoming time...
5. Which functions are "supported" - all that have been shipped?