►
From YouTube: Plan and track projects closer to your code #DemoDays
Description
Matt Butler, Senior Product Manager, shows how rapidly the new GitHub Issues adapts to the way your team works.
0:00 - Start
0:40 - Planning and Tracking as it relates to Developer velocity
2:15 - Why use GitHub Issues to plan and track work?
3:34 - A first look at GitHub project tables/spreadsheets
7:00 - Moving to a project board view/Kanban and slicing views on the fly
9:29 - Three variations on workflows - standard backlog management
14:39 - An iteration-focused workflow/sprints
19:46 - Planning view vs managing the current sprint day-to-day
22:57 - Epic tracking and building a birds-eye view
34:22 - Dynamic filtering for different views
Sign up for the beta: https://github.com/features/issues
A
Hello,
hello,
everyone
welcome
back
to
another
fun
episode
of
demo
days.
Hey
get
rid
of
that
all
right,
cool
cool
cool.
If
this
is
your
first
time
here,
definitely
say
hi
in
the
chat.
Let
everyone
know
where
you're
watching
from
today,
if
you've
been
following
us
closely,
we
recently
introduced
new
beta
features
within
github
issues,
all
to
bring
your
planning
and
tracking
efforts
much
closer
to
the
actual
work
on
your
code.
B
Hey
thanks
aj,
so
hi
everyone,
my
name's
matt,
I'm
a
product
manager
here
at
github
and
I'm
also
joined
today
by
eric
who's,
going
to
be
helping
us
out
in
the
chat.
So
as
a
bit
of
an
introduction
about
me,
I've
been
working
in
the
developer
experience
space
now
for
around
the
last
10
years.
I
previously
co-founded
a
project
management
company.
So
it's
a
really
big
interest
to
me
in
how
teams
can
successfully
plan
and
track
their
work
while
still
having
a
great
developer
experience
and,
in
my
opinion,
having
that
great
developer.
B
Experience
also
really
helps
companies
in
terms
of
getting
the
right
velocity
and
hitting
the
right
objectives
and
the
right
outcomes
that
they're
really
looking
for
and
in
order
to
enable
that
to
happen.
Staying
close
to
coding
github
is,
in
my
opinion,
one
of
the
best
ways
that
you
can
do
that.
So
today,
I'm
going
to
show
you
a
bit
around
the
new
projects
and
talk
about
how
we
can
use
those
for
different
situations.
B
So
if
you
haven't
signed
up
yet
make
sure
you
check
out
our
page
here
at
github.com
features
issues
where
you
can
sign
up
and
request
access
for
any
of
your
accounts
into
the
beta.
We
have
been
working
our
way
through
the
backlog
there,
but
we
are
still
quite
early
in
the
private
beta
we're
working
hard
to
open
this
up
to
as
many
people
as
possible
as
quickly
as
we
can
so
please
bear
with
us
there,
but
hopefully
this
will
be
a
good
sneak
peek
for
you
all
today.
B
What
is
in
store
for
us
there
and
one
of
the
questions
that
a
lot
of
teams
kind
of
ask
me
is
around
kind
of
like
why
github
issues
like
why
use
github
issues
for
planning
and
tracking
and
for
me
we
all
need
a
way
to
be
able
to
plan
our
work.
We
need
to
track
issues
and
we
need
to
talk
about
the
things
that
we
build.
I
github
our
universal
answer
to
this
is
github
issues,
so
github
issue
tracking
is
special
because
it's
so
focused
on
simplicity.
B
It's
really
focused
on
being
flexible
and
they're,
just
so
powerful,
whilst
being
both
those
things.
So
we
github
issues
you
can
express
ideas
with
github
flavored
markdown
you
can
assign
and
mention
contributors.
You
can
react
with
emoji.
You
can
clarify
things
with
attachments
and
videos
and
we
recently
actually
like
increased
the
size
of
videos.
You
can
add
and
added
support
for
additional
file
types.
So
it's
easier
than
ever
to
be
able
to
make
things
as
clear
as
possible
within
issues
and
also
you're
really
connected
to
the
code
base.
B
So
with
that
being
said,
let
me
just
dive
right
into
a
demo
today.
So
there's
a
bunch
of
different
things
that
I
want
to
take
you
through
for
the
new
projects,
but
let's
have
a
look
right
here
at
one
that
we
put
together
earlier.
So
this
is
essentially
one
of
the
new
projects
and
what
it
will
look
like
once
you've
started
to
populate
it
with
some
different
issues.
B
So
one
of
the
things
you'll
notice
here
is
that
we
have
been
heavily
inspired
by
the
spreadsheet,
and
this
was
something
that
we
found
from
talking
to
lots
of
different
teams
and
whatever
tracking
solution.
They
were
using
and
yeah,
there's
quite
a
few
on
the
market,
whichever
one
they
were
using.
They
kept
ending
up
in
a
spreadsheet
and
what
they
found
was
they
really
valued
the
simplicity
of
the
spreadsheet
and
it
really
valued
how
customizable
it
was,
but
when
we
drilled
into
kind
of
where
does
that
fall
down
like?
B
Why
isn't
everyone
just
using
spreadsheets
for
this?
The
answer
was
because
they
became
style
really
quickly.
So,
whilst
that
initial
act
of
actually
building
out
and
creating
the
spreadsheet
was
quite
enjoyable
for
a
lot
of
teams
going
in
every
day
and
updating
cells
to
reflect
the
source
of
truth,
wasn't
a
job
that
anybody
on
the
team
wanted
to
actually
do.
B
And
so
what
we're
hoping
here
is
that
by
bringing
that
power,
flexibility
of
a
spreadsheet
and
injecting
it
with
the
context
of
github
issues
and
keeping
things
up
to
date,
we'll
be
able
to
give
a
fantastic
experience
for
for
software
teams,
and
so
this
should
feel
quite
similar
like
if
you've
used,
excel
or
use
google
sheets.
You
know
I
can
can
do
things
here,
a
bit
I
can
zoom
up,
I
can
zoom
down.
B
Let
me
just
make
sure
this
is
a
good
size
with
one
if
I
zoom
in
a
little
bit
how's
that
would
that
be
a
little
bit
better
zoom
in
excellent
okay.
So
I
can,
I
can
kind
of
reorder
these
rows.
So
obviously
things
like
prioritization
is
great.
There
I
can
make
sure
everything
is,
is
nicely
prioritizing
about
top
items
at
the
the
top.
Here
I
can
also
do
the
same
with
the
columns.
I
can
move
those
around.
B
So,
as
we
start
to
kind
of
bring
this
in,
we
can
start
to
see
like
the
different
powers
of
the
spreadsheet
star
interface.
Another
really
good
one
is
status.
This
is
actually
something
that
we
are
going
to
start,
including
by
default
into
all
new
projects,
and
the
status
field
is
a
little
bit
special,
because
what
that
lets
us
do
is
actually
kind
of
flip
from
this
table
view
into
a
board
view.
B
So
if
I
just
head
up
here
and
hit
the
board,
we
just
immediately
take
that
exact
same
data,
but
we
start
viewing
it
as
a
task
board
and
one
things
I
want
to
highlight,
as
we
kind
of
make,
that
switch
is
just
how
fast.
That
is
because
we
have
spent
a
lot
of
time
trying
to
make
this
as
fast
as
possible.
B
We
really
want
this
to
feel
fast,
not
just
in
terms
of
how
things
load,
but
also
in
terms
of
the
usability.
So
we
have
great
support
for
things
like
keyboards
navigation.
This
should
feel
kind
of
really
like
a
spreadsheet
in
terms
of
that,
but
we
also
have
built
our
new
command
palette,
which
is
probably
my
favorite
feature
that
I
use
multiple
times
a
day,
and
this
just
lets
me
kind
of
execute
all
of
the
actions
I
can
do
in
the
ui,
but
just
by
typing
that
command.
B
So
as
an
example,
there
group
by
is
one
of
the
new
things
that
we've
added
in.
So
if
I
take
group
by
and
then
pick
one
of
the
entries
there,
we
can
actually
start
to
slice
and
dice
this
screen
by
those
entries,
and
then
this
makes
it
really
easy
for
me
to
kind
of
like
drag
and
drop.
And
when
I
do
so,
it
will
update
the
value
of
the
entry
there.
B
So
one
of
the
keys
here
kind
of
as
we're
showing
these
and
this
we're
building
these
different
bits
of
functionality
out
is
that
we're
trying
to
think
of
primitives
here
so
we're
trying
to
build
in
different
plan
tracking
primitives
and
enable
you
to
put
them
together
in
your
own
way
that
really
fits
the
flow
that
makes
sense
to
your
team.
So
you
can
see
the
data
that
you
want
to
see.
B
B
Something
like
the
board
layout
might
be
perfect
for
zooming
in
and
focusing
on
what
you
want
to
achieve
over
the
next
week,
but
to
talk
a
bit
more
about
that,
I'm
actually
going
to
switch
over
to
this
other
project.
Here,
where
I
will
talk
a
bit
about
how
you
can
set
these
up
for
different
different
ways
of
working.
B
So
for
me,
kanban
is
just
all
about
flow.
It's
all
about.
How
can
we
have
a
system
where
work
flows
through
it?
It's
pulled
in
in
a
just-in-time
manner,
and
teams
can
really
easily
come
in,
see,
what's
important
and
make
those
trade-off
decisions
when
they're
deciding
what
to
work
on
next
and
how
they
want
to
organize
that
backlog.
B
One
things
we
can
do
is
we
can
look
in
and
we
can
customize
our
status
column.
So
we've
got
this
flow
here
of
backlog
in
progress,
code
review
and
done
so
again.
That's
keeping
it
quite
simple,
but
of
course
you
can
add
in
something
else
here.
If,
for
example,
you
have
a
merge
step,
you
could
just
come
in
here
and
you
could
create
a
new
option
and
for
merged
and
then
kind
of
like
it's
as
simple
as
that
to
be
able
to
reflect
that
within
the
project.
B
So
let's
say
that
something
else
we
want
to
do
here
is
to
start
communicating
priority.
So
we
already
have
things
like
we've
got.
You
know
the
number
of
items
in
the
backlog
here,
but
maybe,
as
a
team,
we've
found
that
being
able
to
be
really
explicit
around
things
that
are
like
urgent
is
really
important
to
us,
and
maybe
we've
missed
some
things
in
the
past,
and
we
want
to
make
sure
that
we
don't
miss
things
in
the
future.
B
B
Medium
and
then
we
can
just
go
and
we
can
chill
out
on
the
beach
for
things
that
are
low
variety
and
if
I
just
hit
save
that
column,
just
pops
in
here
and
I
can
come
in-
and
I
can
start
to
populate
that.
So
maybe
let's
just
pick
a
couple
of
the
items
here
and
I'm
just
going
to
set
those
to
be
urgent
and
high
just
to
help
us
kind
of
understand,
what's
most
important
for
us
to
work
on.
B
B
B
Quickly
switch
over
to
the
command
panel
and
we
can
see
our
task
board
here
and
we
have
that
layout
that
we
just
built,
so
we
just
added
merged
in
actually
going
to
drag
this
over
I'm
going
to
put
that
before
done,
because
that
makes
more
sense
from
a
flow
perspective
and
now,
as
a
team.
We
have
this
nice
view
where
we
can
see
hey
here's
everything
in
our
backlog.
That's
prioritized.
B
We've
got
a
couple
of
items
here
that
actually
this
no
status
column
and
what
that
means.
If
I
switch
back
to
a
table,
that's
these
two
items
here.
So,
as
you
can
see,
they
actually
have
a
null
value
here.
So
the
way
that
we
communicate
that
in
on
the
board
view
is
to
essentially
have
them
in
that
know,.
B
And
then
one
things
we
can
do
here
is:
I
can
actually
save
the
changes
to
this
view
and
what
that
does.
Is
that
essentially
means
that
when
I
share
this
url
now,
everyone
will
see
the
same
thing.
So
if
we
wanted
to
always
use
this
as
a
board,
we
can
save
that
as
a
view,
and
we
can
share
that
around
and
everyone
will
see
this
as
a
board
rather
as
a
table.
B
B
B
So,
let's
just
say
all
these
things
that
are
merged
in
progress
make
sense
for
them
to
be
in
our
sprint
one,
and
then
maybe
we've
got
some
things
out
here
that
we've
already
decided
are
in
sprint
too,
and
so
we're
starting
to
build
up
this
idea
of
having
this
sprint
information
just
encoded
right
here
with
the
issues
and
one
of
the
things
I'll
jump
in
and
say
actually
now,
because
it's
a
question
that
we
get
quite
a
lot
is
around
kind
of
where's
this
data
stored.
And
how
else
can
we
access
it?
B
B
B
If
you
don't
want
to,
you
can
just
kind
of
stay
in
the
simplicity
of
the
issue,
so
a
couple
of
different
options
for
how
you
want
to
work
there,
and
the
really
nice
thing
is
that
this
can
be
added
to
more
than
one
project.
So
if
there's
a
couple
of
teams,
which
we
see
quite
a
lot
right,
there's
an
issue
and
there's
more
than
one
team
that
wants
to
work
on
it
kind
of
a
stakeholder
in
it.
You
can
just
add
this
to
multiple
projects
and
each
team
can
keep
an
eye
on
it.
B
B
B
Let's
move
this
one
up,
we'll
drop
that
in
here
and
maybe
like
we'll,
take
this
one
and
in
return
we're
gonna
like
drop
it
down
and
that
one
can
go
into
our
sprint
too.
So
you
get
this
like
nice
planning
view
you
can
make
those
trade-offs
you
can
make
those
drag
and
drops
makes
it
really
easy
to
have
that
conversation
with
the
team
around
what's
important.
B
So
that's
where
the
power
of
these
views
come
come
back.
So
I'm
going
to
rename
this
and
I'm
going
to
call
this.
Let's
call
this
planning,
so
that's
our
planning
view
and
then
I'm
going
to
save
this
so
that
all
those
modifiers
that
I've
applied
to
this
so
think
of
things
like
which
columns
are
visible.
B
Is
it
a
table
or
a
board?
Is
there
a
group
by
applied?
Is
there
a
sort
applied
all
those
modifiers
get
saved
into
the
view,
so
that,
as
I
share
around
this
url,
everyone
sees
that
same
set
of
information,
so
it's
kind
of
like
curated,
essentially
so
that
you
can
make
sure
that
we're
all
talking
about
the
same
thing.
B
B
So
if
I
search
for
sprint
I'll
get
a
nicer
autocomplete
here
and
I
can
set
that
to
sprint
one
and
then
we
can
say:
okay
great.
This
has
all
kind
of
trimmed
down
into
just
the
items
that
are
in
my
first
sprint,
maybe
not
the
most
useful
thing
now
to
look
at
it
in
this
group
by
so
actually
why
don't?
We
transfer
this
over?
B
Let's
switch
this
over
to
a
board
and
then
we're
going
to
save
that,
and
now
we
have
this
great
link
of
the
ogden
raiders
team
that
we're
going
to
share
around,
and
anyone
who
comes
in
here
they're
going
to
be
able
to
see
both
these
tabs
and
they're
gonna
be
able
to
know.
Okay,
here's
where
the
team
does
that
they're
planning
kind
of.
If
we
can
see
what
they're
working
on
right
now,
we
can
see
what
they're
working
on
coming
up
soon
and
we
can
see
a
bit
about
their
backlog.
B
B
One
of
the
things
that
I
do
want
to
highlight
that
we're
working
on
right
now
is
actually
getting
in
the
custom
fields
to
the
board.
One
of
the
things
you'll
notice
is
that
when
I
look
here,
I
have
like
my
urgent,
but
I
don't
have
it
over
here-
give
us
another
week
and
you'll:
have
that
we'll
be
able
to
kind
of
bring
those
custom
fields
through
and
that
one
is
is
literally
going
through
the
release
motions
as
we
speak.
B
Cool,
well,
I'm
just
going
to
really
quickly
pause
there
to
see.
If
there's
any
questions
coming
in
before
I
move
on
to
the
next
one,
where
I'm
going
to
talk
a
bit
about
epic
tracking
and
how
to
build
a
bird's
eye
view.
But
yes,
I'm
going
gonna
do
a
quick
pause
and
see
if
there's
anything
coming
in.
B
Okay,
well,
let's
keep
going
then
so,
let's
talk
about
this
one.
So
this
is
a
really
fun
use
case,
because
I
think
what
we
just
looked
at
with
the
kanban
flow
and
with
the
iteration
flow
we've
got
a
slightly
unique,
take
on
that,
but
they're
things
that
a
lot
of
teams
are
already
doing
so
a
lot
of
teams
are
already
working
in
that
way,
and
I
think
we
just
given
teams
a
much
faster
way
of
doing
that,
the
way
it's
closer
to
the
code.
B
But
thinking
of
how
we
give
teams
a
bird's
eye
view
of
what's
happening,
I
think
that's
a
really
unsolved
problem
for
a
lot
of
teams.
So
I'm
going
to
talk
you
through
how
we
do
that
here
and
how
we've
been
able
to
really
adapt
our
process
using
these
new
projects
and,
in
my
opinion,
make
it
10
times
better.
B
B
And
then
I'm
going
to
come
in
here
the
way
that
I
add
issues
to
a
project.
I
can
add
issues
I
can
add
prs
and
I
can
also
add
draft
issues.
So
draft
issue
is
is
literally
kind
of
just
a
piece
of
text
like
that
and
then,
if
I
have
that
I
can
actually
just
kind
of
convert
that
to
an
issue
really
kind
of
easy.
So
if
I
just
kind
of.
B
On
a
demo
repo
and
just
like
that,
I've
kind
of
converted
that
into
an
issue.
So
that's
a
really
nice
way
of
kind
of
starting
to
populate
these
if
you're
starting
from
scratch-
and
you
want
a
fast
way
to
workflow
information
into
a
project-
you
can
kind
of
just
create
a
bunch
of
those
draft
issues
and
then,
when
you're
ready,
convert
them
into
actual
issues.
B
So
what
we
do
is
we
use
this,
this
kind
of
concept
of
tracking
issue,
it's
kind
of
like
an
epic
I've
kind
of
used
that
terminology
in
the
past-
and
I
know
lots
of
teams
use
that
terminology
of
epic.
This
idea
that
here's
a
big
kind
of
initiative,
slash
big
issue.
Maybe
it's
the
deliverable
of
the
thing
that
actually
goes
out
to
the
end
user
or
when
we're
ready
to
release
it.
B
Let's
have
a
look
in
this
one
see
this
good
example.
So
do
something
like
this,
where
we
use
the
task
lists
and
the
checkbox
in
order
to
break
this
work
down
and
to
allow
people
to
come
into
the
actual
issue
and
see
what
the
details
are
and
then
you
can
kind
of
start
to
traverse
traverse
this
right.
B
So
think
of
this
as
a
graph
that
you're
able
to
reverse-
and
I
can
kind
of
come
in
here-
see
the
details
and
then
I
can
kind
of
walk
back
up
back
that
graph
and
find
out
kind
of
like
what
that
parent
issue
is.
So
this
is
this,
this
kind
of
unit
of
work
that
is
around
that
four
to
six
weeks
that
we're
going
to
use
to
build
out
our
roadmap.
B
B
B
B
There
we
go
so
now
everything
has
an
attached
point
person
and
then
there's
one
more
field
that
I
want
to
kind
of
create.
Here,
that's
a
single
select,
and
that
is
progress,
and
this
is
where
we're
going
to
be
communicating
how
these
are
doing
and
if
there's
anything
that
kind
of
like
the
team
should
be
worried
about
or
kind
of
actioning.
B
B
B
And
then
so
again
we're
starting
to
build
this
out,
we're
starting
to
bring
in
the
information
that
the
team
care
about,
and
then
we
start
to
craft
the
view
so
that
it's
easy
to
consume.
So
unless
I
do
that,
I'm
going
to
come
back
to
my
old
friend
the
group
buy.
I
am
going
to
group
this
by
status
and
then
this
gives
us
kind
of
a
nice
way
to
see
this.
B
B
B
When
are
we
actually
going
to
be
releasing
this
to
people?
I
know
that's
an
important
one:
maybe
we
also
care
about
a
day
like
started
date.
When
did
we
actually
start
work
on
this
item?
I
know
that's
another
kind
of
important
one,
and
so,
as
we
come
into
this
really
easy,
we
can
just
start
picking
this
date
so
objective
ship
date.
Let's
say
that
one's
going
out
early
september
we'll
do
a
friday
release
we're
feeling
brave
this
one's
going
out.
B
B
So
I
think
what
we
end
up
here
then,
is
again:
it's
like
really
customizable
set
to
the
team
and
really
easy
for
the
team
to
change
this.
If
they
decide
that
they're
not
really
using
the
projected
ship
date
or
maybe
the
start
date
doesn't
matter
to
them
for
some
some
reason
really
easy
just
to
get
get
rid
of
it.
You
can
just
kind
of
go
in
here
and
just
actually
kind
of
like
hide
this.
B
B
B
B
B
B
B
B
We've
talked
a
bit
about
how
we
can
use
the
new
project
to
run
iterations
and
we've
also
looked
at
how
we
can
take
that
step
up
and
look
at
things
from
a
kind
of
more
high
level
view,
and
we
can
create
this
bird's
eye
view
of
the
roadmap.
That
is
really
easy
to
share
and
kind
of
keep
updated
between
the
teams
so
happy
to
take
any
questions
if
there
are
any.
So
let
me
just
pause
for
a
moment
and
see
if
there's
any
questions
coming
in.
B
So
here's
a
question
from
brian
patrick:
will
this
support
again
you
based
on
dates?
Yes,
I
very
much
hope
so
I
mean
that's.
Definitely
one
of
the
primitives
that
we
want
to
be
introducing
here
that
I
think,
will
be
really
cool
so
as
we
think
about
these
layout
primitives,
you
know:
we've
got
this
layout.
The
table
we've
got
the
layout
the
board.
I
would
love
to
see
us
expand
this
in
the
future.
B
Again
is
definitely
the
number
one
request
we
get
for
that.
I
often
hear
it
referred
to
as
the
timeline
view.
I
think
that's,
maybe
the
the
favored
way
of
saying
kind
of
gantt
chart
these
days,
so
we
might
call
it
timeline.
Based
purpose
will
be
the
same
same
thing.
So
that's
one
that
I'm
kind
of
very
looking
forward
to
don't
have
a
timeline
for
you
on
that
one
just
yet,
but
that's
definitely
something
to
keep
an
eye
out
for
in
the
future.
B
Awesome
well,
thank
you
so
much
for
joining
me
today.
This
was
really
great.
I'm
happy
to
stick
around
in
the
chat
and
kind
of
answer.
Any
further
questions
you
have
so
I'll
do
that,
but
my
takeaway
for
you
all,
is
you
liked
what
you
saw
if
you
thought
this
was
gonna,
be
useful,
then
come
come
along
sign
up
for
the
beta.
Let
us
know
your
organization
and
we'll
get
you
added
it'd,
be
great
to
get
your
feedback
and
let
us
share
what
we've
been
building
with
you.