You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2014/10/21 17:41:55 UTC

Test run of ticket import to forge-allura

I have exported Allura tickets from SourceForge and imported them to
https://forge-allura.apache.org/p/allura/tickets/   Check it out, how does it
look?  You will need to log in to view them, since this isn't our final run.
Anyone can create an account though.

The import was filtered down to Allura-related tickets (no SF internal stuff)
and milestones were changed from SourceForge development sprints to our release
version numbers.  Also the "size" custom field (used for SourceForge planning)
was converted to a label, so it is not as prominent.  I created accounts for
some top users, so their usernames match.  Other usernames will just show
"Originally created by: username".

How does it look?  Anything look amiss, or could be improved?

P.S. it took about 10 hours to run the import!

-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: Test run of ticket import to forge-allura

Posted by Dave Brondsema <da...@brondsema.net>.
I tweaked the status (and component) options for the new tracker config, so that
works fine now.

Probably next week I'll do a full run, when I get the SourceForge-side redirects
and changes ready too.

On 10/22/14 1:03 PM, Cory Johns wrote:
> LGTM.  I confirmed the issue Igor mentioned, and confirmed that there are
> no other statuses besides "review" that are not present on the new tracker.
> 
> On Wed, Oct 22, 2014 at 6:14 AM, Igor Bondarenko <je...@gmail.com> wrote:
> 
>> Looks great! Existing user accounts are linked, really cool!
>>
>> There's one minor inconsistency, though. Tickets with 'code-review' status
>> imported as 'review'. And if you'll try to edit such ticket, 'open' will be
>> selected by default for a status, since there are no 'review' in status
>> options at all. E.g.
>> https://forge-allura.apache.org/p/allura/tickets/7704/
>>
>> On Wed, Oct 22, 2014 at 6:06 AM, Alex Luberg <al...@slashdotmedia.com>
>> wrote:
>>
>>> I think it looks great, have checked a few older milestones, most popular
>>> user accounts were created and now linked with posts, cool!
>>>
>>> On Tue, Oct 21, 2014 at 8:41 AM, Dave Brondsema <da...@brondsema.net>
>>> wrote:
>>>
>>>> I have exported Allura tickets from SourceForge and imported them to
>>>> https://forge-allura.apache.org/p/allura/tickets/   Check it out, how
>>>> does it
>>>> look?  You will need to log in to view them, since this isn't our final
>>>> run.
>>>> Anyone can create an account though.
>>>>
>>>> The import was filtered down to Allura-related tickets (no SF internal
>>>> stuff)
>>>> and milestones were changed from SourceForge development sprints to our
>>>> release
>>>> version numbers.  Also the "size" custom field (used for SourceForge
>>>> planning)
>>>> was converted to a label, so it is not as prominent.  I created
>> accounts
>>>> for
>>>> some top users, so their usernames match.  Other usernames will just
>> show
>>>> "Originally created by: username".
>>>>
>>>> How does it look?  Anything look amiss, or could be improved?
>>>>
>>>> P.S. it took about 10 hours to run the import!
>>>>
>>>> --
>>>> Dave Brondsema : dave@brondsema.net
>>>> http://www.brondsema.net : personal
>>>> http://www.splike.com : programming
>>>>               <><
>>>>
>>>
>>
> 



-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Re: Test run of ticket import to forge-allura

Posted by Cory Johns <jo...@gmail.com>.
LGTM.  I confirmed the issue Igor mentioned, and confirmed that there are
no other statuses besides "review" that are not present on the new tracker.

On Wed, Oct 22, 2014 at 6:14 AM, Igor Bondarenko <je...@gmail.com> wrote:

