Versions Compared

Old Version 70

changes.mady.by.user Allison Costa

Saved on

compared with

New Version 71

changes.mady.by.user Allison Costa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DescriptionJIRA/BehaviorImplementedLast WorkingTestedStatus

As an Author, I would like to view my proposals.

  • in a list
  • in a detailed view (Card)

<Sprint 29Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

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



  • steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment.
Saving and ARPersisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.



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.




Status
subtletrue
colourRed
colorgreen
titlebugs

Warning  "cannot generate OS"

  • OS exists for AR1 → add another AR→ immediately, warning appears
Navigate and Edit OS on fresh AR



Cannot DoNot Implemented

Create Proposal

...


Capability (General)

...