►
From YouTube: Environments Dashboard Redesign #1
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
B
C
B
C
B
An
additional
week
there
was
a
question:
are
low-hanging
fruits
I'm,
just
adding
an
additional
issue
that
I
think
would
be
simple
and
then
I
can
go
over.
Why
I
think
that
would
be
simple.
So
that's
the
first
issue
in
the
epic
we
want
to
discuss
a
half
of
this
I
think
that
we
can
just
provide
some
sort
of
notification
right
on
right
on
the
modal
when
deleting
a
project.
I
think
that
this
one
was
is
pretty
straightforward.
C
Layout
I
must
have
liked
some
prototypes
of
how
do
you
I
should
look
like
the
model
in
particular,
and
it's
what
it's
a
raised
attention
that
Primus
dashboard
was
a
copy
of
sorry,
so
many
words
of
the
operations
dashboards,
and
now
they
completely
changed
how
to
add
projects.
It's
not
a
model,
any
words
in
line.
C
B
C
B
Just
loading
up
the
security
dashboard
here,
okay,
yeah
yep
I,
see
what
you're
saying
now:
yeah
that's
different,
so
the
environments
dashboard
change
you
mentioned
I,
don't
think
that's
on
master.
Yet
this
looks
different
than
what
I
saw
in
the
environments
dashboard,
but
it
looks
essentially
the
same.
It's
just
not
in
a
modal.
B
B
Dashboard
working
like
the
security
dashboard,
the
only
thing
that
looks
immediately
different
to
me
is
that
the
security
dashboard
is
using
graph,
QL
and
I.
Don't
think
our
environments,
dashboard
is
I,
think
it's
still
using
our
arrest.
Api
I,
don't
know
how
much
of
an
issue
that
would
be,
though,
because
that's
just
data
fetching,
so
the
presentation
layer
of
the
dashboard
should
be.
C
B
A
C
The
CIT
dashboard
and
when
I
look
at
all
the
dashboards
that
we
have
a
prosecute
lab,
it's
difficult
to
find
the
source
of
truth
or
the
user
experience,
there's
some
dashboard
that
they
have
a
complete
different.
Looking
for
you,
that's
a
or
I
know
you
and
I've
done
this
in
different
way.
You
it's
just
very
different
visually
and
also
the
interaction
and
looking
at
the
prototype
for
the
the
CIC
dashboard.
I.
B
A
Question
what
are
with
the
epoch?
What
is
our
our
goal?
Our
end
goal
because
I
see
all
of
the
link
tissues
with
some
mostly
minor.
It
sounds
like
adjustments
in
functionality,
with
the
exception
of
meaty
and
displaying
some
group
level
stuff,
but
to
your
point,
I,
don't
see
any
like
designs
or
or
end
goal,
which
I
can
just
what
Jake
brought
up
originally
so
I
feel
like
to
discuss
the.
A
How
is
a
little
hard,
because
we're
just
kind
of
seeing
these
little
incremental
improvements
beside
make
sense,
I'd
love
to
see
where
we're
trying
to
get
to,
and
then
we
can
have
I
think
it
would
really
feel
the
discussion
on
on
how
we
can
get
there
more
incrementally
and
first,
it's
just
a
few
of
these
little
fixes,
because
what
what
I
don't
want
to
happen?
Is
we
go
through
and
make
all
these
incremental
fixes?
And
then
we
come
in
with
a
design
and
have
to
go
back
and
rework
all
of
this
right.
So
you.
C
C
This
is
really
a
redesigning
and
I
think
this
needs
to
go
through
the
workflow
design
phase,
and
then
we
look
like
what
you're
saying
it's
more
holistically
and
perhaps
even
break
it
down
into
all
these
fixes
that
are
listed
here,
but
I
also
find
it
very
interesting
because
there
are
some
logging
froze
there,
some
things
that
we
can
just
discuss.
Not,
for
example,
that's
not
just,
let's
use
the
mode
that
we
have
now
in
implement
or
use
a
component
later
and.
A
B
We
want
to
use
this
meeting
to
to
fuel
the
design
ideas
for
some
of
these,
like
theme
I'm.
So
like
this
second
issue
and
yet
because
the
environments
dashboard
improved
the
add
project
modal.
For
that
I
think
that
we
can.
We
can
pre-populate
that
away.
We
kind
of
pre
populate
the
milestone
selector
with
milestone,
so
the
user
doesn't
have
to
think
about
what
milestone
is
in
their
head.
C
Especially
that
these
are
like
fixes
to
existing.
Oh,
yes,
there's
an
all
existing
issues,
or
you
know
he
has
been
to
the
feature,
but
we
also
have,
for
example,
show
as
an
issue
that
Jackie
law
to
show
a
heat
map
in
environments
dashboard
right,
so
that's
adds
more
complexity
in
like
what
Jake
was
saying,
there's
no
way
to
easily
fascinate
to
the
more
complexity
we
are
to
this
thing,
bigger
monster
will
get
in
additionally,
Jackie
might
had
a
chat
I.
Think
we
discussed.
C
Isn't
a
team
make
a
couple
of
times
or
mentioned
to
instead
of
just
iterative,
the
environment
dashboard
make
improve
the
connection
between
the
environments
list
view
that
we
have
in
a
concise
in
the
environment,
operational
environments
with
the
apartments
dashboards,
so
in
a
way,
merge
them
to
create
this
unified
user
experience,
where
yeah
users
will
be
able
to
see
everything
related
to
environments
and
deployments,
but
then
managers
and
people
that
need
this
new
analytics
view.
They
would
also
get
that
in
a
single
place.
C
D
B
C
C
B
C
Yeah,
so
maybe
I'm
thinking
for
us
to
maybe
idh
on
the
prototype
and
also
look
at
what
Jackie
added
there.
For
example,
we
know
the
pagination
is
coming
and
how
that
would
impact
or
how
that
would
look
like
notifications,
etc.
I
know
that
it's
not
ideal
not
or
that,
but
maybe
we
can
play
around
living.
Do
you
have
access
to
dissing?
Can
you
I,
don't
know,
add
notes
and
acting
to
this
file?
Cuz
I
see
anomalous
here,
yeah.
A
C
That
we
want
to
make
some
fixes
any
programs
to
what
be
Marvin's
dashboard
offers
now
like
this
experience-
and
this
is
actually
dashboard-
is
something
DIF.
It's
really
that
we
want
that's
gonna
leave
at
the
group
level
when
it's
gonna
show
metrics
waited
to
your
release
and
everything
else,
and
that
will
connect
you
to
the
environments
dashboards.
So
when
you
see
their
last
five
deployments,
you
click
you
go
to
this
page,
for
example,
and
I.
Think
the
problem
of
the
inconsistent
user
experience
is
something
that
we
can
solve
in
the
future.
C
A
Yeah
yeah
I
guess
that's
what
I
was
trying
to
reconcile
in
my
head
and
maybe
maybe
Jackie
can
add
some
clarity.
There
is
that,
where
I'm
trying
to
see
the
difference
between
the
environments,
dashboard
redesign
and
just
implementing
some
UX
that
type
issues
right,
because
that
sounds
more
like
what
we
have
so
far
and
that's
fine.
If
that's
where
we
want
to
start.
A
C
C
Since
she
asked
us
to
talk
about
how
to
implement
these
improvements,
I
think
maybe
should
go
back
to
the
directional
yeah,
how
to
make
those
small
faces
that
might
need
some
UI
or
UX
polishing
or
fix
or
whatever.
But
then
we
focus
on
the
bigger
picture
later
on
yeah
make
sense.
We
had
some
fun
this.
A
For
the
modal
and
Hansen's,
so
you
you
pointed
to
some
other
modal's
that
we
would
kind
of
use
as
a
guideline
there.
So
that's
really
helpful
Jake.
Looking
at
this
list,
where
do
you
feel
like
you
would
need
the
most
input
from
hi
Anna?
That
might
be
a
good
place
to
start
flushing
things
out,
for
example,
indicating
to
users
removing
adding
a
project
project
from
dashboard,
for
you
affects
all
others.
Is
that
something
we
need
the
most
input,
because
that
might
be
a
good
place
to
start
brainstorming.
B
I
think
that
I
think
that
that's
workable
without
a
ton
of
input,
one
I
mean
I,
definitely
would
definitely
love
to
have
some
more
direction
on
exactly
what
sort
of
notification
to
use
or
what
sort
of
UI
text
to
use,
but
other
than
that
I.
Don't
think
it
would
require
time
to
put
one
thing
for
sure
that
I
would
would
love
to
discuss
further
in
terms
of
in
terms
of
design
is
add,
custom
version
to
environment
in
stash
board.
C
C
B
B
Yes,
I
remember
my
questions
about
this
now,
so
one
of
the
questions
were
the
pipeline.
That's
visible
right
at
the
very
top
of
the
card
is
that
indicator
of
the
latest
pipeline
for
an
environment
that
starts
with
that
name,
because
this
is
talking
about
grouped
environment.
So,
for
example,
there's
the
development
group
and
there's
346
environments
in
a
development
group
does
that
pipeline
represent
the
latest
pipeline
of
a
job
run
in
one
of
this
sub
environments
of
development,
yeah.
C
That
was
the
that
wasn't
the
initial
description,
but
to
say
that
when
we
work
on
this
thing
making
over
a
year
ago,
we
didn't
really
dive
in
through
these
technicalities,
and
the
details
was
just
like
the
station
history.
Life
just
show
the
latest
by
plying
that
run,
that
run
from
this
group
and
then
do
the
latest
deployment
from
that
pipeline,
and
then
maybe
you
why
I
think
this
prototype,
you
can
see.
That's
yeah.
C
Deployments
for
that
in
higher
means-
or
there
probably
be
a
group
environment
cards,
but
this
one-
you
only
have
one
I've.
What
I
remember
then
also
looking
at
it
see
why
I
don't
think.
That's
very
intuitive
and
I
think
that
users
who
want
to
see
more
details
or
go
somewhere
from
this
view.
But
yes,.
C
B
There's
so
it
if
development
is
like
this
top
level,
environment
group
and
there's
sub
environments
under
development,
is
there
a
way
from
this
mu
to
get
to
those?
Some
environments
is
like
clicking
that
card
open
up
two
additional
environments:
okay,.
C
A
C
C
C
C
C
This
one
we
have
one
like
investigate
job
to
be
done.
I
think
this
is
more
something
for
for
Jackie
and
I
differences
between
operations
and
environments,
dashboard,
there's
now
they're
connected.
That's.
Why
I
have
the
first
issue
that
twenty-eight
users,
that,
when
you
remove
something
from
the
environment
dashboard
it
also
removing
from
the
operations
dashboard
yeah,
we
became
partner.
B
They're
they're
also
tied
together
and
it
back
end
as
well
as
it's
not
just
like
cosmetically
on
the
front
end.
It's
they're,
sharing
information.
Everything
from
the
environments.
Dashboard
is
just
like
fed
from
all
the
operations
components
on
the
on
the
backend
as
well.
So
there's
a
lot
of
stuff
tied
together.
There.
B
B
Just
to
go
back
to
this
spec
one
real
fast
I,
don't
wanna
linger
on
it
too
much,
but
looking
at
the
just
the
proposal,
it's
already
assuming
that
context
of
20
environments
for
iterations,
so
there's
yeah,
we're
definitely
gonna
need
someone
from
probably
Shawn
someone
who's
gonna,
have
the
context
of
imagination
and
to
do
this,
because
when
we
start
adding
pagination
to
the
dashboards,
we're
gonna
have
to
be
changing
our
test
to
accommodate.
For
that.
C
B
C
B
C
B
C
I
have
an
issue
actually
to,
in
my
backlog,
to
look
at
the
apartment
that
word
redesign
in
general,
but
maybe
we
should
scatter
like
a
session
to
just
ID
aides.
On
top
of
this,
because
I
feel
like
I
wanna,
do
just
work
on
UI
proposals
or
my
understanding
of
it.
Everybody
needs
you
to
like
help
me
with
this
yeah,
just
pointing
out
what
is
a
cosmetic
change
and
change,
and
what
it's
not
a
change
right.
B
D
C
To
the
discussion
of
the
National
ensign
of
departments
dashboard
way,
because
this
epic
lists
feature
enhancements
and
redesigns
and
then
Nicole
was
here
was
this
question
round?
Okay?
Is
it
a
redesign
of
the
dashboard?
Are
we
just
fixing
features
that?
Could
you
know
just
enhancing
things
and
I
think
the
last
thing
I
was
saying
to
Jake
was
about
scheduling
some
time
or
to
look
at
this
holistic
improvement
to
the
environment,
dashboards
with
Haiti
and
together
to
get
more
context,
because
those.
A
D
C
Bezel,
read
doesn't
really
belong
to
the
best
work
family
to
make
it
live
family
right
and
we're
talking
about
pagination,
in
my
opinion,
have
your
presentation
that
card
view
is
just
ought
in
the
way
that
that
the
environments
dashboards
is
displayed
now
it
doesn't
really
give
a
lot
of
flexibility
to
play
around
when
it's
in
add
more
functionalities.
On
top
of
it,
so
I
think
you
would
be
more
into
fixing
some
of
this.
The
issues
that
we
know
how
to
fix,
but
then,
looking
to
the
future,
all.
D
So
just
lists
out
all
the
environments
that
are
in
your
groups
and
projects
like
instant
level
list.
I
guess
is
what
we're
going
to
be
looking
at
and
then
what
will
the
cars?
Is?
We,
your
selected
projects
and
environments?
We
wouldn't
touch
the
pagination
of
the
cards
if
you
feel,
like
that's
a
weird
experience.
I
mean
I.
D
Have
this
issue
out
there
right
now
talking
about
a
heat
map,
a
static
heat
map
of
the
status
of
your
environments,
because
the
the
problem
that
people
are
trying
to
solve
when
they
go
to
that
dashboard
is
what's
the
status
of
my
currently
deployed
code
right,
so
they're
wanting
to
see
the
latest
pipeline.
They
want
to
see
if
their
environments
are
alive
and
then
triage
any
issues
from
their
environment
status
right.
C
B
D
B
D
D
D
B
Right
I
think
right
now
we
equally
sounds
good.
If
I,
you
know,
if
we
start
to
feel
it,
that's
too
frequent.
We
can,
we
can
move
it
out
or
we
can
do
the
other
way
around
for
you
too,
if
you
feel,
if
you
feel
by
weeklies
good
at
first
and
if
you
feel
we
need
more
frequently
but
weekly
works.
Fine
for
me,
okay,.
D
So
I
think
the
action
items
out
of
this
meeting
will
set
it
at
weekly
at
first
until
we
get
our
grasp
on
how
we
want
to
tackle
this
combination
of
UX
debt
and
tech
debt
fixes
at
the
environments
dashboard
with
ik
flirting
with
this
redesign
concept,
once
we
figure
out
which
direction
we
want
to
go,
maybe
we
can
make
it
longer
and
have
more
async
tactical
discussions,
I!
Think
right
now,
it's
like
we
have
a
big
hairy
problem
in
front
of
us
that
people
aren't
solved
so
I.
Think
that's
perfect,
I!
D
Kind
of
poke
at
some
of
the
gaps
that
you're
seeing
and
if
there's
a
lack
of
a
why
around,
why
we're
doing
anything
and
then
we'll
meet
up
next
week
and
hi
on
and
I
have
our
one-on-one
this
week,
we'll
talk
a
little
bit
about
the
CI
CD
director,
dashboard
and
where
that
should
live.
Because
right
now
we
have
this
idea
of
combining
all
of
it
together
and
that
might
be
might
be
wrong
after
you
kind
of
dig
into
some
of
the
stuff
that
we
currently
have
in
the
epics.
C
C
The
changes
that
are
listening,
this
epic
for
the
environments
dashboard,
but
because
it's
attached
to
the
operation,
dashboards,
the
dashboard
and
in
that
beauty,
experience
already
changed.
So
we
quickly
discussed
this
was
just
implementing
the
change
in
the
UI
or
enjoin'd
interaction
assets
and
then,
once
the
operations
Ashworth,
it's
a
big
most
people.
We
can
reuse
some
components
and
think
on
this
differences
during
a
bigger
redesign.
B
Coupled
in
the
back
end,
so
the
from
the
Ruby
on
Rails
side
of
things,
all
in
all
the
information
about
the
environments
comes
from
the
operations
controller
on
the
server,
so
I
think
that's
might.
That
might
be
why
they're
coupled
together,
but
that's
I,
mean
we
can
break
that
all
apart
on
the
on
the
front
end.
So
from
the
users
point
of
view,
it
can
be
completely
different.
Yeah.
D
Like
the
operator
persona
and
the
release
manager,
persona
are
different
right.
Okay,
we're
two
minutes
over
time.
Sorry
I'll
I'll
go
ahead
and
set
this
meeting
to
be
recurring.
Is
this
timeslot
good
for
y'all
yeah?
Okay?
Generally,
it's
good
for
me.
I
just
got
pulled
in
last
one
thank
you
I'll
go
ahead
and
send
it
by
yeah.