I’m a complete novice on many of the machines at Asmbly, and I’ve been opening problem reports when I think there might be a problem, because I don’t have the experience to know that it’s nothing to worry about. But it seems like unless the problem results in a Red Tag, it just goes off into the aether. I know from talking to a steward that my problem reports have been discussed, but I don’t have the learning opportunity to see that discussion or the outcome.
Proposal:
Add a Discourse name field to the Problem Report feedback form, and ping the submitter here with the outcome.
Shane started that on discourse shortly after he took over his duties. Mainly to address the issue that the woodshop cannot be red tagged just due to a single machine. A second reason was to let people know which machines were not working in case they were going to come in just to use those specific machines and waste their time. A by product of that was that people would read the postings and volunteer to help either by contributing parts or materials or actualy fixing the equipment. So often the equipment would not be down more than a day. He is no longer around so all that network is lost. You are right using and reporting the trouble code as I and other people suggest does not provide feedback to anybody outsude the steward’s communication channel which i believe is called slack. I have also at times heard that what i have submitted was discussed but as you, it also left me thinking: discussing and fixing are worlds apart, are they going to fix it quick? Often i took it upon myself and took the time to fix what i could. So until someone takes over and decides to have postings and keep track of them until they are resolved, there may not be many answers or help forthcoming on this topic.