> Looks great! Existing user accounts are linked, really cool!
>
> There's one minor inconsistency, though. Tickets with 'code-review' status
> imported as 'review'. And if you'll try to edit such ticket, 'open' will be
> selected by default for a status, since there are no 'review' in status
> options at all. E.g.
> https://forge-allura.apache.org/p/allura/tickets/7704/
>
> On Wed, Oct 22, 2014 at 6:06 AM, Alex Luberg <al...@slashdotmedia.com>
> wrote:
>
> > I think it looks great, have checked a few older milestones, most popular
> > user accounts were created and now linked with posts, cool!
> >
> > On Tue, Oct 21, 2014 at 8:41 AM, Dave Brondsema <da...@brondsema.net>
> > wrote:
> >
> > > I have exported Allura tickets from SourceForge and imported them to
> > > https://forge-allura.apache.org/p/allura/tickets/   Check it out, how
> > > does it
> > > look?  You will need to log in to view them, since this isn't our final
> > > run.
> > > Anyone can create an account though.
> > >
> > > The import was filtered down to Allura-related tickets (no SF internal
> > > stuff)
> > > and milestones were changed from SourceForge development sprints to our
> > > release
> > > version numbers.  Also the "size" custom field (used for SourceForge
> > > planning)
> > > was converted to a label, so it is not as prominent.  I created
> accounts
> > > for
> > > some top users, so their usernames match.  Other usernames will just
> show
> > > "Originally created by: username".
> > >
> > > How does it look?  Anything look amiss, or could be improved?
> > >
> > > P.S. it took about 10 hours to run the import!
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > >               <><
> > >
> >
>

Re: Test run of ticket import to forge-allura

Posted by Igor Bondarenko <je...@gmail.com>.
Looks great! Existing user accounts are linked, really cool!

There's one minor inconsistency, though. Tickets with 'code-review' status
imported as 'review'. And if you'll try to edit such ticket, 'open' will be
selected by default for a status, since there are no 'review' in status
options at all. E.g. https://forge-allura.apache.org/p/allura/tickets/7704/

On Wed, Oct 22, 2014 at 6:06 AM, Alex Luberg <al...@slashdotmedia.com>
wrote:

> I think it looks great, have checked a few older milestones, most popular
> user accounts were created and now linked with posts, cool!
>
> On Tue, Oct 21, 2014 at 8:41 AM, Dave Brondsema <da...@brondsema.net>
> wrote:
>
> > I have exported Allura tickets from SourceForge and imported them to
> > https://forge-allura.apache.org/p/allura/tickets/   Check it out, how
> > does it
> > look?  You will need to log in to view them, since this isn't our final
> > run.
> > Anyone can create an account though.
> >
> > The import was filtered down to Allura-related tickets (no SF internal
> > stuff)
> > and milestones were changed from SourceForge development sprints to our
> > release
> > version numbers.  Also the "size" custom field (used for SourceForge
> > planning)
> > was converted to a label, so it is not as prominent.  I created accounts
> > for
> > some top users, so their usernames match.  Other usernames will just show
> > "Originally created by: username".
> >
> > How does it look?  Anything look amiss, or could be improved?
> >
> > P.S. it took about 10 hours to run the import!
> >
> > --
> > Dave Brondsema : dave@brondsema.net
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> >               <><
> >
>

Re: Test run of ticket import to forge-allura

Posted by Alex Luberg <al...@slashdotmedia.com>.
I think it looks great, have checked a few older milestones, most popular
user accounts were created and now linked with posts, cool!

On Tue, Oct 21, 2014 at 8:41 AM, Dave Brondsema <da...@brondsema.net> wrote:

> I have exported Allura tickets from SourceForge and imported them to
> https://forge-allura.apache.org/p/allura/tickets/   Check it out, how
> does it
> look?  You will need to log in to view them, since this isn't our final
> run.
> Anyone can create an account though.
>
> The import was filtered down to Allura-related tickets (no SF internal
> stuff)
> and milestones were changed from SourceForge development sprints to our
> release
> version numbers.  Also the "size" custom field (used for SourceForge
> planning)
> was converted to a label, so it is not as prominent.  I created accounts
> for
> some top users, so their usernames match.  Other usernames will just show
> "Originally created by: username".
>
> How does it look?  Anything look amiss, or could be improved?
>
> P.S. it took about 10 hours to run the import!
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>               <><
>