►
From YouTube: Ecosystem Team Triage Process - 2021-01-11
Description
Lukas and Matt walk through the weekly triage process for the Create:Ecosystem team
A
A
We
cleared
a
bunch
out
last
week,
but
I
basically
wanted
to
show
matt
how
I
do
triage
and
the
most
important
thing
is
obviously
triage
issue,
and
the
other
thing
that
I
always
keep
handy
is
the
categories
page
for
product,
because
often
enough
issues
end
up
with
us,
because
they're
api
issues,
or
because
we
also
have
now
this
machine
learning
thing
that
you
know
assigns
a
lot
of
issues
to
us.
So
that's
basically
the
stuff
that
I
keep
handy.
A
A
Yeah
here,
because
it's
one
of
ours,
I
would
likely
to
look
for
an
appropriate
epic.
So
this
is
also
something
that
you
might
want
to
have
handy
like
a
list
of
epics.
I
don't
know
if
we
have
like
a
list
of
epics.
You
know
that
is
just
ours,
but
usually
I
just
search
for
them
on
the
spot
so
ecosystem,
and
then
we
probably
can
add
jira
jira
issue
integration.
A
Yeah,
okay,
I'm
just
adding
it
to
this
epic,
because
in
the
worst
case-
and
you
know
my
nice
backlog,
because
it's
not
a
customer
one-
it
doesn't
look
like
that
should
be
good
good
enough.
You
can
check
this
one
and
move
on
to
the
next
okay,
and
these
are
actually
ones
where
you
might
be
able
to
help
me
with,
because
we
ended
up
basically
inheriting
the
the
confluence
stuff
right.
So
when
you
join
the
team,
we
I
I
assume,
I
don't
know
yeah.
C
What
do
you
think
right?
Yeah?
I
think
well
just
some
background
the
so.
Yes,
the
knowledge
team
was
working
on
this
because
they
were
responsible
for
wikis
or
we
were
responsible
for
wikis,
and
so
we
had
ideas
and
thoughts
on
how
the
confluence
integration
would
work.
But
now
the
knowledge
team
doesn't
exist
and
wikis
belong
to
the
editor
team.
A
C
A
I
mean
we
still
should
validate
whether
this
is
you
know,
because
it's
like
cross
promotion,
whatever
right,
I
will
just
move
it
to
milestone
backlog.
It's
you
know,
appropriate,
appropriate
milestone
is
probably
the
same
for
this
one
right,
yeah
right
I
mean
I
pin
pink
patrick
on
on
those,
let's
just
move
them
to
the
backlog
and
just
call
it
a
day.
A
Oh,
I
actually
think
I
just
look
check
this
one
without
us
looking
at
it
and
I
think
yeah.
This
one
was
where
we
had
a
discussion
last
week
about
the
that
belongs
to
it's
about
a
list
of
open
source
projects.
You
know
basically
a
better
whatever
project
overview
page
on
the
instance.
I
just
moved
it
to
managed
and
grouped
not
owned,
because
yeah
that
product
figured
that
one
out
I
mean
people
discussed
it
and
yeah.
C
A
C
A
A
I,
to
be
honest,
like
I
assume
it's
not
that
big
of
a
deal
to
fix
it,
at
least
from
you
know
that
doesn't
sound
too
hard,
probably
just
like
a
little
configuration
and
we
need
to
correct
the
links
you
know
we
could.
I
don't
know
how
39
looks
otherwise
we
could
give
it
a
low
priority
opportunity
too.
It's
a
customer
issue,
so
we
could
either
go
for
39
or
we
could
go
for
13.
C
Right,
I
I
would
put
it
in
39
for
now
I
think
yeah,
I
think
it's
getting
13
nine
is
getting
fairly
full
just
from
the
stuff
I've
been
putting
in
there
thinking.
So
as
we
do,
the
planning
I'm
sure
we're
gonna
have
to
go
through
and
prioritize.
What's
really
important,
but
at
least
it's
there,
then
we
can.
A
I'm
just
going
to
ping
andy
because
he
created
the
other
issue
right
yeah
and
then
just
my
milestone,
13
nine,
and
that
should
be
it
right.
I
wonder
if
we
do
the
same
thing
off
and
it's
good
that
I
close
the
epics
right
ethics
system
search,
jira,
okay,
this
seems
to
be
the
one
issue
detail
view
issue:
expand
integration
to
support
issues.
Probably
it's
still
this
one
yeah.
So
you
can
just
add
it
to
this.
To
this
epic.
A
A
A
A
C
A
So
apparently,
a
big
customer
has
the
problem
that
you
know
big
customer,
I'm
just
saying
that
all
you
know,
because
they
have
nine
hundred
thousand
issues
in
jira
that
the
that
the
sync
is
being
delayed
via
the
dbcs
connector
and
I'm
just
going
to
ask
kristen,
and
I
don't
think
if
someone
explained
it
because
if
we
have,
we
should
have
the
project
integrations
jira
integration
and
there
is
the
jira
wow.
That's
nice
jira
integration
and
I
hope
we
have
ebcs,
no
obviously
jira.
A
A
B
A
A
A
Yes,
so
let's
see
what
do
we
have
here?
How
are
these
sorted?
So
I
don't
know
if
we
generally
would
do
them
from
top
to
bottom
or
whatever,
but
maybe
we
are
able
to
just
do
them
in
this
call,
and
then
we
don't
have
this
problem
navigating
to
a
non-existent
service
added
url
results
in
a
500
power,
another
game
to
add
an
impression.
This
dollar
is
a
500
error,
rather
than
the
404.
B
A
A
A
A
A
A
B
B
A
A
B
A
A
A
A
A
Ecosystem
created
everything
is
right,
stone
backlog,
I
don't
know,
do
we
have
like
red
mines?
This
thing
we
could
have
a
look
whether
we
have
a
red
mine.
Do
people
still
use
red
mine.
I
assume,
like
it's
open
source
right
so
probably
like,
like
a
few
folks,
are
using
it
for
product
management
but
yeah.
Definitely
one
of
ours.
Let's
just
you
know
check
it.
We
have
a
new
other
meeting
in
four
minutes
right,
yep
yeah.
A
With
these
other
issues,
I
mean
you've
done
it
before
as
well,
and
but
this
is
all
that
there's
to
it,
you
know
I
try
to
make
sure
that
front
and
back
end.
Labels
are
on
that.
The
appropriate
labels
are
on
that
it
might
be
assigned
to
an
epic
one
if
there
is
one
and
otherwise
just
assign
it
to
to
a
different
stage
right.
So
like
this
is
just
just
called
my
fetching
remote
upstream
fade
fatal.
Could
not
break
user
name
run
cd?
You
know
this
sounds
like
one.
That's
not
integrations
this.
A
A
Okay,
I
will
have
a
look
great.
This
was
very
helpful.
Thank
you
yeah.
This
is
just,
and
I
mean
starting
once
we
once
we're
down
here.
I
probably
once
we
we're
down
to
zero
here
should
be
not
not
a
big
e,
because
right,
usually
you
just
get
like
between
three
and
five
a
week
right.
I
think
we
just
need
to
be
prepared
once
I
take
the
second
part
of
my
current
leave.