Labels
Labels
35 labels
- Things to do with metasmoke's V2 API - probably for Art.
- Issues which require someone (usually @Undo1) with higher access to fix records
- AKA the data exploders (any of them - JS or SQL)
- Pull requests that update a dependency file
- Issues relating to auto, manual and mod flagging
- Servers, software, versions, deployments, all of the Stuff that is teward's purview as sysadmin.
- Probably one for thesecretmaster. Things to do with how MS uses redis.
- metasmoke's review system and associated things
- This involves coordination with changes in SD.
- Post search on metasmoke
- Anything to do with the user interface, particularly UX concerns
- HF issues label. Outside of HF, also consider using type: up-for-grabs.
- HF invalid label to make issues not count towards the 5.
- Pull requests that update Ruby code
- Discussions that have been discussed and resolved.
- Bugs that aren't bugs, or FRs that come from a misunderstanding (might be cause for a UI issue)
- Resolved/fixed.
- Bugs/FRs that will not be fixed/implemented for various reasons.
- We'll do it later. Maybe. 6-8 months.
- This needs more investigation.
- Issues that can't be reproduced in testing.
- We like the idea and might get around to it at some point.
- Issues which require revisiting because they may have become obsolete or changed in some way
- Buggy or otherwise incorrect behaviour.
- Something that requires discussion among the team.
- This has been done before.
- Requests for a new feature.
- Issues that need feedback on them before anything further can be done.