| Description | JIRA/Behavior | Implemented | Last Working | Tested | Status |
|---|
As an Author, I would like to view my proposals. - in a list
- in a detailed view (Card)
|
| <Sprint 29 | Sprint 37 | Sprint 37 | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| color | green |
|---|
| title | working |
|---|
|
|
| Saving within a CR | Capability Requests have their own save button. Though information looks like it is kept on the frontend, it is not in the backend without hitting save. - Change CR1 → don't save → navigate to CR2, change CR2 → save
- Only changes to CR2 are kept
- CR1 changes are not saved
- Change CR1 → don't save → navigate to CR2, change CR2 → don't save → navigate to CR2 (changes are still present in front end) → save
- Changes to CR1 are persisted
- Changes to CR2 are not persisted
- A refresh without hitting save does not persist work
| Jira |
|---|
| showSummary | false |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-976 |
|---|
|
|
|
|
| - steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment.
| Status |
|---|
| |
|---|
| subtle | True |
|---|
| colour | Yellow |
|---|
| color | green |
|---|
| title | Review |
|---|
|
|
| Saving and AR | Persisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used. | Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-976 |
|---|
|
|
|
|
| | Status |
|---|
| |
|---|
| subtle | True |
|---|
| colour | Yellow |
|---|
| color | green |
|---|
| title | Review |
|---|
|
|
| Observation Specification Generation | Popup warns user is overwriting their OS. Pops up even if no OS is currently generated or if one cannot be generated (validation needed?) If OS cannot be generated, tab is available but empty. | Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-972 |
|---|
|
| <Sprint 35 | Sprint 37.538 | Sprint 37.538 | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| color | green |
|---|
| title | working |
|---|
|
|
| Navigate and Edit OS on fresh AR |
|
|
|
| Not Implemented | Status |
|---|
| |
|---|
| subtle | True |
|---|
| colour | Grey |
|---|
| color | green |
|---|
| title | ignored for release |
|---|
|
|
