►
From YouTube: GitLab - Plan:Project Management Sprints MVC Discussion
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
At
that
point,
we
have
a
model
that
behaves
like
a
milestone,
not
entirely
like
a
milestone,
but
it'll
be
able
to
tell
you
whether
the
for
the
percentage
of
issues
are
complete,
we'll
be
able
to
assign
issues,
but
from
a
back
in
perspective
inside
of
the
rails
console,
and
that
is
why
I'm
currently
also
working
on
the
Sprint's
finder
misprints
finder.
It
just
finds
Sprint's
based
on
on
the
criteria.
You
give
it
right.
So.
A
Right,
so
that's
why
I'm
working
on
the
career
on
this
bridge,
finder,
the
sprint
finder
and
the
sprints
create,
create
update,
delete
and
promote
well
promote,
I
guess
I
could
I
could
leave
it
for
later,
but
at
least
create
update
and
delete
of
services.
Those
three
services
are
required
for
the
sprints
controller.
A
You
know
everything
is
in
the
line
where
I
need
these
three
Amar's
that
actually
add
the
model
behavior
right
and
that
is
most
likely
being
merged
either
today
or
Monday.
It
really
depends
on
whether
I
can
get
it
done
before
Myra's
afternoon,
because
that's
when
she
will
be
taking
a
look,
then
the
the
sprints
finder
already
got
its
initial
reviews.
So
I
need
to
address
that
change.
C
B
A
I'm,
actually
thinking
that
by
Wednesday
or
Thursday
of
next
week
at
the
latest,
I
will
have
at
least
a
work
in
progress.
Mr
rinse,
the
actual
controller,
the
sprints
controller,
and
with
that
sprints
controller
in
place
front
again,
can
you
know
at
the
sprint
data
to
the
sidebar
and
allow
the
the
sprint
to
be
added
via
the
sidebar
quick
actions?
We
can
do
later.
Yeah,
quick.
A
D
A
New,
it
is
essentially
exactly
the
same
behavior,
because
I
am
refactoring
milestone
into
a
concern,
but
it'll
it'll
be
easy
to
diverge
afterwards,
because
this
is
a
brand
new
model,
completely
separate,
completely
separate
table.
It
has
the
same
structure.
The
table
has
exactly
the
same
structure.
Well,
not
exactly
the
same
data
base
team
took
the
opportunity
to
tell
me
to
improve
certain
things
about
the
table,
but
it
basically
behaves
the
same
cool
and
then
API.
A
That
would
be
the
approach,
I
think
I'm,
not
sure
how
we're
yeah,
yeah
yeah
so
I
think
for
a
couple
months
ago
we
decided
that
we
have
to
implement
API
on
graph
QL
and
then
use
the
graph
QL
methods
inside
of
the
v4
API,
so
you're
not
supposed
to
implement
anything
new
in
v4
API
would
come
later.
Unless
you
know
a
front-end
wants
to
do
the
API.
Instead
of
the
controller,
we
could
do
that
I,
just
don't
create
the
controller.
I
create
the
actual
graph
QL
API.
First,
yes,.
C
C
A
Because
yeah
yeah
yeah,
because
you
can
just
ask
for
new
attributes
for
less
attributes
or
whatever
you
need
good
news
there,
because
I
haven't
started
working
the
controller.
There's
zero
cost
to
telling
me
now
that
I
need
to
do
the
graphical
API
instead
of
a
controller
I
mean
I,
still
need
all
these
services
that
I'm
talking
about
anyways
in
the
graphic
you
LAPI
it
just
changes.
A
My
my
thinking,
okay,
I'll,
add
it
to
the
crafty
old
API,
first
and
I'll
completely
forget
about
the
controller
controller
will
not
exist
ever
actually
it
might
have
to
which
is
because
we
we're
gonna
re
in
order
to
actually
create
the
sprint.
You
know
like
you
haven't
you
have
a
list
of
all
the
Sprint's
that
exist
Donald.
This
would
be
a
question
for
you.
We
can
either
do
it.
You
know
how
the
rails
view
with
that
just
grabs
all
of
those
Sprint's
that
exists
unless
you
delete
it.
A
A
So
I'll
just
read
the
graphical
API
I'll
forget
about
the
controller
and
front
and
we'll
generate
all
these
different
areas.
So
I
mean
the
only
really
new
thing
you
got
to
create
is
the
create
edit
and
delete
Sprint's
page
because
the
other
ones
are
just
anything:
the
sidebar
and
editing
the
issues
and
amaras
views
yeah
I'm
glad
we
had
the
same.
D
A
D
B
A
Literally,
just
reading
of
changing
the
name
and
bleeding
this
print
right,
we
could
do
just
that
and
it
and
then
adding
the
issue.
I
mean
the
thing
is:
adding
the
yeah,
actually
just
creating
updating
and
destroying
this
friend
doesn't
really
add
value
to
the
user
right
because
you're
not
adding
it
to
an
issue
you're,
not
adding
it
to
a
milestone.
So
immersion
I'm,
sorry,
but
it
would
be
a
valid
MVC
and
it
does
remove
the
complexity
of
updating
the
Mercia,
quests
and
issues
to
add
the
system
notes
and
the
emails
of
these
things.
So.
B
A
Like
you're,
really
just
by
changing
the
main
you're,
changing
the
sorry,
the
signal
you're,
sending
your
developers
right
like
at
least
that's
what
I
got
from
all
of
the
research
that
UX
has
been
doing
like
people
just
want
to
be
able
to
say
this
belongs
to
milestone
whatever,
and
it
belongs
to
the
Sprint.
For
week,
five
or
something.
C
Well
then,
the
next
thing
that
you
do
after
this
so
like
we
can
do
the
system
notes
and
all
other
stuff,
but
the
basic
goal
is
like:
if
you
know
which
issues
are
part
of
what
Sprint
right
and
you
can
see
how
many
got
completed
that
sprint
and
then
you
just
can
start
to
calculate
the
velocity
which
we
can
show
on
the
Sprint
view.
And
then,
when
teams
going
and
do
their
planning,
they
say,
I
can
only
do
X
amount
of
weight
per
Sprint
so
like
they
make
trade-off
decisions.
A
B
C
So
that's
where
that's,
where
stepping
back
like
the
stuff,
that
Patrick
is
doing
overlaps
a
lot
with
the
stuff
that
we
eventually
like
want
to
do
in
Sprint's,
because,
like
the
synthetic
labels
or
whatever
he's
doing,
we're,
gonna
want
to
have
that
same
approach
for
sprints,
probably
and
so
like
how
you're
separating
out
the
mouse
and
stuff
to
a
concern
that
same
stuff
should
probably
separate
out
of
concern.
So
I
don't
know
if
it
makes
sense
for
you
guys
to
pairing
that
part
of
it
done
so
you
don't
redo
things
here
or
like.
C
C
B
From
some
discussion
in
the
past
there
was
a
decision
to
have
a
different
event
tracking
each
of
these
activities.
So
every
time
an
issue
is
closed,
every
time
a
milestones
changed
and
something
else.
Every
time
a
way,
it's
changed
on
an
issue
that
a
different
object
with
track
each
of
those
activities.
So
in
that.
B
B
A
B
A
A
I
mean
the
main
problem
here
is
that
I
have
to
refactor
things
into
the
other
model,
so
it'll
basically
end
up
being
a
race
to
the
finish
where
the
first
one
to
merge
is
the
one
that
doesn't
have
to
read
factor
everything
but
yes,
I
I
did
I,
wrote
it
over
right
now
to
follow
up
with
Patrick
I'll
meet
with
him.
Just
to
make
sure
that
you
know
these
changes
are
making
or
not
going
to
kill
him
when
he
tries
to
refactor
and
everything
is
entirely
different.
C
I
think
I
think
one
of
the
things
too
is
like
touching
into
that
work
like
eventually
on
an
issue
or
an
issue
want
to
show
the
milestones
that
has
been
assigned
to
in
the
past,
maybe
as
well
as
the
current
one
right.
So
one
of
the
reasons
why
people
ask
for
multiple
milestones
is
because
they
want
to
be
able
to
report
historically
accurate
information
on
milestone
view
to
see
like
if
an
issue
blowing
there
lots
of
different
things
when
I
go.
Look
at
the
milestone
over
spring
for
I
want
to
see
it.
C
C
D
A
C
C
In
the
course
doing,
this
were
like,
if
you
delete
things
it
never
Tinley
releases
erases
the
history
from
the
issue
itself.
So
then
you
don't
have
another
disability
right,
so
I'm,
almost
and
I'm,
like
I,
want
to
do
this
with
labels
as
well.
Eventually,
we're
I
think
we
should
shift
an
archive
model
instead
of
the
delete.
So
we
aren't
destroying
data
because
that's
like
for
compliance
and
other
purposes
but
like
this
is
something
that
Holly
and
I
can
talk
about.
But
clearly
you
can
create
a
sprint.
A
C
A
C
One
other
thing
thinking
about
into
the
future,
where
the
thing
that
diverged
is
like
setting
milestones
on
or
I
mean
Sprint's
like
an
auto
schedule.
So
basically
they
always
start
there
two
weeks
long
and
they
always
start
on
Monday
right.
So
that
way,
you're
not
really
creating
them
yourself.
This
is
what
we're
doing.
Would
that
support
that
well
or
like
I?
Just
don't
want
like
break
things
or
not
give
the
future
direction
up
front,
so
you
can
make
good
architecture.
This
is
yourself,
but
that's
definitely
not
NBC
I'm,
just
saying,
like
eventually.
A
Actually,
don't
allow
deletion
and
updates
you
just
removed
a
lot
of
work
related
to
you
know
creating
system
notes
when
something
gets
deleted,
creating
and
stuff
like
that,
and
the
only
system
no
required
now
is
when
you
change,
which
milestone
sorry,
which
sprint
is
assigned
to
an
issue
or
merge
West,
you
might
go.
That's.
C
A
C
A
Going
to
put
that
at
the
end,
because
you
know
I
can
I
can
create
the
ones
that
I
really
want
understand
need
are
the
spring
create
service?
That's
it!
That's
all.
I
need
with
the
spring,
create
service.
I
can
create
the
graph
QL
initial
rescue,
L
API,
that
lets
you
actually
grab
the
the
sprint
information
and
with
that
sprint
information
and
then
I,
have
to
update
the
issues
and
merge
request
a
graphical
api's.
A
B
B
Yeah
right
absolutely
no
code,
no
functionality
right
so
once
we
have
that,
like
there's
going
to
be
work,
probably
to
add,
like
I,
would
imagine,
we
would
typically
spend
a
milestone
on
the
kind
of
work
that
involves
being
able
to
search
by
any
object
right.
So
if
we
can
break
out
that
kind
of
stuff
that
we
know
we
have
to
get
for
the
first
iteration
just
create
an
issue
with
anything.
You
think
that
could
be
broken
it--and
get
into
somebody
else
and
that
would
at
least
reduce
the
risk,
and
we.
B
A
Yeah
I
mean
now
that
I'm
talking
to
you,
I
I've
been
able
to
whittle
this
down
a
lot.
You
know
just
the
create
service,
the
graph
QL
API
only
to
create
part.
We
can
once
that's
done
front
and
can
come
in,
but
while
that
is
being
done,
there's
nothing
stopping
other
back-end
engineers
from
creating
the
update
service,
the
story
services,
things
like
that
and
the
story
service
does
need
to
create
system
notes
and
emails
and
stuff
like
that,
but
with
the
model
merged,
it's
actually
not
hard
to
paralyse.
This
work
also.
C
Think
you
could
probably
do
the
front
end
at
the
same
time
like
if
we
have
four
get
some
UX
direction
from
Holly,
then
I
don't
know
like
I
always
wrote
stuff
using
mocks,
so
I
would
write
my
craft,
my
craft
queries
and
I
talk
to
my
back
in
engineering,
be
like
hey.
What's
the
query
going
to
look
like
and
like
I
would
moderate
it
out
and
mock
the
data
and
then
I
could
build
my
whole
front
end
and
then,
as
soon
as
like
the
back
end
was
ready.
C
A
C
Do
you
want
me
to
just
like
write
down
specific,
like
from
user,
for
you,
I
can
create
a
sprint.
I
can
add
an
issue
to
sprint.
I
can
like
it
not
all
most
stages.
That's
way,
so
you
can
feel
like.
Ok,
now,
I
can
see
a
list
of
issues
on
my
sprint.
So
we
like
kind
of
do
things
breaking
down
the
big
like
Sprint's
thing,
into
very
small
user
tasks
that
we
feel.
A
A
C
A
A
A
We
can
do
that
quickly
and
you
know,
with
the
spring
created
then
step:
two
is
screens
F
and
J
and
H
yeah
fjh,
and
that's
your
MVC
right.
There
yep
so
two
issues,
one
issue
for
the
creation:
one
issue
for
the
actual
assignment
two
issues
and
I
want
to
shoot
to
the
actual
assignment.
Two
milestones
emerge
press.
Do
we
want
to
assign
these
to
merge
quest?
I
mean
I'm,
adding
the
relationship
this
one
case,
because
it
was
not
expensive
to
add
and.
C
That's
how
I'm
I'll
see
it
work
right
now
we
can
solve
this
two
ways,
one
way
and
I'm
gonna
talk
to
whoever
the
PM,
James,
Ramsey
or
somebody
else
right
now.
Issues
are
soft
related
to
merge
requests,
but
we
need
we
need
to
add
a
different
kind
of
relationship
where
there's
in
actual
this
merger
quest
is
implementing
this
issue.
It's
not
just
related
to
like
it's
literally
implementing
it,
and
so
it's
there
inexplicably
linked.
A
A
A
C
A
Yeah
so
be
through,
thee
is
one
issue
and
F
through
H
is
another
issue,
and
then
we've
got
the
MBC,
and
while
this
is
happening,
we
can
actually
be
working
on
adding
editing
to
the
to
the
API.
You
know
and
destroying
or
archiving
right
now
milestones
are
allowed
to
be
destroyed
by
the
way
I
know,
yeah
I
do
see,
I
just
see
what
you
mean.
If
you
destroy
a
milestone,
you're
you're
getting
rid
of
a
lot
of
information.
It's.
C
The
same
thing:
when
you
kill
a
label
to
leave
a
label,
it
removes
it
from
the
list
and
there's
somebody
done
accident.
Then
it's
like
you
lose
all
that
you
can't
ever
get
it
back.
So
if
you,
if
you
archive
things
like
it,
I
think
that's
a
better
approach,
because
if
you
archive
it
it
could
disappear
from
the
issue
but
then
like.
C
If
you
not
on
our
credit,
then
it
comes
back,
and
so
it's
like
you're,
not
really
removing
issues
you're,
just
like
hiding
things
that
don't
matter
anymore,
basically
but
you're
not
losing
all
the
data,
for
it
only
is.
A
C
That's
where
there
can
only
be
one
like
that.
The
theory
is
and
correct
me
if
I'm
wrong.
We
want
to
show
on
an
issue
like
what
Sprint's
it's
been
part
of.
What
writing
milestones
has
been
a
part
of,
but
it
only
can
ever
be
part
of
one
active
at
a
time
right
so,
like
the
the
logic
would
be
like
you
can't
archive
an
active
sprint,
you
can't
archive
an
active
milestone
so.
C
C
Or
they
probably
need
that
for
compliance
yeah,
that's
where
I'll
talk
to
Matt
Gonzales
and
manage
because
he's
working
on
that,
but
I
like
that
to
basically
the
taking
system
notes
to
the
extreme
and
rolling
them
all
up
until
the
compliance
report.
Basically,
and
so
we
can
make
sure
that
that
stuff
happens,
but
all
of
that
is
not
MVC
I'm.
Just
like
saying.
C
A
I
think
we
can
start
with
B
through
the
next
week
seriously:
I'm
gonna
prioritize
the
create
finder
and
then
the
graph
QL
API,
with
a
graph
QL
API
inflight,
not
even
done
just
in
flight,
so
I
know
more
or
less
what
the
queries
are.
Gonna
look
like
from
can
totally
jump
in
and
create
these
views,
and
you
know
mocking
and
I
think
connect
with
me.
Okay,.
A
C
C
A
A
A
C
A
C
B
C
C
A
C
C
A
A
Set
boxing
this,
you
just
removed
a
lot
of
work
towards
the
MVC
and
I'm
very
glad
that
we
talked
about.
We
talked
with
Donald,
because
I
was
going
to
do
a
controller
instead
of
a
graphical
again
kaha
and
we're
done
I've
been
necessary.
Oh
yeah,
cool
I
actually
feel,
but
this
a
lot
more
lightweight.
Okay,
because
I
don't
have
to
worry
about
system
notes
and
all
that
stuff.
Yet
yeah.
C
B
C
C
A
So
I'll
I'll
get
that
straight
model
review
wrapped
up
today,
so
that
that
I'm
blocks
everything
else
and
then
I'll
thing
in
the
graphical
API
issue
and
I'll
think
you
directly
gave
as
well
as
Donald
and
you
jump
when
I
feel
like
we
can
get
started
on
like
right
before
I
start
on
the
graphical
API
I'll
tell
you
so
that
you
can
see.
If
there's
a
front-end
engineer,
that's
able
to
pick
this
up.