►
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
To
be
an
overview
of
the
troubleshooting
process
for
I
guess
this
issue
regarding
license
scanning
results
not
showing
up
in
the
merger
quest
widget
for
a
particular
project
owner
turns
out.
The
problem
has
to
deal
with
permissions
and
access
to
the
data.
That's
needed
from
the
merge
request,
widget,
because
then
the
merge
request,
widget
populates
data,
sometimes
from
data
that's
generated
from
the
CI
jobs.
A
A
What
the
current
bug
bit
or
behavior
is
and
what
the
expected
behavior
is
so
after
glancing
that
I
usually
then
take
a
quick
look
at
the
additional
discussion
to
see
if
there's
any
other
relevant
data
just
because
sometimes
the
discussions
don't
have
don't
make
their
way
back
to
the
issue
description.
A
So
we
see
here
that
MOU
added
some
additional
screenshots.
This
is
also
assigned
to
labels,
P
1
and
s
2,
so
P,
1
I.
It
takes
the
priority
in
terms
of
how
urgent
it
is
to
fix,
and
then
the
severity
relates
to
how
bad
it's
broken.
I
believe.
So
in
this
case,
it's
the
highest
priority,
because
it's
SLA
for
bugs
and
severity
issues
needs
to
be
fixed
as
soon
as
possible.
A
How
bad
in
terms
of
how
bad
it's
broken,
the
feature
just
doesn't
work
and
the
workaround
is
too
complex
and
unacceptable,
which,
after
my
analysis,
I
agree
with,
but
let's
kind
of
recap
real
quickly.
What
the
actual
issue
is,
so
you
have
a
project
owned
by
user
1
user
2
Forte's.
That
project
has
their
own
fork
of
the
project,
make
some
changes
and
then
put
some
earth
request
from
their
fork
up
to
a
branch.
A
In
this
case
probably
master
of
the
originating
project
and
the
user
to
which
is
the
user
with
the
fork,
can
now
see
the
merge
request.
Load
correctly,
merge
request,
widget
load
correctly
in
context
from
from
the
parent
project,
but
the
are
I
guess
the
code
owner
of
the
original
project
can't
see
any
of
that.
A
A
I
wanted
to
check
out.
So
the
first
thing
we
did
essentially
was
go
through
the
reproduction
step.
So
we'll
do
that
now,
so
we
have
two
accounts
logged
in
one
for
this
repo.
This
is
my
local
dev.
Environment
is
jabber
fest,
which
bones
and
created
this
auto
remediation
repo,
and
we
have
this
Colombian
prod
user,
which
is
a
member
of
that
project
that
shouldn't
matter.
But
at
least
you
have
access
to
fork
that
repo,
so
first
thing
we'll
do
is
work
that
repo.
A
A
A
A
A
So
we're
going
from
our
fork
and
master
into
the
upstream
project
and
you
see
Columbian
pride,
slash
yarn
remediation,
sorry
fork.
Auto
remediation
group
is
the
upstream
project,
so
now
you
will
create
them
retro
crust.
Now.
The
key
thing
here
to
realize
is
that
this
merger
quest
is
going
to
go
up
and
show
up
against
the
obstruent
project,
not
from
our
Fork,
because
that's
where
it's
going
to
so
I'm
just
gonna
create
this
so
are
submitting
over
emerge
arrest
up
to
the
upstream
project.
A
And
I'll
go
into
detail
why
that
is
so,
you
see
it's
not
loading
and
we
do
get
counsel
errors
right
which
might
make
you
think.
Okay,
it's
a
friend
an
issue,
but
if
we're
actually
thinking
about
permissions
issues,
the
front-end
shouldn't
matter,
because
the
front-end
was
working
in
context
of
running
putting
up
a
more
against
a
project
II
owner.
So
so
with
that
said
now
he
navigate
back
to
the
fork.
One
thing
to
keep
in
mind
is
that,
as
I
mentioned
earlier,
the
data
from
the
merge
request
widget
consumes
data
from
the
job
pipe.
A
A
They
want
tweaking
a
repeater
merge
request
across
repos,
but
this
is
just
to
showcase
that
this
isn't
leave
the
problem
and
warrants
further
back
end
in
the
investigation,
so
we're
gonna
make
them
at
least
a
developer,
because
users
that
are
reporters
developers
and
maintain
errs,
have
access
to
the
CI
jobs
to
view
and
to
open,
merge
request.
So
every
changes
from
the
developer.
Now,
if
we
reload
the
page
and
again,
this
is
this-
is
showing
the
merge
request
from
the
perspective
of
the
original
code
owner
for
the
project.
A
A
The
link
we
made
so
much
functions
about
generating
the
link
because
it's
taking
the
job
or
else
of
a
CI
pipeline
ID,
so
the
pipeline
ID
was
99
and
appending
it
to
the
current
project.
That
URL
does
not
exist
in
this
case,
but
it
does
exist
if
we
change
this
to
there's
a
Colombian
pride
I
believe,
which
was
the
essentially
the
context
that
this
job
was
run
in
so
I'll
open
up.
I
guess,
I'll,
add
to
the
issue
that
we
have
that
additional
detail,
but
you
could
see
that
it's
the
that
the
merge
request.
A
Widget
relies
on
you
having
permission
to
the
CI
doubts
that
run,
so
we
really
need
to
reconsider
and
do
a
full
audit
of
all
the
merge
request.
Widget
data
that
gets
pulled
in
that
relies
on
CI
pipeline
results,
which
is
I,
don't
think
they
work
entirely
in
context
of
merger
quests
foot
up
against
upstream
repo.
So
as
a
result
of
that
investigation,
I
outline
the.
A
A
Here
it
is
which
basically
covers
exactly
what
I
just
said
in
this
video.
Hopefully
it
was
enough
to
give
you
an
idea
of
like
the
debugging
process,
but
because
there
is
nothing
to
do
from
the
front-end
that
once
we
fix
the
backend
logic,
this
the
UI
should
just
work,
I
guess,
with
the
exception
of
the
links
there,
the
link
problem
that
we
incur
encountered
in
this
video,
which
I'll
add
as
a
note
here,
but
we
may
tackle
that
as
part
of
this
issue
as
well.
So
that's
pretty
much.
It.