...
| Info |
|---|
Add your comments directly to the page. Include links to any relevant research, data, or feedback. |
| Page Properties |
|---|
|
| title | HIGH |
|---|
/ / | Status |
|---|
colour | | Status | | Status |
|---|
| colour | Yellow |
|---|
| title | In progress |
|---|
|
|
|---|
| Impact | |
|---|
Red | | | Driver | |
|---|
| Approver |
|
|---|
| Contributors | |
|---|
| Informed |
|
|---|
| Due date | |
|---|
| Outcome | |
|---|
|
Background
The MODULE-DATA epic is outdated and should not be done arbitrarily.
...
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | "Epic Link" = "MODULE-DATA" AND Status != Closed |
|---|
| serverId | 45e63be1-2551-37a6-b050-86a38172f71d |
|---|
|
Options considered
| Option 1: | Option 2: |
|---|
| Description | Remove all open items besides SIMP-3218 | Retain all open items and triage individually |
|---|
| Pros and cons |  Allows natural migration to module data as appropriate
 None
| Allows for full analysis of each remaining module Will probably camp on the backlog without resolution as it already has |
|---|
| Estimated cost | | |
|---|
Action items
Outcome