How many times have you been testing something for work or some extracurricular activity and found something you though to be really super duper extra important only to have no one care? I’ve done it a few times, most folks I know have. This is a difficult situation to be in. rejection is tough. No one likes to spend time reproducing, isolating and whatnot just to find out that no one cares about your issue. That was a RIMGEA reference for my bug advocacy friends out there.
In my opinion, this is one of things at the heart of the context-driven community. Finding relevant information in a timely manner and presenting it to people who care. Here is a great anecdote from Perze.
bug rejections sometimes happen because there is no clear line between the test objective/mission and your test cases.
— Perze Ababa (@perze) October 14, 2013
Direct communication with the people who rely on your information certainly goes a long way to make your work worth while. Things like clarifying your information objectives, your mission, your test charters have been really helpful to me. Have you ever been in this kind of situation? How did you resolve the conflict, how did you reduce the chances it would happen again?