►
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).
B
So
bear
with
me
I
guess
so,
first
off
like
first
thank
you,
everyone
who
looked
at
it
and
George
for
commanding
in
it.
It's
always
nice
to
have
a
lot
more
eyes
on
on
the
code.
So
you
not
going
like
on
by
yourself
and
just
you're
looking
at
the
right
things
so
yeah
this
is
going
to
be
technical,
but
I
guess
we
can
take
any
other
questions
afterwards,
so
yep.
B
B
The
first
thing
was
I
was
not
sure
how
it
was
really
running
and,
and
where
was
the
parallel
parallelism?
Starting
Uncas
flat
could
have
imported
in
France
a
lot
of
very
small
workers
in
parallel
and,
and
that
depends
a
lot
on
the
resources
that
the
specific
server
or
cluster
has
because
yeah.
It
depends
on
how
many
files
are
allocated
to
these
workers.
B
So
yeah
there
once
this
I
think
what
it
does
is
well
what
it
does
is
actually
start
like
one
single
work:
if
a
worker
pair
single
issue
that
it
imports
and
and
then
after
all
of
the
issues,
are
imported,
what
github
API
offers
you
can
pull
all
of
the
notes
from
the
specific
repository.
So
it
can
start
a
lot
of
the
or
the
same
process
on
every
single
note,
so
yeah
it
just
pulls
all
the
notes
in
them
links
them
to
the
specific
issues
through
a
caching
mechanisms.
B
There
are
some
basic
fields
that
are
pulled
by
K
anytime.
You
query
the
issue
API,
but
their
own
commands
can
be
loaded
or
not
loaded
separately,
so
we
can.
Similarly,
they
get
having
forking
worth
all
of
the
issues
like
that.
We
just
import
every
every
issue,
with
their
descriptions
and
some
of
the
metadata
and
then
have
another
another
stage.
So
to
say
where
we
will
import
notes
and
then
another
stage
where
we
would
import
attachments,
for
instance,
and
some
other
stuff.
B
That
is
strictly
related
you
to
the
issues,
but
we
will
have
to
kind
of
fetch
from
the
same
issues.
Eight
guys
will
have
to
will
get
the
the
issues
first
and
through
the
commands,
and
one
other
like
question
that
I
have
on
the
github
in
the
mediation
is
like.
Why
is
it
not
using
especially
like
on
note?
Why
is
it
not
using
sincerity,
but
it
rather
starts
again
a
single
psychic
work
on
every
single
note
that
it
inserts
so
it
kind
of
inserts.
It
does
a
lot
of
like
to
me.
We
can.
D
C
B
Understand
it
for
four
issues,
because
you
want
to
make
that
tapping,
although
you
can
still
get
the
ideas
from
the
bulkinsert
and
try
and
map
those
to
the
giro
issue,
for
instance,
so
then
you
have
their
meaning
in
the
in
the
cache
and
because,
like
psychic
could
not
guarantee
that
it
will
not.
It
will
not
include
the
same
job
twice.
You
want
to
have
that
in
care.
So
you
don't
free
import',
the
same
issues
to
challenge
or
something
like
that.
B
So
you
want
to
have
that
mapping,
sort
of
and
then
I
guess
that
will
be
another
aspect:
importance
when
you
want
to
to
trigger
the
import
on
the
same
project
for
the
second
time,
for
instance,
to
kind
of
import
again
some
of
the
newer
issues
and
so
on.
So
it's
great
to
have
that
caching
and
that
mapping
so
I
guess
for
the
issues
it
makes
sense,
I!
Think
for
the
market.
We
can
improve
that.
So
sorry
for
thank
you
feeling.
B
Well,
the
beauty
is
single
threaded
there,
but
I
think
the
idea
of
having
this
parallel
stuff,
where
you
can
like
I,
think
I
did
change
the
PLC.
Where,
for
the
commands,
I
do
batches
of
light,
I
do
batches
of
100
issues
and
for
the
for
each
of
this
issue,
I
will
start
a
batch
important
for
the
commands
themselves
and
then
commence
themselves
all
important.
B
It
does
mulk
insert
with
a
lot
of
more
commands.
There
are
some
issues
with
the
jura
rubygem
at
the
moment
that
it
does
not
allow
to
pull
commands
in
pages
like
you,
just
pull
all
of
the
commands
that
from
the
issue
at
once,
so
we'll
have
to
work
on
the
outside
as
well
to
improve
the
DGM
itself
but
yeah.
The
idea
is
like
to
bet
to
bet
it
isn't
in
some
way
and
to
just
do
the
balkans
there's
at
least
on
the
notes.
C
B
C
Just
thinking
this
advanced
stage
worker
that
we
were
discussing
so
if
there's
more
than
one
relation
that
can
be
migrated
apart
from
the
top-level
issues,
then
yes,
we
we.
We
can
reuse
a
lot
of
gift
wrapped
importer
code,
because
if
we,
if
we
just
don't
reuse
any
of
of
github
importer
code,
we
can
still
do
this
with
in
batches
with
job
waiters.
You
know
there
is
a
lot
of
functionality
that
exists
already.
B
B
I
think
is
the
one
one
thing
that
we
can
reuse
because
we
can
and
like
it
will
be
I
think
it
will
be
good
to
do
it
in
stages.
Even
even
even
though
notes
are
strictly
related
to
the
issue,
and
you
don't
have
to
pull
the
issues
once
again
to
do
this.
I
think
that
gives
the
opportunity
for
the
for
the
user
that
does
the
import
to
actually
see
all
of
the
issues
imported
even
before
the
commands
arise
on
each
of
the
on
each
of
the
of
the
issue.
B
C
B
B
Yeah,
it
will
be,
it
will
be
similar,
even
if
we
do
like
we
can
do
it
flat
and
a
flat
manner
to
import
issue
than
having
four
commands
from
the
issues
and
unimportant
estimates
where
we
can
do
in
deep
line
for
each
issue,
import
everything
and
then
move
to
not
tomorrow
you
should
work.
Maybe
you
can
have
several
issues
that
do
import
everything
first
and
then
move
to
another
batch
of
issues
that
import
everything
top
down
yeah.
So
there
are
two
different
approaches
that
we
can
take.
I.
B
Think
just
because
we
have
experience
with
have
important
I
mean
the
code
itself
and
people
that
work
in
there.
We
can
reuse
that
idea
so
yeah.
The
other
thing
to
move
on
with
the
github
recorder
and
how
it
handles
things
that
we'll
have
to
address
here,
I
think
is
I
did
not
see
where
it
does
report
on
the
failed
imports
like
if
an
issue
did
not
import.
How
did
how
does
the
user
receive
that
kind
of
feedback?
B
E
B
B
F
C
F
B
G
G
You
know,
making
the
same
mistakes
for
architecting
this
in
a
way
that
doesn't
allow
us
to
do
this,
so
we
definitely
want
to
be
able
to
understand
which
things
imported,
which
didn't
where
the
failures
are
and
then
be
able
to
either
retry
those
failures
or
report
back
to
the
user,
which
things
that
fail,
which
things
fail,
so
they
can
manually
do
something
about
it
at
least
know
which
items
haven't
haven't
imported.
So
this
is
definitely
something
we
need
to
like.
G
C
G
Decide
to
batch,
so
efficiency
is
important,
I
mean
particularly
in
my
personal
I.
Don't
care
like
if,
if
we
import,
you
know
all
issues
and
then
add
all
the
comments
like
if
they
show
up
like
that
or
they
show
it
vertically.
Alright
like
that
is
not
I
know
where
the
value
is
and
which
one
is
more
valuable
to
the
user.
G
B
B
Yeah
I,
like
I,
totally
agree
again:
I,
don't
think
that
that
is
going
to
be
part
of
the
MVC
theirs
I,
don't
know,
I,
don't
talk
about
this
combo
yeah,
that's
there's
something
to
be
thread
and
unfollowed
up
so
yeah.
There
is
that
there
is
quite
a
bit
of
notes
on
on
this
fact
disfellowship
him,
so
we
need
to
take
care
of
those.
B
Yeah
then
there
is
the
I
think
with
the
notes
yeah.
So
we
have
this
on
the
button
where
George
is
mentioning
using
the
import
state
from
like
technical
and
architecture.
I
think
decision
is
that
ever
I
think
I
think
that's
the
right
thing,
because
that's
what
all
of
our
importance
to
use
the
state
and
the
import
data
and
I
think
we
can
reuse.
That
is
an
object
that
is
being
used
for
the
entire.
Like
a
lot
of
our
imports,
Fresno
do
import
repository
and
issues
were
repository.
B
I,
don't
think
we
have
an
importer
that
does
only
issues
right
now,
so
I'm
not
exactly
sure
how
that
will
work.
If,
for
instance,
someone
wants
to
import
issues
from
JIRA
and
that
wants
the
important,
a
positive
or
something
else
from
Florida,
so
not
exactly
sure
how
that
will
work
with
this,
but
the
important
my.
C
Main
my
main
concern
was
exactly
that
that
the
import
state
of
the
project
is
the
responsibility
of
it
was
to
import
the
project
as
a
whole
right,
not
partial,
import
of
just
issues
or
whatever
else
we
introduced
along
the
you
know,
along
the
way.
Let's
say
we
introduced
milestone
migration
from
JIRA.
We
introduced
epics
migration.
If
we
reuse
the
same
import,
state
I
think
there
might
be
also
some
side
effects
in
terms
of.
If
you
update
import
states
to
impress
right
now,
will
the
project
work
or
will
the
project
show
an
import
in
progress
state?
C
B
You
be
more
specific
on,
like
updates
on
the
models.
What
do
you
mean
like
pretty
much?
What
we
update
there
is
set
the
enforce
part,
which
seems
to
be
the
case
for
all
of
other
enforcement.
Obviously
we
didn't
have
yet
I,
don't
think
we
have.
We
haven't
yet
an
import
that
does
imports
from
two
different
providers.
So
that's
gnostic
dad
was
not
tackled
yet.
So
that's
probably
something
that
will
require
not.
B
Not
talking
about
reporting
issues
from
JIRA
and
from
some
other
place
we're
talking
about
like
importing
a
JIRA
project
into
a
github
project.
That's
my
understanding.
So
I
think
this
is
fine
to
be
used,
but
if
we
we
have
other
visions
that
it's
going
to
be
like
importing
issues
from
JIRA
and
repository
issues
from
some
other
place
and
yeah,
we
need
to
revisit.
C
C
Then,
if
we
just
need
to
double
check
the
unintended
side,
effects
of
updating
like
messing
with
the
import
state
when
the
project
is
imported
already,
you
know
I'm
not
sure,
there's
any
side
effects
in
the
UI,
like
I
said,
was
the
importer
state
blocking
they
use
the
use
of
the
project.
B
That
can
be
tackled
just
to
see
if
it's
a
specificity,
what
we
can
group
the
importers
and
say
these
are
issues
only
import,
just
no
need
to
be
positive,
and
so
on.
Yeah,
so
like
right
now,
I
don't
see
the
need
to
create
another
kind
of
object
or
to
store
the
statement
about
the
different
place,
but
maybe
the
more
we
dive
into
it.
It's
all
video,
but
yeah.
It's
it's
a
fair
point.
If.
G
G
B
Yeah,
so
with
that
moving
like
there
are
two
pieces
of
data
on
the
import
happening.
The
import
state,
which
is
mainly
I,
see
it
as
a
reporting
the
progress
on
the
on
the
import
because
it
goes
into
shadow
and
then
it
goes
into
started
and
any
goes
into
I.
Think
it's
finished
or
something
like
that.
B
A
couple
faces
a
couple
statuses
and
then
there
is
import
data
where
you
store
some
of
the
metadata
of
the
import
itself,
I
think
it's
or
some
clear
shells,
or,
for
instance,
for
the
for
the
jury,
important
store,
the
project
key
that
you
are
importing
from
and
I
think
this
is.
This
data
can
be
then
used
also,
for
instance,
for
for
storing
the
I.
Don't
know
they
lost
the
last
year,
I
issue
that
was
imported
so
that
when
next
time
the
import
is
started.
B
You
can
know
from
from
which
point
on
to
move-
and
this
is
a
bigger
question
for
the
data
idea.
Potentially
we're
like
it's
quite
complicated,
I,
don't
I
I'm
for
sure
not
we're
not
going
to
tackle
it
in
the
MVC.
But
there
are
a
lot
of
aspects
there
where
we
imported
a
bunch
of
issues
and
then
to
these
issues
the
description
was
dedicated.
Where
commands
were
edited.
What
do
you
do
when
you've
imported
update
is?
How
do
you
update
it
thread?
Which
ones
were
actually
changed?
B
Which
ones
did
not
change
and
so
on
so
for
the
MVC?
We
can
actually
I.
Think
it's
not
too
complicated
to
do
you
imported
everything
from
gr
at
up
to
issue
by
X
and
then
on
the
next
import.
You
can
import
from
this
issued
downwards
any
new
issue
there,
any
new
issue
that
was
added
but
I,
don't
think
we
can
tackle
in
this
version
the
previous
row
by
D.
B
B
So
yeah:
well
we
don't
have
that
yet,
but
I
think
well
I
mean
we
can
we
can
do
that.
I,
guess
and
BC
were
quickly
following
up
with
the
iteration
on
that,
so
that
that
seems
like
an
addressable
addressable
thing
to
do.
As
for
for
updating
the
edits,
that
happened,
I
think
that's
a
bigger
problem.
That
does
require
a
lot
more
thinking
and
architecture,
but.
G
B
C
B
D
B
B
G
Here
the
external
ID
is
going
to
be
more
and
more
important.
So
if
it's
something
that
you
can
find
used,
you
know
for
the
MVC.
So
for
the
MVC
you
can
use
that
fine,
but
I
think
eventually,
we'll
add
up
storing
the
external
ID
for
a
couple
of
different
reasons.
One
is
for
any
one
of
those
failures
that
are
not
just
like
you
know
you
import
this
much
and
then
you
stop.
Let's
say
you
have
failures
throughout.
G
You
can
go
back
and
figure
out
where
those
failures
are
and
then
just
working
and
pulling
those
things
and
the
other
one
is.
We
may
want
to
provide
actually
links
back
from
our
issues.
So
maybe
in
the
comment
we
may
want
to
put
a
link
back
to
the
JIRA
original
JIRA
issue
so
having
those
IDs
or
links
that
that
our
external,
unique
IDs
are
going
to
be
useful
for
some
of
the
features
we're
thinking
about.
So
if
this
is
something
that
you
find
useful
now
for
MVC,
please
feel
free
to
add.
B
For
the
linking
back,
we
like
the
grr
service,
already
provides
that,
if
you
would
put
in
if
you,
if
you
connecting
the
JIRA
service
to
the
given
project
or
given
instance,
and
then
you
put
the
the
issue
key,
it
will
identify
the
project
and
the
link
back,
and
we
already
have
that
even
in
DiBiase.
As
for
the
import
for
tracking
the
sailors,
I'm
not
sure
we
want
to
add
that
feel
to
the
issues
table
itself,
but
rather
have
a
separate
table
to
just
storing
that.
So
this
is
where
the
the
technical
hospital
becomes.
B
Do
we
want
to
add
another
field
to
the
issues
table
and
mainly
have
it
is
like
empty
or
null
and
then
for
some
of
the
important
values
there
or
if
you
want
it
only
to
track
the
status
of
the
import,
then
we
probably
don't
want
to
do
that.
Probably
just
have
it
some
other
object,
somehow
the
table
track
it
there
and
then
just
get
rid
of
that,
and
so
on.
So
wonder.
G
B
B
Oh
there's,
one
outside
of
the
embassy
where
anything
is
like,
so
we
would
import
issues.
Would
we
want?
So?
Let's
say
we
have
a
customer
that
would
want
to
only
import
art
like
a
portion
of
the
issues
that
they
have
in
in
JIRA
into
github,
like
the
the
simplest
thing
that
I'm
thinking
is
like
I
want
to
only
important
issues:
I
don't
need
everything
imported
into
gitlab.
Let's
just
start
fresh
import,
only
the
open
issues
and
we'll
just
continue
to
work
on
github.
B
So
then
we'll
have
to
have
the
option
of
selecting
the
status
that
you
want
to
view
issues
to
be
imported
or
man.
There
is
another
request
where
you
want
to
the
ones
that
are
resolved,
resolved
idea
were
and
so
on
and
so
forth.
Is
that
something
that
would
plan
on
adding
them
doing?
When
is
that,
like?
Maybe
they
can
just
pull
the
gql
from
the
JIRA
issue?
Put
it
into
a
field
that
we
provide
very
the
issues
so.
H
I
think
they
not
for
the
MVC
but
I
think
yes
exactly.
We
need
some
way
to
allow
the
user
to
kind
of
customize
the
issues
that
would
get
important,
I
I'm
gonna
talk
with
Gabe.
We
can
make
a
decision
on
this,
I
think
one
that
makes
the
most
sense
to
me
and
we'd
seen.
The
easiest
is
just
accept
a
query
string
like
just
take.
Let
them
create
the
query
and
you're
and
copy
and
paste
it
into
RN,
and
we
can
use
that
to
structure
the
the
important
point
I
mean.
H
G
I
People
that
can
import
our
admins
or
owners
and
good
lob,
so
they
I
would
assume
that
people
who
have
that
permission
have
some
knowledge
and
I
would
also
say
that
yes,
there's
already
a
endpoint
and
for
searching
for
issues
based
on
a
jaql
query
so
like
it's,
not
that
would
be
the
path
of
least
resistance
for
us
to
do,
and
you
know
like,
as
a
next
step,
to
allow
better
scoping
of
issues.
Even
if
that
is
more
technical,
it's
the
easiest
place
to
start
and
I
would
start
there.
I
also
think
it's
important.
I
We
were
talking
about
yesterday
in
slack
that,
like
made
more
or
less
like
linking
one
project
in
JIRA
to
one
project
can
get
loud,
but
I.
Don't
think
that
that's
like
that
restriction
is
beneficial
in
long
run,
especially
if
you
look
at
the
JQ
o
query,
which
spans
multiple
projects,
because
the
way
the
issues
are
organized
in
the
endpoints,
it's
not
it's
not
automatically
scoped
to
project.
It's
just
like
you
have
an
issues
in
point
and
you
can
get
all
issues
basically
and
I.
Think
you
can
scope
it
to.
I
You
can
insert
a
parameter
to
get
a
project,
but
you
can
also,
with
the
JQ,
look,
really
look
across
all
projects
and
so
I
think
there
is
a
valid
use
case
where
people
want
to
pull
like
multiple
projects
or
issues
from
different
projects
into
one
get
a
project,
and
we
shouldn't
force
them
to
not
be
able
to
do
that.
Tygris
not.
B
I
I
think
this
gets
back
to
a
underlying
problem
of
like
what
the
original
scope
for
the
ABC
was,
making
it
more
or
less
like
once
the
import
is
done.
You
don't
maintain
state
about
anything
like
they're
responsible
for
basically
not
duplicating
things
and
we're
not
maintaining
like
partial
imports
of
some
objects
later
on
and
based
on.
I
What's
new,
like
that's
super
complex,
and
that's
something
that
maybe,
if
we
get
to
that
point
and
that's
required,
but
right
now,
I'm
just
like
of
the
mindset
like
if
you're,
if
you're
importing
issues
you
know
project
and
you
realize
I
need
to
rerun
the
imports.
I
didn't
get
everything
like
what
I
did
when
I
was
running.
B
B
I
I
H
B
H
Like
when
I'm
spinning
up
when
I'm
sitting
when
I'm
setting
up
the
import
process,
let
say
I
wanna,
pull
from
this
project
or
here's
my
jQuery
or
whatever
an
optional
like
add
this
label
to
these
issues,
any
issue
that
gets
imported
because
then
that'll
left
that
would
allow
the
user
to
kind
of
self
maintain
tracking
and
even
say
you
know
they
could
create
a
separate
different
label
every
time
we
maybe
that
was
important.
One
import,
I'm,
trying
to
think
ways.
I
E
Would
be
the
benefit
in
allowing
them
to
import
again
begin
without
first
removing
the
issues
does
it
does
sound
like
in
that
case
we
would
potentially
have
imported
project.
The
project
has
issues,
and
then
you
import
it
again
and
now
you
have
issue
one
project,
one
issue,
one
import
would
that
be
correct.
You
would
have
essentially
multiple
copies.
The.
I
Goal
would
be
like
think
about
slowly
transitioning.
Let's
say
you
don't
want
to
bring
all
you.
This
is
like
not
the
MU
C,
but
when
we
get
to
allowing
people
to
scope
by
Jake,
you
go
query.
Let's
say
somebody
just
wants
to
give
get
lab
a
dry
run
and
they
have
a
sprint
and
JIRA
and
they
want
to
bring
just
that
sprints
issues
up
right
and
those
like,
so
they
write
a
jQuery.
They
scope
it
to
just
the
sprints
issues.
They
copy
that
over.
Let's
say
that
you
know
they're
p.m.
I
is
working
on
issues
for
the
next
one
and
then
they
want
to
bring
that
next
sprint
over
right,
like
and
so
like
scoping
the
issues.
It's
just
that
and
then
importing
those
issues.
You're
gonna
have
the
there's
a
couple
different
scenarios
where
you're
gonna
bulk
import
like
an
entire
project
over,
but
then
you're
gonna
have
the
scenario
where
I
just
want
a
small
subset
of
my
issues,
because
maybe
I
don't
even
care
about
all
the
other
issues
over
there.
I
Right
now,
or
maybe
I
like
we
just
don't
know,
but
that's
where,
like
I,
would
not
artificially
limit
the
user.
By
saying
once
you
import,
you
can't
import
again
for
the
project,
because
then
we
would
have
to
add
state
tracking
for
okay.
Have
you
deleted
all
the
issues
from
the
other
project
or
we'd
have
to
add
state
track
before?
Okay,
which
issues
have
you
important,
have
u-unless
just
grab
the
ones
that
you
haven't
yet
like
there's
all
sorts
of
conditional
logic
that
it's
gonna
get
super
messy.
E
That
mean
that
we
would
potentially
have
to
kind
of
versions
of
an
issue
sure
okay
I'm
just
trying
to
decide
if
from
UI
perspective,
if
we
need
to
warn
them
with
that
or
denote
the
differences
somehow
like
we
have
open
and
closed
when
we,
you
know
close
an
issue
or
when
we
turn
an
issue
into
an
epoch.
It
closes
that,
but
it
creates
that
copy,
and
that
alone
causes
confusion.
And
so
I
want
to
understand
if
there's
a
way
that
we
need
to.
E
I
But
that's
also
like
where
we
have
to
balance
not
over
engineering.
You
know
like
to
meet
what
their
goals
are
and
I
think
the
only
way
that
we
do,
that
is
by
shipping
in
small
pieces
and
like
and
then
iterating,
so
in
the
way
that
I
look
at
it
is
like
get
the
basic
NPC
working
where
you
pull
issues
next
up
get
the
JQ
o
query
working
where
it's
pulling
all
the
things
scope,
the
JQ
worry,
don't
worry
about.
H
H
H
Going
piece
of
feedback,
yeah
I,
don't
know
it
might
have
been
about
custom,
workflows
or
I
need
for
that
it
was.
The
comment
was
really
dislike.
Stop
treating
us
stop.
Treating
us
constant
users
like
were
stupid,
I
was
on
the
custom
fields,
issue
yeah
was
it
the
custom
field,
just
like
sticks
with
me
is
like
because
I
know
what
we're
coming
from
it
from
that
we
want
to
put
guard
rails.
H
So
you
don't
you
don't
mess
things
up,
but
at
the
same
time
like
if
you're
doing
this,
if
you're
interactive
in
these
products,
like
you
generally
know
what
you're
doing,
and
we
need
to
respect
that
and
just
read
it
I'd
rather
give
information
and
learn
when
somebody
does
get
confused
and
use
that
to
optimize
I.
Think.
F
I
want
to
kind
of
push
back
a
bit
about
all
this
because
it
feels
like
what
we're
doing
is
just
your
shotgun
blasts,
saying:
hey,
here's
everything,
but
there's
no
organizational
structure
and
so
you're
not
having
any
sort
of
I
imported
this
at
this
date
and
time
on
this
project,
it's
like
well,
there
is
no
project
data,
that's
coming
over,
there's
no
labeling,
there's!
No
anything!
That's
coming
over,
except
with
the
pieces
that
we've
described
and
so
having
this
issue
of
your
having,
for
example,
re-importing,
can
cause
confusion.
F
F
F
I'm
saying
is
that
okay,
that's
fine
and
wonderful,
but
let's
leave
that
at
this
as
an
engineer,
excuse
me
engineering
level
and
not
leave
that
as
a
user-facing
project
or
tasks
like
we
have
this
thing
under
the
hood.
It's
working
behind
the
scenes
for
private
use
and
tests
kind
of
like
at
a
beta
version,
but
it's
not
ready
for
primetime.
It's
not
ready
for
user
consumption.
Apart
from
like
specific
user
test
cases
like
we
hand-picked
users
to
test
this,
I
wouldn't
roll
this
out
publicly
until
like
we
can
have
qualitative
or
quantitative
usage
of
it.
F
So
like
I'm,
importing
a
project
or
have
a
project
in
segments
and
I
know
I
did
it
on
this
date
within
this
inventory,
with
this
architecture
of
these
labels
and
then
I
can
do
it
in
a
few
and
merged
them,
or
you
know
having
a
more
robust
project
instead
of
just
here's,
some
data
figure
it
out.
Yeah.
I
So
maybe
we
stash
that
and
save
that
with
the
project
itself.
So
you,
when
you
go
to
the
JIRA
importer,
you
can
click
on
the
tab
to
view
my
past
imports,
along
with
all
the
data
they
came
up
with
them,
like
there's
all
sorts
of
ways.
I
completely
agree
that
I
want
to
iterate
to
get
there,
but
like
that.
If
we
wait
until
it's
at
that
point
to
start
getting
it
in
the
hands
of
customers,
that's
three
months
out
and
like
no.
F
I
H
Get
an
MVC
out
of
this
by
1210
we
took
the
reduce
scope
and
communicated
the
risks
involved.
You
know,
and
it's
getting
reported
on
to
the
executive-level
in
the
air
efficiency
mediator.
Having
and
at
this
point
it
seems
it
it's
comfortable
with
us.
Moving
forward
with
an
MVC
that
is
uncomfortable
sentence
makes
sense,
and
so
that's
that's
where
this
is
that
so
yeah
I
agree
there
are
things
I
would
I
would
rather
have
in
the
MVC
before
we
rolled
it
out.
I
Those
lines
Holly.
What
can
we
do
to
do?
Some
of
that
qualitative
research
at
the
same
time
so
like
I,
would
like
to
do
that
in
parallel
and
I
would
like
to
like
roll
that
in
as
we're
shipping,
these
small
things,
those
improvements
like
I,
don't
want
to
just
say,
like
put
the
blinders
on
in
march
forward.
So
I
would
like
to
figure
out
what
we
can
do
to
like
be
intentional
about
doing
this
in
a
timely
manner.
I
H
Don't
we
had
some
I
know
one
of
the
things
we're
tracking
is
like
the
number
of
instances
that
have
the
turret,
like
integration
spot
right,
I
think
I
saw
that
in
periscope
the
other
day
yeah
it's
there,
it's
an
HP,
yeah
I.
Was
there
not
trying
to
leverage
that,
like
in
a
messaging
tool
that
the
growth
team
has
rolled
out?
Actually,
like
maybe
hey
like
to
try
to
import
some
issues
just
right
now
we
can
expand
our
I
just.
E
Need
to
define
first,
who
it
is
that
we
want
to
actually
do
the
testing
with
so
I
suppose,
with
Kathryn
again
yesterday
and
I
have
started
working
on
a
research
issue
that
I'm
gonna
wrap
up
actually
after
this
call
and
Daniel
and
I
and
Katherine
will
start
collaborating
on
that.
To
start
this
research
process,
but
I
think
we
need
to
understand
if
we're
looking
for
people
who
are
actively
looking
to
move
from
JIRA
to
get
lab
or
if
it's
customers
who
are
kind
of
trying
to
do
that
process
right
now.
E
Another
way
we
need
to
define
all
of
that
I
also
reached
out
to
Ben
Prescott
the
other
day
and
got
access
to
Zen
desk
and
started
looking
for
tickets,
and
there
were
several
requests
in
there
from
customers
for
this
very
issue.
So
it
would
be
great
if
we
can
maybe
get
in
touch
with
those
people
and
take
advantage
of
that
and
kind
of
pull
some
resources
from
there.
E
But
my
first
thought
is
that
we
could
start
with
a
survey
just
to
kind
of
cast
a
wide
net
and
see
who
all
might
be
a
qualifier
for
this
type
of
research
and
then
from
there
start
working
on
some
quick
wireframes
or
a
prototype
or
just
even
high-level
interviews.
If
nothing
else,
because
there's
a
series
of
questions
that
I
know,
we
want
to
answer
before
we
get
too
deep
just
to
help
us
kind
of
get
down
the
right
path.
E
F
F
C
B
G
Heard
of
cases
where
people
use
that
format
and
and
just
export
all
of
JIRA
massage
it
into
the
CSV
format
and
import.
So
this
is
a
cheap
way
or
like
the
only
way,
right
now
for
people
to
move
issues
from
JIRA
into
good
lab.
However,
it
only
does
title
and
description
and
I
think
description
might
be
broken
right
now
we
have
a
bug.
So
that's
that's
the
state
of
it
right
now.
A
Whatever
on
the
talk
there,
just
before
of
labeling
and
all
I
can
stuff,
when
we
import
stuff,
maybe
George
Nellie
Sandra,
maybe
know
the
way
we
accomplish.
That
on
service
desk
was
to
lie
users
to
upload
templates
and
then
allow
them
to
select
the
template
and
use
that
when
you
know,
when
somebody
emails
service
desk,
it
seems
like
we
could
do
something
very
similar
and
it's
relatively
low
cost
and
it
would
give
the
user
the
ability
to
basically
set
any
labels
any
milestones.
Any
quick
action
can
be
executed
on
every
issue.
A
F
I
think
that's
something
that
would
be
a
really
huge
benefit
you,
you
know
through
the
late
importing
process,
you
would
say:
okay
now
I
finished,
my
import.
Do
you
want
to
add
a
label
or
some
sort
of
taxonomy
to
this
job
that
you
have
completed,
and
then
that
ties
it
into
our
labeling
system.
So
then,
when
they
leave
the
process
once
they've
finished
now
their
import
has
an
attached
label
as
part
of
this
workflow,
so
they're
not
really
importing
anything.
They
just
have
to
add
something
manually.
It.
A
Wouldn't
either,
but
even
that
would
be
quite
a
lot
harder
to
build
in
this
case.
As
the
importer
creates
issues,
it
would
use
a
template
that
we've
that
the
user
has
defined
themselves
and
pushed
up
to
the
project
and
that
template
could
have
quick
actions.
Add
these
three
labels
assigned
to
this
milestone
and
apply
a
way
that
I
don't
know
why
you
would
want
to
do
that.
But
you
know
you
just
have
this
maximum
flexibility
that
you
can
use
any
quick
action
in.
F
B
There
are
some
things
to
be
answered
there
like,
even
if
we
only
allowed
it
to
label
things,
do
we
want
to
have
a
default
label
on
every
important,
even
if
they
don't
affect
anything,
do
we
want
to
kind
of
hardly
impose
a
label
on
any
import
so
that
they
can
wait
to
remove
them,
but
at
least
like
even
the
if
they
forgot
to
do
so,
we'll
have
it
labeled
by
some
date
or
something
anything
and
similarly
with
a
template.
If
they
didn't
create
one,
should
we
have
one
set
up
by
default
and
so
on
that.
G
B
Think
just
labeling
it
couldn't
work.
I'll
have
to
look
into
that,
and
and
even
like
labeling,
maybe
with
the
current
date
like
during
important
date
and
then
the
next
important
F
during
import
the
other
date
or
date.
Time
were
whatever
so
that
you
can
down
later
on
just
filter
out
and
that
we
can
work
on
that
and
I'm.
G
B
C
I
Again,
to
get
loud
description
and
like
the
most
important
thing
is
moving
comments
over
which
is
like
a
whole
other
like
can
worms
and
so
I
don't
know.
This
is
why
we
sort
of
like
need
to
get
something
out
there
and
then
start
getting
feedback
from
customers
about
what
is
important
for
them
to
bring
over,
because
I
have
a
sort
of
a
good
idea
based
on
the
information
I
have,
but
it's
incomplete,
and
so
like
doing
things
in
of
Li.
I
While
keeping
these
things
in
mind
is
what
we
need
to
do
and
like
touching
base
on
a
regular
cadence
to
talk
about.
Okay
well,
really
sustain
this
much.
What's
what
problem
should
we
solve
next,
because
there's
literally
like
30
problems
that
we
can
focus
on,
but
we
really
need
to
force
rank
them
and
I
put
the
engineering
effort
behind
solving
the
ones
that
are
most
important
for
the
customers,
something.
C
G
All
said
and
done,
yeah
max
anything
from
from
and
now
of
course,
getting
keen
and
both
dropped
off,
but
my
understanding
is
that
long
term
this
goes
back
to
I
just
got
saved
here.
This
is
being
recorded
long
term.
This
feature
comes
back
to
the
import
team
towards
maintenance
and
featured
broke,
but
it
all
I
know
what
monitor
means,
whether
that's
three
miles
Thomas
or.