You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.
erotondo opened this issue
May 5, 2021
· 1 comment
Labels
BacklogA backlogged issue that still needs to be completedEditorAn issue related to the editor component of the softwareFrontendAn issue handled by the frontend developersGit-KingsFrontend
Option to use a template when creating a new scenario
Potentially using an existing scenario as a template
Have a template that is “strict”/follows the process as scenarios were originally described to us (Intro -> Problem Setup/Who you are -> Initial reflection -> Initial action -> stakeholder conversations -> Middle reflection -> Final action -> Outcomes and consequences -> Final reflection ; or something along these lines)
BACKLOGGED: Ran out of time to implement; needed to focus on integrating with the backend team to set up new endpoints that worked with the new schema before deploying changes to the server.
The text was updated successfully, but these errors were encountered:
erotondo
added
Git-Kings
Frontend
Backlog
A backlogged issue that still needs to be completed
Frontend
An issue handled by the frontend developers
Editor
An issue related to the editor component of the software
labels
May 5, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BacklogA backlogged issue that still needs to be completedEditorAn issue related to the editor component of the softwareFrontendAn issue handled by the frontend developersGit-KingsFrontend
Option to use a template when creating a new scenario
BACKLOGGED: Ran out of time to implement; needed to focus on integrating with the backend team to set up new endpoints that worked with the new schema before deploying changes to the server.
The text was updated successfully, but these errors were encountered: