►
From YouTube: Plan | FY21Q1 OKR - Competitor Walkthrough
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
Hey,
it's
Gabe
Keenan
park
managers
in
the
plan
stage
we're
going
to
do
a
demo
today,
JIRA-
and
this
is
part
of
our
cue
121,
ok
hours
and
the
park
organization
with
the
goal.
This
is
a
to
walk
through
Giro,
but
also
can
I
talk
about
building
a
better
importing
experience.
So
it's
easy
for
customers
to
migrate
from
JIRA
or
migrate
to
get
lab
from
JIRA.
So
we
have
a
demo
JIRA
account
set
up,
and
this
is
the
basic
default
view.
A
When
you
log
in
you
have
some
project
view
you
can
kind
of
like
look
at
some
most
recent
items
that
you've
looked
at.
You
can
also
search
if
you
want
to
do
an
advanced
search,
I
guess
across
all
of
your
projects
and
then
you
can
create
something,
create
an
issue
you
can
kind
of
split
by
what
that
is,
and
what
project
it
should
go
into.
B
A
Left
achill
I
think
I
can
also
hit
the
C
based
on
that,
so
yeah
I
can
use
smart
keys,
which
is
nice
down.
Here
we
have
our
notifications.
We
can
see
the
ones
that
are
direct
notifications
versus
watching
oddly.
This
is
an
issue
that
came
up
is
folks
coming
over
to
get
loud,
we're
not
sure
how
to
watch
issues
so
I
pointed
them
TV
notifications,
toggle
in
our
sidebar
on
our
issues,
which
they
see
the
first
time.
We
can
also
switch
I
guess
to
other
products
here.
A
So
the
admin
view
we
can
confluence
is
hooked
up
or
service
desk
those
sorts
of
things,
I,
guess
fast.
Toggle
there,
a
Help
section.
We
won't
go
into
settings
user
management
system,
settings
products,
projects,
issues,
I,
guess
these
are
configurable
type.
Things
will
kind
of
walk
through
those
right,
quick-
and
this
looks
like
this
would
be
equivalent
to
get
labs
group
view
configuration.
So
it
looks
like
they
have
some
schemas
for
issue
types
and
I
can
add.
A
I
can
kind
of
customize
my
issue
type
phone
to
do
that,
make
either
standard-issue
type
or
subtest
issue
type.
So
the
idea
works
is
they?
Don't
have
that
epics,
but
then
they
have
issues
and
then
you
can
have
sub
tasks
or
sub
issues,
but
they
all
end
up
in
the
same
place.
So
we'll
go
back,
who
walk
through
the
way,
creating
a
new
project,
and
you
have
the
option
to
pick
between
a
class
and
project
or
their
next-gen
I
think
we
should
do
both.
A
B
A
Simplified
workflow
is,
instead
of
being
highly
configurable,
a
streamlined
configuration
versus
flexible
and
advanced
twenty
different
kinds
of
ports
and
classic
for
reports
for
agile
teams,
hundreds
of
marketplace
apps
and
dozens,
and
you
next-gen
and
other
things
like
multiple
boards
and
cross
project
boards,
which
would
be
like
our
groups
or
a
single
board
per
project
roadmap,
is
here
as
well,
so
it
looks
like
they
might
not
have
the
roadmap
on
the
classic.
At
this
point,
you
have
a
preference
on
which
one
you
want
start
with
when
we
go
with
the
next-gen,
since
it's
not
yeah.
A
A
A
Right
select
we're
going
to
do
a
scrum
project,
create
that
so
it
looks
like
the
first
thing
we
haven't
done
is
we
have
not
started
a
sprint,
so
this
looks
like
a
basic
board.
You
can
start
I
guess
which
we
added
to
your
favorites
over
here
I'm.
Assuming
there
are
rules
you
can
configure,
which
we
don't
have
yet
we'll
do
that
a
little
bit
and
let's
just
follow
their
instructions.
A
I
sense,
Keaney
are
here,
I'm
gonna,
go
ahead
and
add
you
I
think
you
created
you're
here
you
go,
add
cool
new
people
added,
that's
refresh
page.
You
see
that
or
it
just
doesn't
show
up
hey.
You
have
to
accept.
First
I,
don't
know
the.
B
A
I'd
probably
have
to
accept
this
interesting
little
arrow
up
here.
I
guess
this
will
pop
up
on
your
project
level
navigation.
So
you
see,
there's
a
road
map,
there's
a
backlog,
there's
a
board
pages,
adding
an
item
and
then
project
settings
I
guess
we
can
just
go
through
for
seeing
demo
sprint
one.
We
have
no
issues,
drag
issues
from
a
backlog
section
or
create
new
issues
to
play
and
work
for
the
Sprint
start
sprint
when
you're
ready,
we'll
go
ahead
and
populate
the
backlog.
A
B
A
Alert
icon'
flag
it
we
can
move
it
to
a
demo
square
on
top
of
backlog
bottom
of
backlog.
One
of
the
things
I
know
right
here
is:
when
you
have
lots
of
issues,
we
have
the
same
problem
in
get
lab
and
I've
heard.
Complaints
about
JIRA
is
that
it's
hard
to
drag
things
from
way
down
in
your
backlog
and
prioritize
them
in
some
sort
of
ordered
way.
A
So
like
assuming
this
is
list
is
super
long.
It
it's
hard
to
say,
like
I,
want
to
prioritize.
It's
almost
like
grooming,
your
backlog,
oh
I,
like
it
here,
grooming,
your
backlog
for
the
next
sprint,
and
so,
instead
of
like
assigning
it
to
a
sprint
or
something
like
that,
you
you
have
to
drag
it
all
the
way
up
to
the
top,
which
is
making.
A
So
they
have
that
it
looks
like
they
have
that
kind
of
wonky
type
thing
too,
or
even
quick.
A
certain
part
of
the
project
open
sidebar
I
mean
if
you
click
on
the
issued
tile
itself
will
take.
You
maybe
won't
take
me
no
anyway.
So
this
is
sprint
wine.
We
can
create
an
issue
droplet
here.
We
can
also
create
a
new
spring
if
we
want
to
do
that
so
spring.
A
A
A
It's
our
goal.
Now
that
we
ran,
we
are
kicked
into
our
back
to
our
board
with
to
do
in
progress
done.
It
looks
like
you
can
customize
stages
here.
So
if
we
want
to
have
a
stage
for
a
review,
maybe
we
could
have
that
before
it's
done
and
maybe
want
to
have
one
for
design
shift
that
over
here
yeah-
and
it
looks
like
this-
is
like
a
nice
little
navigator
down
here.
So
you
can.
Your
board
has
lots
of
horizontal
lists.
You
can
quickly
like
see
what's
in
scope
with
the
Ottoman
scroll,
interesting.
A
B
A
All
right
cool,
let's
close
that
out
and
let's
put
this
into
design,
so
basic-
we're
close
here,
which
pretty
simple,
want
to
open
up
this
issue
and
look
at
it.
This
is
a
nice
thing
about
this.
Is
you
can
look
at
your
issue
and
issue
bore
without
navigating
away
or
losing
your
context,
something
that
we're
working
on
looks
like
you
can
base
pretty
straightforward
description
with
the
WYSIWYG.
A
B
A
And
I
think
markdown
works
as
well
list
yep,
so
they
have
the
basic
markdown
editor
as
well.
I
guess
you
can
add
apps
here,
which
we
don't
have
anything
else
configured.
What
it
looks
like
it
will
be
a
we
can
add
in
confluence
or
whatever
the
marketplace.
Apps
are
the
functionality
of
this
issue
card
watchers
other
actions
going
to
a
parent
here
it
looks
like
move
it
clone
it
delete
it
prints,
export
the
XML
word,
look
open
issues
and
new
jury
issue.
B
A
A
Cool
yeah,
so
they
have
a
basic
pub/sub
implementation
looks
like
they
are
subscribed
here,
so
we
can
get
stuff
in
real
time.
Pretty
straightforward.
It's
kind
of
nice
I,
don't
know
the
underlying
technical
implementation,
but
some
basic
publish/subscribe
yeah.
It's
nice
lots
of
errors,
pinching,
it's
not
reassuring
necessarily,
but
that's
cool,
and
it
looks
like
back
to
the
issues
you
can
configure
the
issue
to
open
in
a
sidebar
like
on
our
issue
boards
or
you
can
have
open
in
a
dialogue.
So
that's
your
choice,
which
is
interesting.
We
can
go
ahead
and
a
story.
A
I'll
assign
this
to
me
and
you
can
also
move
through
the
workflow
stages
on
the
issue.
So
this
is
one
of
the
things
that's
really
tricky,
Bakula
that
we're
gonna
have
to
figure
out.
It's
easy
to
do
in
this
context,
scoping
it
to
a
project,
because
the
issue
belong
to
the
project
team.
You
have
a
single
issue
board,
so
you
can
have
multiple
contexts.
A
A
That's
a
cool
edit
delete
has
emoji
here
as
well
can't
add
an
emoji
to
the
word
emoji,
though,
which
is
difference
between
lesson
them.
So
it's
hard
to
see,
like
you
know,
thumbs
up
that
sort
of
thing
so
also
there's
added
some
labels
before
I'm,
just
kind
of
pretty
straightforward
labels
here
as
well
they're
kind
of
extensive
all
you
can
create
a
new
one
on
the
fly
if
it
doesn't
exist,
when
creamy
label
can't
have
spaces
or
be
more
than
20
55
characters.
Okay,
yeah.
B
A
Face
alright,
so
this
is
a
it
looks
like
you
also
have
this
option
up
here
to
attitude
epic
soup.
That
does
know
epic
has
been
graded
in
this
project,
create
your
first
epic
I.
Think
we'll
go
look
at
the
roadmap
here
in
a
second
before
we
get
there.
It's
also
worth
kind
of
noting
noting
some
other
things
in
the
project.
Settings
I
think
one
of
the
powerful
things
I,
don't
know
what
this
category
does
or
managing
him
does
I
guess
this
is
project.
A
A
In
the
project
settings
we
also
can
go
and
to
change
the
access
it
looks
like
that
stuff.
This
is
interesting
thing.
Is
there
issue
types
the
way
they
handle
that,
so
they
have
custom
fields
in
there
next-gen,
but
they
are
configurable
on
issue
type
level.
So
first,
you
can
specify
say,
will
call
an
issue
type
of
kenan
a
a
kingdom
description
and
pick
the
icon
of
this
type.
A
If
you
want,
you
can
be
a
heartbeat
yeah
like
it
and
then
save
that
if
we
create
this
new
Keenan,
if
you
type,
we
can
tell
people
how
to
use
it,
it
looks
like
we
can
delete
it,
and
then
we
can
customize
the
fields
that
show
up
on
it
so
context:
assignee,
label,
StoryCorps
announcements,
prints,
hi
fields
below
your
grade.
This
field,
you
can't
edit
its
name,
so
they
have
like
fields
that
are
system
level
fields,
and
then
we
also
could
add
things
like
I.
A
A
We
could
also
add
people
we
want
to
say,
like
specify,
maybe
who
the
reviewer.
Yes,
that's
been
something
that
folks
would
think
it
lab
avasta,
be
like
break
down
ownership
of
a
issue
based
on
roles
default.
People,
let's
just
say,
restrict
to
a
single
person,
so
you
have
multiple
assign
or
a
single
one.
I'll
save
that
and
then
I
think,
there's
dropdowns
priority
all
sorts
of
different
fields.
You
can
configure
for
this
issue
type.
A
It
does
not
look
like
they
are
yeah,
so
your
fields
then,
are
available
to
your
other
issue
types
if
you
want
to
like
pop
them
in
so
it's
easy
to
share
issue
or
custom
fields
across
your
issue,
types
and
kind
of
customize.
What
issues
look
like
I
think
this
is
kind
of
a
nifty
little
thing
and
it
flies
so
much
flexibility
out
of
the
gate
that,
like
it's.
B
B
B
B
A
A
B
B
A
A
A
B
B
B
A
A
A
B
A
B
A
A
A
You
had
a
type
drop-down
there
for
the
board.
I
think
the
only
place
you
can
add
epics
it
looks
like
is
in
this
road
map
view
so
status
in
progress
today,
export
months
toggle
between
weeks
months
and
quarters,
views
dependencies,
visualized,
work,
streams,
late
to
better
understand
your
risk,
progress
and
we'll
look
at
today.
So
let's
go
through
this
a
little
bit.
What
needs
to
be
done
and
I
think
epic
for
this
P
I
increment.
A
So
cool
we
can
do
that.
A
second
looks
like
we
can
toggle
the
dates
these.
If
we
want.
Let's
look
at
this
in
weeks,
just
because
well
it's
kind
of
hard
to,
and
you
can
pop
this
open
and
look
at
your
details
of
this
epic.
It
looks
like
which
is
pretty
much
the
same
as
an
issue
I'm
assuming,
since
we
can't
toggle
easily
on
that.
You
can
say
this
is
for
this
quarter
and
then,
let's
make
this
a
dependency
of
this.
B
B
A
I
link,
no
I
was
wondering
if
I
could
like
cross
like
things
oh
yeah,
it
looks
like
you
can
that's
weird.
Also
weird
so
I
can
see.
Third
I
like
I,
like
that
little
contextual,
pop-up
I,
do
too
the
thing
that
I
found
weird
about
is
that
dates
overlap
this
one
I
guess
you
could
have
that
way
out
here
to
feature
what
happens?
I
put
this
one.
A
A
Could
be
to
do
what's
weird
is
this
must
be
a
bug
because
I
can
see
right
here
and
progress
review
done,
but
this
one
doesn't
have
those
other
states
or
columns
that
I,
maybe
but
I
can
move
it
in
the
review,
which
once
I
did
that
it
looked
like
that.
I
might
add
to
you
the
board,
or
maybe
you
just
joined
the
project.
Muncher.
A
Cool
when
I
didn't
break
that
dependency
you're
here
and
there
is-
we
talked
about
this-
there's
no
horizontal
scrolling
here,
so
I
don't
think
again,
scroll,
oh
yeah.
I
can
then
right.
So
there
is
horizontal
scrolling
here
and
I
can
go
anywhere.
I
want.
If
we
thinking
going
here,
add
some
child
issues.
Oh
yeah.
B
A
A
Yep,
that's
nice.
This
is
just
so
one
weird
thing
I
was
trying
to
understand
is
because
I
added
this
to
a
sprint
in
another
project
yep,
but
it's
showing
the
backlog
here.
So
I
guess.
Maybe
if
there's
like
subtasks,
that
the
other
project
tests
to
take
care
of
maybe
like
does
it
show
up
on
that
projects
board?
If
I
look
here
and
I
go,
it's
my
backlog.
B
A
B
A
A
B
If
you
get
a
large
enough
like
if
you're
reporting
on
like
a
portfolio
level
roadmap,
you
probably
would
want
a
view
that
isn't
as
cluttered
is
not
the
right
isn't
as
busy
just
to
like.
If
you're
you
know,
if
we're
talking
about
like
here's,
a
plan
for
the
future,
and
you
don't
have
any
progress
information
because
nothing
started
yet
that
could
be
helpful
and
then
yeah.
If
there's,
if
you
have
a
ton
of
dependencies-
and
you
just
want
to
convey
the
timeline,
you
could
remove
that.
That
makes
sense.
Yeah.
A
A
Now,
looking
at
this
I
like
this
last
updated
and
you
can
refresh
I
guess
without
reloading
the
page
to
update
looking
our
backlog,
we
see
our
other
items
down
here
labs.
If
we
go
ahead
and
put
this
in
this
room,
one
sprint
scope
will
be
affected
by
this
action
time.
Eleven
tyramine
backlog
from
from
sprint
backlog
to
sprint
line.
That's
confirmed.
B
A
A
A
A
A
B
A
A
A
B
A
A
Should
we
you
can
quickly
hide
all
the
cover
images.
I,
guess
that's
like
hiding
labels,
it's
getting
noisy.
A
A
Think
a
higher
level
before
do
that
I
was
gonna.
Look
at
see.
Where
do
you
see
your
subtasks
like
in
here?
This
is
why
you
don't
like,
sometimes
because
this
is
a
bug
it's
eat
here,
so
I
can
see
on
this
issue,
but
it's
not
like
searchable
or
anything
which
I
wouldn't
necessarily
expect
it
to
be,
but
it
has
the
same.
Exact
interface
is
an
issue.
That's
why
I
like
just
like
tasks
is
a
thing
not
like
some
issues,
but
oh
yeah,.
A
Let's
see
here,
let's
see
if
we
can
find
out
where
we
look
at
things
like
what's
pages
here,
are
some
templates
to
get
you
started
on
this
masterpiece
create
your
first?
We
need
a
decision
can't
do
that
without
confluence,
but
it
looks
like
their
main
template.
Sir
decisions
meeting.
That's
proc
quirements
in
retrospectives,
+7,
more,
which
I
can't
look
at
unless
I
draw
confluence.
Yeah.
Okay
confluence
is
a
pretty
big
deal
like
lots.
A
A
Knots
Elysee,
you
evaluate
a
short
club
shortcut,
okay,
so
this
just
will
pop
me
open
to
my
repo,
quick,
quick,
add
the
navigation
I
guess
to
make
it
feel
more
nicer
project
settings.
Look
at
this
I,
don't
see
anything
here
for
what
it's
a
feature
you
can
toggle
on.
It
looks
like
your
right
map,
your
backlog,
your
Sprint's
reports
and
estimation
and
pages
release,
versioning
and
they're.
Pushing
up
so
hard
because
you
know
can
actually
use
pages,
which
is
interesting.
Release
in
versioning
is
off.
Let's
turn
it
on
look
at
that
yet,
and
we.
A
Ok,
so
we
have
our
looks
like
a
timeline
of
things
scope,
so
you
can
kind
of
see.
This
is
what
I
think
a
lot
of
folks
when
they
say
I
want
to
see
the
history
of
my
milestone
or,
like
the
story
of
it,
I
think
this
is
in
large
part
poly.
The
experience
that
they're,
referring
to
because
they're
used
to
looking
at
things
in
this
way
where
they
can
kind
of
look
through
like
how
scope
changed
throughout
all
right.
It's
not
bad
I
mean
it
makes
sense.
It's
a
little
noisy
but
well.
B
I
guess
yeah.
My
questions
always
been
like.
How
do
you
combine
this
information
with
your
burn
down
information
into
a
single
view?
No
I
don't
know
what
the
what
that
would
look
like,
but
I'm
only
something
when
I
was
using
JIRA
back
in
the
day
and
it's
kind
of
one
of
those
things
I
was
going
to
say.
Yeah.
A
I,
don't
know
you
can
kind
see
your
scope,
changelog,
which
that's
got
a
nice
see
how
things
evolve,
incomplete
issues,
completed
issues
and
issues
completed
outside
of
Sprint,
so
things
that
weren't
associated
with
Sprint
should
be
kind
of
nice.
I
don't
mind
that
at
all-
and
this
will
be
the
burndown
chart
like
we
have
so
they
have
like
the
burn
down
and
they
have
a
burn
up.
It
shows
changes
and
then
we
have.
We
can
look
at
our
velocity
report.
A
A
Zero,
so
commitment
rush
is
completed.
That's
a
it's
a
nice
way
simple
and
then
your
accumulo
diagram
over
time,
yep,
which
is
kind
of
nice.
So
it's
not
just
one
one
sprint,
but
every
every
time,
I'm,
just
gonna
cool,
I
guess
this
is
the
other
thing
releases.
So
this
is
a
big
big
understanding
for
me.
A
It
could
lab
when
I
realized
that
when
people
are
like
I
want
to
see
releases
they're
talking
about
software
relation
releases,
which
is
versions,
but
it's
they
want
like
a
release
report
like
here
in
JIRA
and
they're,
using
milestones
for
releases
in
many
respects,
and
so
this
is
like
why
there's
good
overlap
with
I
guess
the
release
group
would
think
it
lab
because
they're
working
on
this
similar
type
thing,
but
this
is
not-
has
very
little
to
do.
I
guess
with
planning.
You
know
it's
more
like
what
was
shipped
with
and
begin
a
thing.
Yeah.
A
B
A
A
B
A
Yeah
there
should
be
which
says:
swing
galeb
right
now
you
can
associate
a
release
to
a
milestone,
right,
I'm,
not
sure
I,
don't
think
we
UX
is
there
for
like
doing
it
all
within
they
get
loud.
You
I,
but
with
the
API
I,
think
you
can
do
all
that
stuff,
which
is
kind
of
nice.
A
The
if
you
look
at
in
the
context
of
where
you
look
at
this,
though
cuz
I,
can
click
on
this
and
I
can
just
hop
back
to
my
search
if
I
want
to
like
work
on
this,
so
I
would
think
this
would
just
pop
it
open
and
modal.
Instead
of
doing
that,
but
I
mean
it
still
provides.
Some
nice,
like
I,
don't
have
to
redo
my
search
every
time.
I
go
back
and
wait
for
the
page,
reload
just
kind
of
nice
and
back
to
main
menu.
A
A
A
B
A
A
B
B
A
Yeah,
let's
that's
more.
A
A
B
A
But
it's
for
the
demo
board
and
I.
Don't
know
why
it's
showing
so
like.
You
only
have
one
board
per
project,
there's
a
plan
project
and
then
there's
a
demo
project
mm-hm,
and
this
is
the
board
from
the
demo.
But
it's
showing
it's
not
scoping.
My
it's
like
that
same
problem,
there's
like
bleed
across
the
projects
but
I,
don't
think
they're
supposed
to
be
I
shouldn't,
be
able
to
specify
a
sprint
from
a
different
board
or
a
different
project.
Well,.
B
A
B
I
think
that's
just
probably
like
a
little
interesting,
I'm
gonna
start
the
demo
to
sprint,
because
I
think
that
affects
that
view.
Yeah
did
you
start
it
yeah,
so
you
might
want
to
probably
need
to
refresh
this
oh
yeah.
So
now
I
can
pick
demo,
okay,
hey
back
yet
all
right.
So
we
have
one
flagged
see
I'm,
just
like
a
bunch
of
stuff.
A
B
B
A
B
A
All
right,
I
think
you
know:
we've
had
a
pretty
good
overview.
Okay,
we'll
have
to
go.
Look
at
the
classic,
I
think
so
I
think
that's
what
most
folks
ran
over
all
it
wasn't.
A
horrible
experience,
I
think
there's
some
defects
like
everything
that
worth
cleaning
up
on
their
part,
but
simply
out
of
all
that
the
thing
that
looked
the
most
daunting
from
an
importer
standpoint
for
me
was
the
custom
fields
in
issue
types.
One
thing
that
we
don't
have
anywhere
close
to
supporting.
A
B
A
Yeah
I
think
this
is
the
thing
that
is
the
biggest
challenge
to
get
right,
especially
within
the
context
of
having
lots
of
the
groups
in
projects.
I
think
you
know,
like
I,
think
the
reason
why
JIRA
initially
went
to
create
this
next
gen
is
because
they
realize
how
complex
they
had.
Let
things
get
from
a
configuration
standpoint
classic
and
they're
trying
to
simplify
it,
but
I,
don't
I,
don't
know
it's.
A
This
is
what
I
kind
of
had
envisioned
I
would
like
to
see
happen
with
issues
anyways
is
they
have
no
type,
and
then
they
some
types
you
can
specify
different
workflows,
which
I
don't
see
here.
I'm
sure
you
can
do
that
in
classic,
but
the
simplicity
of
the
custom
fields
is
like
a
nice
nice
thing.
Yeah.
A
And
so
like
right
now
we
have
the
label
bleed,
but
it
would
be
hard
to
build
a
good
experience.
I
mean
it
seems
like
it
would
be
hard
to
create
a
good
experience
from
a
UX
standpoint
like
cuz.
If
you
had
all
these
fields,
how
would
you
build
like
a
good
experience
and
like
searching
and
that
sort
of
thing
you
know
filtering
I,
guess
that's
why
they
eventually
created
jaql
and
all
that
yeah.