THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
As a rule, we Close tickets instead of Resolving them when they are done.
Background: There are semantic differences for Resolve and Close (implementor vs reporter considers it done), but I don't see how they practically apply to the Flink project. Looking at the numbers, Flink has 11066 closed tickets, and 3372 resolved tickets (that's why I propose to close instead of resolve)
Labels
| Label | Description |
|---|---|
| test-stability | test instabilities |
| starter | tickets suitable for new contributors |
| usability | usability issues |
stale-blocker | A Blocker ticket without an assignee or public discussion. It is about to become "auto-deprioritized-blocker" by the flink-jira-bot. |
stale-critical | A Critical ticket without an assignee or public discussion. It is about to become "auto-deprioritized-critical" by the flink-jira-bot. |
stale-major | A Major ticket without an assignee or public discussion. It is about to become "auto-deprioritized-major" by the flink-jira-bot. |
stale-minor | A Minor ticket without an assignee or public discussion. It is about to become "auto-deprioritized-minor" by the flink-jira-bot. |
auto-deprioritized-blocker | A Blocker ticket that has automatically been moved to Critical by the flink-jira-bot. |
auto-deprioritized-critical | A Critical ticket that has automatically been moved to Major by the flink-jira-bot. |
auto-deprioritized-major | A Major ticket that has automatically been moved to Minor by the flink-jira-bot. |
auto-closed | A Minor ticket that has automatically been closed by the flink-jira-bot. |
stale-assigned | A Major+ ticket that is assigned but has not received an update for some time. It is about to become "auto-unassigned" by the flink-jira-bot. |
| Auto-unassigned | A Major+ ticket that has been automatically unassigned by the flink-jira-bot. |
...