Solution For This Issue is Backward Compatible.

This case is a thing that is not behaving as expected.

Marks as incoming doomsday if left unattended. Can cause earthquake, tsunami, meteor shower, and/or Ragnarök!

This issue is blocked mainly due to a dependency from 3rd party or from client. There is no workaround and we can't proceed further until the dependency is resolved or available. You must inform the client about this as it will introduces late in schedule.

This is just at discussion phase. Please do not do anything else aside discussing what to do.

This is related to documenting articles and facts in an official/internal document.

There is someone handling and proceeding with this case.

The case is completed and is parked under staging (e.g. next/staging branch or goods are in the werehouse). It is pending for release to customer (e.g. master branch / package picked up by logistics).

This case is about improving on an existing item/feature/task.

This case is now in Grand Testing phase. Be prepared to destroy.... I mean test the subject with absolute power!

This issue is completely related to infrastructure for developing the project.

The Solution for This Issue Is Not Backward Compatible

The case is about adding a new feature.

This case is about asking a question.

This case is scheduled to start with the given due date, rather than delivering on it.

Potential Security Vulnerability That Compromises Customers

The case is actually a suggestion, not a big issue.

It is decided that the case will not be implemented/fix.

This issue has another, temporary way to make it works.

There is no other way. You have to resolve this issue!