penumbra
penumbra copied to clipboard
decaf377: propagate changes to circuit stack
This was moved into the current sprint outside of sprint planning - can someone account for this? @cronokirby @TalDerei
Yeah this task should be in the current sprint since it's in progress.
That is incorrect - it has not been estimated, and was not prioritized and explicitly added during sprint planning, so it should not be being worked on without explicit admission into the current sprint iteration. Other work in the Sprint 0 milestone should take priority, unless myself and @hdevalence explicitly sign off on adding a ticket.
Moved back to backlog for sprint load reasons