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
Technical feasibility of research report recommendations… i.e. what’s next after “continuous page numbering” #3974?
Yang – couple other tickets that fall under technical feasibility here…
We estimated in the workshop things like jump links would be really hard. Haven’t completed write up, not sure it’s worth continuing. Is it worth spending time to know just how hard that would be?
Jen – it will be nice to have this documented someday, but doesn’t need to be done immediately.
Mack to add to backlog
Tasks
What work is necessary for this story to be completed?
Acceptance Criteria
What will be created or happen as a result of this story?
How to configure this issue
Attached to an Epic (what body of work is this a part of?)
Labeled with Practice Area (engineer, data science, design, research , product)
Labeled with Type (bug, request, discovery, documentation, etc.)
The text was updated successfully, but these errors were encountered:
Issue Description
[Notes from sprint planning on 01/28/25]
Tasks
Acceptance Criteria
How to configure this issue
engineer
,data science
,design
,research
,product
)bug
,request
,discovery
,documentation
, etc.)The text was updated successfully, but these errors were encountered: