Release phases
Scope Freeze: August 12, 2019
Code Freeze: August 15, 2019
Voting Date: August 22, 2019
Release Date: August 27, 2019
Required tickets
The most important tasks, features, optimizations, and fixes that have to get into the release.
Such tickets have to be labeled "important" in JIRA.
| key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Unresolved tickets (excluding documentation tickets)
| key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Tickets, which require release notes
Tickets with flag Release Notes Required, but Release Note is not filled:
| key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Release Notes
List of tickets with Release Notes:
| key |
summary |
type |
assignee |
status |
resolution |
release note |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Unresolved tickets
| key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Resolved tickets
| key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
