►
Description
Often we call things "known issues" or "limitations" when really they are just how the product works in the current release. You can sometimes call these things prerequisites instead.
This short video shows you how to "make lemons into lemonade."
https://docs.gitlab.com/ee/development/documentation/topic_types/reference.html#reference-topic-titles
A
This
is
a
quick
video
about
turning
lemons
into
lemonade,
so
you
might
have
seen
pages
that
have
a
topic
called
limitations
and
sometimes
we'll
even
just
call
them
known
issues
but
I'd
like
you
to
just
look
at
those
things
as
if
maybe
they're,
actually
just
the
way
that
the
product
is
functioning.
If
they're
the
way
that
the
product
is
functioning,
you
might
be
able
to
incorporate
them
in
other
ways.
So
I
just
wanted
to
give
an
example.
Just
to
get
your
mind
thinking
about
it.
A
So
one
of
the
limitations
is:
oh,
you
can't
do
this
thing.
You
can't
upload
a
widget
if
you're,
not
a
maintainer,
if
your
widget
is
too
big
you're
going
to
have
problems
and
if
it's
a
Thursday
and
it's
raining,
there's
no
way
it's
going
to
happen.
So
that
might
look
like
a
limited,
a
list
of
limitations
to
you
and
you
might
think
it's
just
the
way
that
we
should
present
it,
but
actually
we
can
take
those
things
and
make
them
into
prerequisites.
A
So,
instead
of
saying
it's
going
to
fail,
if
it's
too
big
just
say,
oh,
it
has
to
be
smaller
than
this
yeah.
It
has
to
be
any
day
besides
Thursday
and
the
sun
must
be
shining,
or
at
least
you
have
to
be
thinking
good
thoughts.
So
anytime,
you
see
limitations
just
think
about
how
they
might
be
prerequisites
or
just
things
that
need
to
exist.
In
order
for
you
to
be
able
to
do
a
task.