►
From YouTube: GitLab 12.10 Introduces Requirements Management!
Description
GitLab 12.10 introduces the ability to manage requirements! This video demonstrates our MVC for this feature.
if there are any questions or comments, please feel free to comment on our open issues / epics, or create a feature request.
Epic for Requirements Management MVC: https://gitlab.com/groups/gitlab-org/-/epics/1696
A
Do
everyone
and
welcome
I'm
here
to
demonstrate
a
new
feature
released
and
get
lab
12.10
for
requirements
management?
It's
a
feature,
we're
super
excited
about.
I
know
a
lot
of
people
have
requested
being
able
to
manage
your
requirements
from
within
get
lab
and
that
it's
now
a
released
feature.
If
you
look
at
this
demonstration
project
you'll
see
along
the
left-hand
navigation
bar
there's
an
entry
for
requirements
and
if
we
click
on
that
it
brings
us
to
a
list
of
requirements.
Now
this
list
is
very
similar
to
things
we
see
elsewhere
in
the
product.
A
We
see
this
in
issues
and
merge
requests,
and
here
you'll
see
your
list
of
requirements
each
with
a
unique
identifier,
so
requirement
can
be
in
one
of
two
states.
It
can
be
open
or
it
can
be
archived,
and
this
allows
us
to
filter
these
buttons
along
the
top.
Allow
us
to
filter
on
the
open
requirements,
or
in
this
case
the
archived
requirements.
A
You'll
also
see
that
there's
the
ability
to
see
both
archived
and
open
requirements.
In
case
you
want
to
view
all
the
requirements
in
a
project
going
back
to
archive
or
open
requirements,
you'll
see
that
each
requirement
is
presented
with
when
it
was
created
by
who
was
created
and
when
it
was
last
updated
now
to
add
any
requirement.
You
can
click
on
the
new
requirement
button,
and
this
will
bring
up
a
box
where
you
can
type
in
whatever
requirement
text.
You
need.
A
Clicking
on
the
create
requirement
will
give
this
requirement
a
unique
identifier,
and
it
will
say
it's
created
just
now
and
it
was
updated
just
now.
So
if
we
look
at
a
requirement
that
was
updated
seven
minutes
ago-
and
we
want
to
make
some
changes
to
this-
we
can
click
on
the
edit
button
and
we'll
bring
back
our
text
box
where
we
can
add
additional
information.
A
We
can
then
save
these
changes.
If
we
decide
that
a
requirement
is
no
longer
applicable
to
development,
we
generally
don't
want
to
delete
it,
because
requirements
are
considered
a
durable
artifact
throughout
the
lifecycle
of
a
project.
However,
we
may
want
to
archive
it
so
that
it's
no
longer
in
the
list
of
active
requirements
doing
so
it's
as
simple
as
clicking
on
the
archive
button.
You'll
see
that
the
counselor
slides.
Now
we
have
three
open
requirements
and
two
archived
requirements.
A
If
we
accidentally
archive
a
requirement,
we
can
easily
go
back
over
here
and
reopen
these
requirements
by
simply
clicking
on
the
reopen
button
notice
that
you
cannot
edit
archived
requirements
because
they're
durable.
We
want
them
to
maintain
their
state
for
the
lifecycle
of
the
project
as
a
history
of
where
the
requirements
were,
however,
to
bring
it
back,
clicking
reopen,
will
move
it
back
to
the
open
requirements,
and
you
can
see
it
comes
back.
A
You'll
also
note
that
all
requirements
have
unique
identifier
for
some
regulated
industries,
and
other
industries
is
required
to
have
requirements
with
unique
identifiers
in
order
to
discuss
them
or
talk
amongst
your
team.
So
you
can
reference
them
by
their
unique
identifier.
This
is
a
brand
new
feature
and
we're
very
excited
to
launch
this.
If
there
are
any
questions,
please
don't
hesitate
to
contact
us
as
we
implement
further
revisions
of
this
we'd
love
to
hear
your
feedback
and
if
there's
anything
else,
we
can
do
to
make
your
life
easier
with
regards
to
requirements,
please
reach
out.