►
From YouTube: Plan How To - Confidentiality
Description
Melissa Ushakov walks through how Issue and Epic confidentiality and how you can use them!
A
Hi
y'all
I'm
melissa
ushaka
from
the
plan
stage
and
today
I'm
going
to
walk
you
through
issue
and
epic
confidentiality
and
how
you
can
use
that
in
your
organization,
so
first
to
explain
the
concept
when
an
issue
or
epic
is
marked
as
confidential.
What
happens
is
that
that
work
item
is
now
only
visible
to
members
of
that
group
of
projects
that
have
a
reporter
of
above
or
above
access.
A
A
So
my
main
group
is
melissa,
inc,
that's
the
top-level
group
and
then
I
have
different
organizations
and
portfolios
underneath
with
the
very
bottom
being
teams
so
first
to
talk
through
issue
confidentiality
and
how
you
can
use.
That
is
that
many
times
what
we'll
see
is
that
there
are
groups
within
the
same
organization
that
work
together
most
of
the
time.
So
you
want
an
easy
way
to
give
somebody
access
to
most
of
your
backlog,
but
not
all,
and
you
can
use
that
with
confidential
issues.
A
So
what
you
can
do
is
that
let's
say
that
the
reporting
and
analytics
and
notifications
group
are
work
together.
Often
you
can
add
the
engineering
manager
as
an
example
from
the
reporting
and
analytics
group
as
a
guest
to
the
notifications
team
and
now
they'll
be
able
to
see
everything
except
confidential
issues,
and
you
can
make
those
confidential
issues.
You
can
use
it
for
say
the
stealth
project
that
your
group
is
working
on,
that
only
your
group
members
can
see
so
that
way
that
em
can
see
most
of
the
backlog,
but
not
all
at
gitlab.
A
A
Now
I'm
going
to
talk
through
epics
and
epic
confidentiality,
because
that
one
is
a
little
bit
different.
So,
as
you
know,
epics
is
exists
at
the
group
level
and
permissions
for
them
cascade
down.
So
what
that
means
is
that
whoever
is
a
member
of
a
group
or
project
beneath
that
epic
can
see
it
as
an
example.
The
epics
that
exist
at
the
melissa
inc
level
are
visible
by
members
of
this
entire
subgroups
and
projects,
because,
basically,
each
of
these
teams
is
attached.
A
What
that
does
in
epics
is
that
if
an
epic
is
marked
as
confidential,
you
have
to
be
a
member
of
the
group
where
that
epic
lives
with
at
least
reporter
and
above
so
as
an
example.
If
I
create
a
confidential
epic
at
the
portfolio
shared
services
level,
the
teams
underneath
won't
be
able
to
see
it
only
direct
members
of
the
portfolio
shared
services
group
or
any
members
that
have
cascaded
from
from
groups
above.
A
So
this
feature
is
useful
in
a
couple
different
scenarios,
one
let's
say
that
there's
a
stealth
project
that
only
certain
people
should
have
access
to.
You
can
use
confidential
epics
there
or
many
times
when
epics
are
still
going
through
the
vetting
process
or
scoping
process.
You
don't
necessarily
want
your
team
to
be
distracted
by
these
epics
until
they
reach
a
certain
level
of
review
and
and
they
can
be
made
public.
A
A
One
thing
to
remember
about
epics
being
confidential
is
that
when
epic
is
marked
as
confidential,
then
all
of
the
issues
underneath
have
to
be
marked
confidential
as
well.
So
that's
something
to
keep
in
mind
before
implementing
the
solution,
so
that
is
all
I
had
today
for
you
around
confidentiality
thanks
for
watching,
and
hopefully
this
video
was
useful.