Feature | Issue | Who | Notes / TODO |
---|
Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-1302 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-173 |
---|
|
/ Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,assignee,status |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-174 |
---|
|
| | UXPROD-775 handles system-wide tag deletion |
Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-1520 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-162 |
---|
|
/ Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-163 |
---|
|
| |
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-1559 |
---|
|
| Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-79 |
---|
|
| | Nested arrays cannot be sorted currently. Similar issue with coverage statements. That's being done in line 105 of entitlement.groovy, so that may be reusable code model. |
| Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-92 |
---|
|
| | Generator changes made. Held up with testing strategy, so no PR made yet. |
| Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-49 |
---|
|
| | Kurt has had discussion with Wayne Schreider. Moving away from ansible roles, towards a front-end module to provision those permissions. Details in Jira. (Preference is to use this for all bootstrapping.) Makes sense to do with permission sets. |
| Jira Legacy |
---|
server | System JiraJIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-139 |
---|
|
| | Aim to wrap up next couple of days, pending input from JohnC. Problem being tackled is to address deeply nested paths (eg, /license/record/id/edit/amendment ). SearchAndSortQuery gives more direct control over how results are handled. Works well for some applications, such as licenses, where it handles data routing better. |