►
A
Hello,
my
name
is
tom,
and
this
is
a
quick
demo
on
creating
a
new
project
in
a
new
issue
in
in
a
new
shad.
So
this
time
around,
this
is
implemented
in
a
much
more
generic
way
such
that
we
can
rely
on
the
project
or
group
full
path,
and
you
will
find
the
correct
chart
using
around
action.
I've
also
implemented
a
generic
module
to
to
set
and
read
the
top
level,
namespace
shard
and
also
the
top
level
namespace
id
and
I've
also
for
observability
to
make
it
easier
to
debug.
A
I've
also
shown
the
default
the
context
chart
on
the
develop
performance
bar
as
well,
so
you
can
see
here
for
the
loss
and
found
this
is
indeed
created
in
the
short
one
chart.
So
if
we
go
to
another
group
that
is
created
in
the
default
chart,
which
you
should
say
default,
so
let's
create
a
new
project
and
for
this
loss
and
found
group.
A
A
And
also
I've
gone
ahead
and
edit
issue
assignments
at
a
moment
we
can
only
assign
yourself,
unfortunately,
the
assignment
for
other
issues.
Assignees
doesn't
work,
probably
because
this
is
not
using
full
path,
as
in
the
url
to
request,
it
doesn't
have
the
group
path,
so
it
doesn't
know
to
find
the
correct
assignees
or
the
group
members
for
that.
A
So
the
only
other
thing
that
was
not
implemented
is
stability
to
comment
on
on
this
issue
in
a
new
chart.
Unfortunately,
this
is
a
bit
harder
to
implement
because
the
nodes
table
is
polymorphic
so
because
we
can't
shout
much
question,
for
example,
and
notes
is
also
on
merge
requests.
We
can't
really
shut
the
notes
table
yet.
A
Otherwise
it
will
otherwise
it
will
attempt
to
find
root
ancestor
in
a
default
sha
which
we
know
doesn't
work.
So
after
we
set
the
top-level
line
space,
then
we
come
back
to
the
application
controller,
which
has
a
round
action.
Shutter
read
and
if
we
read
the
top-level
chart
and
then
we
that's
how
we
we
know
to
use
the
right
shard
for
that
one
and
interestingly,
we
can
also
use
shadow
reason
and
just
assume
shadow
rate,
but
unfortunately,
there's
places
where
even
on
get
requests.
We
write
to
the
database.