FYI: Here's a workflow diagram showing the life cycle of Jira issues:
http://www.atlassian.com/software/jira/docs/latest/default_workflow.html The life cycle of most stdcxx issues goes something like this: (Create) | V +-----+ |Open | +-----+ | ^ | | | (Stop Progress when not actively working on the issue.) | | (Start Progress when you start actively working on the issue.) | | V | +-----------+ |In Progress| +-----------+ | | | | | (Resolve after committing a patch and successfully testing | it on a subset of platforms.) | | | V | +--------+ | |Resolved| | +--------+ | | | | (Close after a test for the bug has been committed and confirmed to pass on available platforms.) | | V V +------+ |Closed| +------+ Note that most issues shouldn't be Resolved as Fixed until a patch for them has been committed and verified. They can be closed after a test for the bug has been added to test suite (if it doesn't exist at the time the issue is created) and after nightly builds have confirmed that the test passes. Martin
