►
From YouTube: GitLab 13.6 Kickoff - Create:Knowledge
Description
Issues mentioned:
- Design Management notifications should match email notifications: https://gitlab.com/gitlab-org/gitlab/-/issues/217095
- Designs to have iids scoped to Project: https://gitlab.com/gitlab-org/gitlab/-/issues/217095
A
A
We
plan
to
continue
to
iterate
on
those
from
13
6
and
beyond,
and
we're
looking
forward
to
our
customers
feedback
within
the
next
few
releases
and
to
keep
bringing
the
group
level
wiki
into
parity
with
project
level
wiki,
but
we
don't
have
any
of
those
marked
for
direction
in
this
release.
However,
I
just
wanted
to
mention
that
we
know
it's
important
and
we
are
going
to
be
prioritizing
a
lot
of
the
mvc2
group
level.
Wiki
issues.
A
So
for
this
release,
we've
got
two
direction
items
both
in
design
management
and
we'll
go
through
those
right
now.
So
the
first
one
is
an
important
upgrade
to
how
design
management
management
notifications
go
out
via
email.
A
A
This
is
really
important
as
we
move
towards
being
viable.
We
want
every
part
of
designs
to
work
like
other
objects
in
gitlab.
So
there's
going
to
be
a
theme
that
we
keep
upgrading,
it's
not
that
exciting
of
a
thing,
but
it's
very
important
to
the
user
experience
and
that
they
could
trust
that
the
notifications
are
going
to
come
to
them.
A
So
that's
the
first
one.
The
next
one
is
having
the
design.
I
designs
get
their
own
eye
ids,
which
is
really
critical
to
some
big
architecture.
Changes
that
we
need
to
make
in
order
to
move
designs
to
more
places,
so
right
now
a
design
lives
on
an
issue.
It
has
a
url,
a
file
name
in
the
url
that
doesn't
scale.
We
can't
use
the
id
in
other
places.
We
can't
link
to
that
object,
and
so
the
first
step
that
we're
doing
is
giving
each
design
its
own
iid.
A
A
We
could
take
that
unique
design
itself
then,
and
have
it
show
up
in
other
places
like
on
imr's
or
epics
or
at
the
project
level.
So
it's
going
to
be
really
cool.
What
we
can
do
with
this-
and
this
is
just
the
first
step.