It is a partnership, but it’s important to know that the issue tracker exists for the benefit of the project, which in turn benefits the project’s users. It’s pedantic, but there’s a reason it’s called an issue tracker and not a problem tracker. The dev team can’t action a problem, only the cause of the problem. If the ticket creator can’t identify the cause, nor describe the problem in enough detail so it can be consistently reproduced, there isn’t much a dev can do to proceed. Either the ticket gets a request for additional information or it gets closed as “Works For Me”.
You mention that “Works For Me” rubs you the wrong way, but you neglect to add that each one of those tickets gets a response worded as such:
The issue tracker is not the place for determining the cause of problems. The expectation is that the reporter will avail themselves of other resources to get further assistance. If it later proves that there is indeed a FreePBX bug, the ticket can be reopened with additional details.