Today a bug that I have been watching was resolved as ‘Not a Bug’. In the QA team’s defense, the original bug description was not very clear. I have commented on the bug explaining why it needed to be reopened.
This situation brings up a valid question.
How do we (the Flex community) effectively help the Flex SDK team in a way that doesn’t hinder them? Let’s face it, spamming the inbox of Flex team members isn’t going to get us anywhere.
As I was contemplating this situation, I opened up my Google Reader. It turns out that Joan (a member of the Flex SDK QA team) has a series of posts discussing tips and tricks to using JIRA, along with what we can do to escalate issues that are important.
So for today’s tip, I’m going to provide links to these great posts:
- Flex SDK Fixed Bugs in 3.3
- Flex JIRA Tips (part I): Voting on Bugs
- Flex JIRA Tips (part II) : XML Feeds and Email Subscriptions
- Flex JIRA Tips (part III): How do I reopen a â€˜Closedâ€™ bug?
- Flex JIRA Tips (part IV): Community Fix Candidates
- Flex JIRA Tips (part V) – What does it mean when my bug is â€˜Deferredâ€™?
- Flex JIRA Tips (part VI): Understanding Milestones
- Flex JIRA Tips (part VII): How do I request a Feature in Flex?
I’ll update these links as she posts more.