You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@allura.apache.org by Rich Bowen <rb...@rcbowen.com> on 2013/03/25 15:54:38 UTC
Re: Status of allura import
So, I see you've got a new ticket open about this, which seems to indicate that you're making progress. I was wondering if we could persuade you to take really good notes and produce some docs of how this process works?
--Rich
On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
> Things have settled down on my project a bit now, so I've gone ahead with the migration. I haven't migrated the tickets yet because the code link is broken. If anyone has any insight into this, it would be much appreciated.
> https://sourceforge.net/p/allura/tickets/5844/
>
> Once this is resolved I'll try the ticket import.
>
>
> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>
> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>
>> I'm not sure how I would go about creating a test project on SourceForge. I'm not setting up my own Allura instance, I'm using the one on SourceForge.
>>
>
> Go to http://sf.net/create and click the Create Your Project button. That'll get you started.
>
> --
> Rich Bowen
> rbowen@rcbowen.com :: @rbowen
> rbowen@apache.org
>
>
>
>
>
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
--
Rich Bowen
rbowen@rcbowen.com :: @rbowen
rbowen@apache.org
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
I don't have any other planned improvements right now. Although I'd be
happy to go over the changes that you are planning, if that helps.
On Mon, Apr 8, 2013 at 4:54 PM, Dave Brondsema <da...@brondsema.net> wrote:
> Hey Jon,
>
> We're thinking about smoothing out this process for other SourceForge
> projects.
> Automating a lot of the things you listed as "manual". Just wanted to
> mention
> this in case you were planning on making any further improvements, I don't
> want
> us to duplicate anything or cause conflicts.
>
> -Dave
>
> On 3/27/13 6:56 PM, Jon Schewe wrote:
> > Here are my notes that I used to track my progress doing this migration.
> I
> > needed to make some changes to allura_import.py, those changes are
> reflected in
> > the pull request for allura ticket 6020. One big downside to the new
> tracker is
> > the lack of ability to sort the saved search results by priority.
> >
> > Some python modules needed to be installed, but I don't remember which
> ones
> > beyond the following:
> > * python-paste
> >
> > Steps
> > * notify developers of the potential migration
> > * Migrate the wiki manually - there are some scripts on gist to help wi
> > th this, although I didn't end up using them.
> > * <https://gist.github.com/619537>
> > * <https://gist.github.com/1286682>
> > * Update website redirection.
> > * Notify all developers of the migration.
> > * Remove ticket write permissions
> > * Start migration.
> > * Use `~/src/allura-git/scripts/trac_export.py` to export the tickets
> to
> > allura-import.json
> > * ./scripts/trac_export.py --no-attachments -o
> > ~/projects/fll-sw/allura-import.json --only-tickets -v
> > https://sourceforge.net/apps/trac/fll-sw/
> > * Keep repeating this until it doesn't fail, it seems to timeout
> quite a bit
> > * Request import API key
> > * Use `~/src/allura-git/scripts/allura_import.py` with `user_map.json`
> and
> > allura-import.json to import tickets
> > * PYTHONPATH=~/src/allura-git/Allura
> > * export PYTHONPATH
> > * python ~/src/allura-git/scripts/allura_import.py \
> > -a API \
> > -s SECRET \
> > -p fll-sw \
> > -t issues \
> > -u https://sourceforge.net \
> > --user-map=user_map.json \
> > --verbose \
> > allura-import.json
> > * Manually add milestones
> > * Manually pull the attachments for tickets.
> > * worked from trac files backup, didn't have many so manually worked
> > * Update wiki documentation for where to file bugs
> > * Notify developers
> >
> >
> > On Wed, Mar 27, 2013 at 10:48 AM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>> wrote:
> >
> > Thanks, it looks like all of the information went in. I'll be
> posting the
> > steps I used and references to the tickets I filed to get the import
> to
> > work. I am disappointed that the saved searches can't sort on
> priority.
> >
> >
> > On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <dave@brondsema.net
> > <ma...@brondsema.net>> wrote:
> >
> > It might take a minute or two for search indexes to be updated.
> It
> > looks like
> > search includes your imported tickets now. Also, the API
> endpoint at
> > https://sourceforge.net/rest/p/fll-sw/issues just lists a
> little bit of
> > info for
> > each ticket. If you want an API endpoint for full details on a
> ticket,
> > just add
> > the number to the URL like:
> https://sourceforge.net/rest/p/fll-sw/issues/1
> >
> > On 3/26/13 7:24 PM, Jon Schewe wrote:
> > > Wait, I spoke too soon. In my email came a link to the ticket
> and that
> > shows
> > > more information.
> > > https://sourceforge.net/p/fll-sw/issues/1/
> > >
> > >
> > > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> > >
> > > OK, I hacked up a fix that creates a new hash for the
> document to
> > import:
> > > doc_import={}
> > > doc_import['trackers'] = {}
> > > doc_import['trackers']['default'] = {}
> > > doc_import['trackers']['default']['artifacts']
> =
> > [ticket_in]
> > >
> > > Now I can import a ticket. I can see it
> > > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > > at
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> > >
> > > It also looks like most of the information didn't get
> imported.
> > That's not
> > > going to be very helpful. This is the raw JSON for the
> ticket that was
> > > imported. I would have expected the comments, milestone,
> status,
> > submitter
> > > to make it in.
> > > {
> > > "assigned_to": "jpschewe",
> > > "cc": "",
> > > "class": "ARTIFACT",
> > > "comments": [
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **milestone** set to _Parking
> Lot_\n\n",
> > > "date": "2010-10-02T21:41:54Z",
> > > "submitter": "jpschewe"
> > > },
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **owner** set to _jpschewe_\n *
> > **status** changed
> > > from _new_ to _accepted_\n\n",
> > > "date": "2010-10-02T21:51:55Z",
> > > "submitter": "jpschewe"
> > > },
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **status** changed from _accepted_
> to
> > _closed_\n *
> > > **resolution** set to _invalid_\n * **component** set to
> > _General_\n\n",
> > > "date": "2010-10-02T22:58:37Z",
> > > "submitter": "jpschewe"
> > > }
> > > ],
> > > "component": "General",
> > > "date": "2010-09-21T01:18:00Z",
> > > "date_updated": "2010-10-02T22:58:37Z",
> > > "description": "testing MyLyn",
> > > "id": 1,
> > > "keywords": "",
> > > "milestone": "Parking Lot",
> > > "priority": "major",
> > > "resolution": "invalid",
> > > "status": "closed",
> > > "submitter": "jpschewe",
> > > "summary": "test ticket",
> > > "type": "defect"
> > > }
> > >
> > >
> > >
> > > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <
> jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> wrote:
> > >
> > > Looks like tickets_in should be set to doc in my case.
> > Although line 80
> > > is now giving me problems as it looks like you're
> trying to
> > reuse the
> > > JSON document to submit and it's not working because
> it's not
> > formatted
> > > as expected.
> > >
> > >
> > > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <
> jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> wrote:
> > >
> > > So far it's going poorly:
> > >
> > > Traceback (most recent call last):
> > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 123, in <module>
> > > main()
> > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 51, in main
> > > verbose=options.verbose)
> > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 69, in import_tracker
> > > tickets_in =
> doc['trackers']['default']['artifacts']
> > > TypeError: list indices must be integers, not str
> > >
> > > File to import is attached.
> > >
> > >
> > >
> > > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> wrote:
> > >
> > > I'll try. Should I post them back to the list?
> > >
> > >
> > > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> > <rbowen@rcbowen.com <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>>> wrote:
> > >
> > > So, I see you've got a new ticket open
> about this,
> > which
> > > seems to indicate that you're making
> progress. I was
> > > wondering if we could persuade you to take
> really
> > good notes
> > > and produce some docs of how this process
> works?
> > >
> > > --Rich
> > >
> > > On Feb 23, 2013, at 4:53 PM, Jon Schewe
> wrote:
> > >
> > >> Things have settled down on my project a
> bit now,
> > so I've
> > >> gone ahead with the migration. I haven't
> migrated the
> > >> tickets yet because the code link is
> broken. If
> > anyone has
> > >> any insight into this, it would be much
> appreciated.
> > >>
> https://sourceforge.net/p/allura/tickets/5844/
> > >>
> > >> Once this is resolved I'll try the ticket
> import.
> > >>
> > >>
> > >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> > >> <rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> wrote:
> > >>
> > >>
> > >> On Dec 5, 2012, at 3:17 PM, Jon
> Schewe wrote:
> > >>
> > >>> I'm not sure how I would go about
> creating a
> > test
> > >>> project on SourceForge. I'm not
> setting up
> > my own
> > >>> Allura instance, I'm using the one on
> > SourceForge.
> > >>>
> > >>
> > >> Go to http://sf.net/create and click
> the
> > Create Your
> > >> Project button. That'll get you
> started.
> > >>
> > >> --
> > >> Rich Bowen
> > >> rbowen@rcbowen.com
> > <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>> :: @rbowen
> > >> rbowen@apache.org <mailto:
> rbowen@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> http://mtu.net/~jpschewe
> > >>
> > >
> > > --
> > > Rich Bowen
> > > rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>> ::
> @rbowen
> > > rbowen@apache.org <mailto:
> rbowen@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Dave Brondsema <da...@brondsema.net>.
Hey Jon,
We're thinking about smoothing out this process for other SourceForge projects.
Automating a lot of the things you listed as "manual". Just wanted to mention
this in case you were planning on making any further improvements, I don't want
us to duplicate anything or cause conflicts.
-Dave
On 3/27/13 6:56 PM, Jon Schewe wrote:
> Here are my notes that I used to track my progress doing this migration. I
> needed to make some changes to allura_import.py, those changes are reflected in
> the pull request for allura ticket 6020. One big downside to the new tracker is
> the lack of ability to sort the saved search results by priority.
>
> Some python modules needed to be installed, but I don't remember which ones
> beyond the following:
> * python-paste
>
> Steps
> * notify developers of the potential migration
> * Migrate the wiki manually - there are some scripts on gist to help wi
> th this, although I didn't end up using them.
> * <https://gist.github.com/619537>
> * <https://gist.github.com/1286682>
> * Update website redirection.
> * Notify all developers of the migration.
> * Remove ticket write permissions
> * Start migration.
> * Use `~/src/allura-git/scripts/trac_export.py` to export the tickets to
> allura-import.json
> * ./scripts/trac_export.py --no-attachments -o
> ~/projects/fll-sw/allura-import.json --only-tickets -v
> https://sourceforge.net/apps/trac/fll-sw/
> * Keep repeating this until it doesn't fail, it seems to timeout quite a bit
> * Request import API key
> * Use `~/src/allura-git/scripts/allura_import.py` with `user_map.json` and
> allura-import.json to import tickets
> * PYTHONPATH=~/src/allura-git/Allura
> * export PYTHONPATH
> * python ~/src/allura-git/scripts/allura_import.py \
> -a API \
> -s SECRET \
> -p fll-sw \
> -t issues \
> -u https://sourceforge.net \
> --user-map=user_map.json \
> --verbose \
> allura-import.json
> * Manually add milestones
> * Manually pull the attachments for tickets.
> * worked from trac files backup, didn't have many so manually worked
> * Update wiki documentation for where to file bugs
> * Notify developers
>
>
> On Wed, Mar 27, 2013 at 10:48 AM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>> wrote:
>
> Thanks, it looks like all of the information went in. I'll be posting the
> steps I used and references to the tickets I filed to get the import to
> work. I am disappointed that the saved searches can't sort on priority.
>
>
> On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <dave@brondsema.net
> <ma...@brondsema.net>> wrote:
>
> It might take a minute or two for search indexes to be updated. It
> looks like
> search includes your imported tickets now. Also, the API endpoint at
> https://sourceforge.net/rest/p/fll-sw/issues just lists a little bit of
> info for
> each ticket. If you want an API endpoint for full details on a ticket,
> just add
> the number to the URL like: https://sourceforge.net/rest/p/fll-sw/issues/1
>
> On 3/26/13 7:24 PM, Jon Schewe wrote:
> > Wait, I spoke too soon. In my email came a link to the ticket and that
> shows
> > more information.
> > https://sourceforge.net/p/fll-sw/issues/1/
> >
> >
> > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > OK, I hacked up a fix that creates a new hash for the document to
> import:
> > doc_import={}
> > doc_import['trackers'] = {}
> > doc_import['trackers']['default'] = {}
> > doc_import['trackers']['default']['artifacts'] =
> [ticket_in]
> >
> > Now I can import a ticket. I can see it
> > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > at
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> >
> > It also looks like most of the information didn't get imported.
> That's not
> > going to be very helpful. This is the raw JSON for the ticket that was
> > imported. I would have expected the comments, milestone, status,
> submitter
> > to make it in.
> > {
> > "assigned_to": "jpschewe",
> > "cc": "",
> > "class": "ARTIFACT",
> > "comments": [
> > {
> > "class": "COMMENT",
> > "comment": " * **milestone** set to _Parking Lot_\n\n",
> > "date": "2010-10-02T21:41:54Z",
> > "submitter": "jpschewe"
> > },
> > {
> > "class": "COMMENT",
> > "comment": " * **owner** set to _jpschewe_\n *
> **status** changed
> > from _new_ to _accepted_\n\n",
> > "date": "2010-10-02T21:51:55Z",
> > "submitter": "jpschewe"
> > },
> > {
> > "class": "COMMENT",
> > "comment": " * **status** changed from _accepted_ to
> _closed_\n *
> > **resolution** set to _invalid_\n * **component** set to
> _General_\n\n",
> > "date": "2010-10-02T22:58:37Z",
> > "submitter": "jpschewe"
> > }
> > ],
> > "component": "General",
> > "date": "2010-09-21T01:18:00Z",
> > "date_updated": "2010-10-02T22:58:37Z",
> > "description": "testing MyLyn",
> > "id": 1,
> > "keywords": "",
> > "milestone": "Parking Lot",
> > "priority": "major",
> > "resolution": "invalid",
> > "status": "closed",
> > "submitter": "jpschewe",
> > "summary": "test ticket",
> > "type": "defect"
> > }
> >
> >
> >
> > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > Looks like tickets_in should be set to doc in my case.
> Although line 80
> > is now giving me problems as it looks like you're trying to
> reuse the
> > JSON document to submit and it's not working because it's not
> formatted
> > as expected.
> >
> >
> > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > So far it's going poorly:
> >
> > Traceback (most recent call last):
> > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 123, in <module>
> > main()
> > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 51, in main
> > verbose=options.verbose)
> > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 69, in import_tracker
> > tickets_in = doc['trackers']['default']['artifacts']
> > TypeError: list indices must be integers, not str
> >
> > File to import is attached.
> >
> >
> >
> > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> <jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > I'll try. Should I post them back to the list?
> >
> >
> > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> <rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>>> wrote:
> >
> > So, I see you've got a new ticket open about this,
> which
> > seems to indicate that you're making progress. I was
> > wondering if we could persuade you to take really
> good notes
> > and produce some docs of how this process works?
> >
> > --Rich
> >
> > On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
> >
> >> Things have settled down on my project a bit now,
> so I've
> >> gone ahead with the migration. I haven't migrated the
> >> tickets yet because the code link is broken. If
> anyone has
> >> any insight into this, it would be much appreciated.
> >> https://sourceforge.net/p/allura/tickets/5844/
> >>
> >> Once this is resolved I'll try the ticket import.
> >>
> >>
> >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> >> <rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> wrote:
> >>
> >>
> >> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
> >>
> >>> I'm not sure how I would go about creating a
> test
> >>> project on SourceForge. I'm not setting up
> my own
> >>> Allura instance, I'm using the one on
> SourceForge.
> >>>
> >>
> >> Go to http://sf.net/create and click the
> Create Your
> >> Project button. That'll get you started.
> >>
> >> --
> >> Rich Bowen
> >> rbowen@rcbowen.com
> <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>> :: @rbowen
> >> rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> http://mtu.net/~jpschewe
> >>
> >
> > --
> > Rich Bowen
> > rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>> :: @rbowen
> > rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
Here are my notes that I used to track my progress doing this migration. I
needed to make some changes to allura_import.py, those changes are
reflected in the pull request for allura ticket 6020. One big downside to
the new tracker is the lack of ability to sort the saved search results by
priority.
Some python modules needed to be installed, but I don't remember which ones
beyond the following:
* python-paste
Steps
* notify developers of the potential migration
* Migrate the wiki manually - there are some scripts on gist to help wi
th this, although I didn't end up using them.
* <https://gist.github.com/619537>
* <https://gist.github.com/1286682>
* Update website redirection.
* Notify all developers of the migration.
* Remove ticket write permissions
* Start migration.
* Use `~/src/allura-git/scripts/trac_export.py` to export the tickets to
allura-import.json
* ./scripts/trac_export.py --no-attachments -o
~/projects/fll-sw/allura-import.json --only-tickets -v
https://sourceforge.net/apps/trac/fll-sw/
* Keep repeating this until it doesn't fail, it seems to timeout quite
a bit
* Request import API key
* Use `~/src/allura-git/scripts/allura_import.py` with `user_map.json`
and allura-import.json to import tickets
* PYTHONPATH=~/src/allura-git/Allura
* export PYTHONPATH
* python ~/src/allura-git/scripts/allura_import.py \
-a API \
-s SECRET \
-p fll-sw \
-t issues \
-u https://sourceforge.net \
--user-map=user_map.json \
--verbose \
allura-import.json
* Manually add milestones
* Manually pull the attachments for tickets.
* worked from trac files backup, didn't have many so manually worked
* Update wiki documentation for where to file bugs
* Notify developers
On Wed, Mar 27, 2013 at 10:48 AM, Jon Schewe <jp...@mtu.net> wrote:
> Thanks, it looks like all of the information went in. I'll be posting the
> steps I used and references to the tickets I filed to get the import to
> work. I am disappointed that the saved searches can't sort on priority.
>
>
> On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <da...@brondsema.net>wrote:
>
>> It might take a minute or two for search indexes to be updated. It looks
>> like
>> search includes your imported tickets now. Also, the API endpoint at
>> https://sourceforge.net/rest/p/fll-sw/issues just lists a little bit of
>> info for
>> each ticket. If you want an API endpoint for full details on a ticket,
>> just add
>> the number to the URL like:
>> https://sourceforge.net/rest/p/fll-sw/issues/1
>>
>> On 3/26/13 7:24 PM, Jon Schewe wrote:
>> > Wait, I spoke too soon. In my email came a link to the ticket and that
>> shows
>> > more information.
>> > https://sourceforge.net/p/fll-sw/issues/1/
>> >
>> >
>> > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
>> > <ma...@mtu.net>> wrote:
>> >
>> > OK, I hacked up a fix that creates a new hash for the document to
>> import:
>> > doc_import={}
>> > doc_import['trackers'] = {}
>> > doc_import['trackers']['default'] = {}
>> > doc_import['trackers']['default']['artifacts'] =
>> [ticket_in]
>> >
>> > Now I can import a ticket. I can see it
>> > at https://sourceforge.net/rest/p/fll-sw/issues, but not
>> > at
>> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
>> >
>> > It also looks like most of the information didn't get imported.
>> That's not
>> > going to be very helpful. This is the raw JSON for the ticket that
>> was
>> > imported. I would have expected the comments, milestone, status,
>> submitter
>> > to make it in.
>> > {
>> > "assigned_to": "jpschewe",
>> > "cc": "",
>> > "class": "ARTIFACT",
>> > "comments": [
>> > {
>> > "class": "COMMENT",
>> > "comment": " * **milestone** set to _Parking Lot_\n\n",
>> > "date": "2010-10-02T21:41:54Z",
>> > "submitter": "jpschewe"
>> > },
>> > {
>> > "class": "COMMENT",
>> > "comment": " * **owner** set to _jpschewe_\n * **status**
>> changed
>> > from _new_ to _accepted_\n\n",
>> > "date": "2010-10-02T21:51:55Z",
>> > "submitter": "jpschewe"
>> > },
>> > {
>> > "class": "COMMENT",
>> > "comment": " * **status** changed from _accepted_ to
>> _closed_\n *
>> > **resolution** set to _invalid_\n * **component** set to
>> _General_\n\n",
>> > "date": "2010-10-02T22:58:37Z",
>> > "submitter": "jpschewe"
>> > }
>> > ],
>> > "component": "General",
>> > "date": "2010-09-21T01:18:00Z",
>> > "date_updated": "2010-10-02T22:58:37Z",
>> > "description": "testing MyLyn",
>> > "id": 1,
>> > "keywords": "",
>> > "milestone": "Parking Lot",
>> > "priority": "major",
>> > "resolution": "invalid",
>> > "status": "closed",
>> > "submitter": "jpschewe",
>> > "summary": "test ticket",
>> > "type": "defect"
>> > }
>> >
>> >
>> >
>> > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jpschewe@mtu.net
>> > <ma...@mtu.net>> wrote:
>> >
>> > Looks like tickets_in should be set to doc in my case. Although
>> line 80
>> > is now giving me problems as it looks like you're trying to
>> reuse the
>> > JSON document to submit and it's not working because it's not
>> formatted
>> > as expected.
>> >
>> >
>> > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jpschewe@mtu.net
>> > <ma...@mtu.net>> wrote:
>> >
>> > So far it's going poorly:
>> >
>> > Traceback (most recent call last):
>> > File
>> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
>> > line 123, in <module>
>> > main()
>> > File
>> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
>> > line 51, in main
>> > verbose=options.verbose)
>> > File
>> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
>> > line 69, in import_tracker
>> > tickets_in = doc['trackers']['default']['artifacts']
>> > TypeError: list indices must be integers, not str
>> >
>> > File to import is attached.
>> >
>> >
>> >
>> > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <
>> jpschewe@mtu.net
>> > <ma...@mtu.net>> wrote:
>> >
>> > I'll try. Should I post them back to the list?
>> >
>> >
>> > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <
>> rbowen@rcbowen.com
>> > <ma...@rcbowen.com>> wrote:
>> >
>> > So, I see you've got a new ticket open about this,
>> which
>> > seems to indicate that you're making progress. I was
>> > wondering if we could persuade you to take really
>> good notes
>> > and produce some docs of how this process works?
>> >
>> > --Rich
>> >
>> > On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>> >
>> >> Things have settled down on my project a bit now,
>> so I've
>> >> gone ahead with the migration. I haven't migrated
>> the
>> >> tickets yet because the code link is broken. If
>> anyone has
>> >> any insight into this, it would be much
>> appreciated.
>> >> https://sourceforge.net/p/allura/tickets/5844/
>> >>
>> >> Once this is resolved I'll try the ticket import.
>> >>
>> >>
>> >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
>> >> <rbowen@rcbowen.com <ma...@rcbowen.com>>
>> wrote:
>> >>
>> >>
>> >> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>> >>
>> >>> I'm not sure how I would go about creating a
>> test
>> >>> project on SourceForge. I'm not setting up my
>> own
>> >>> Allura instance, I'm using the one on
>> SourceForge.
>> >>>
>> >>
>> >> Go to http://sf.net/create and click the
>> Create Your
>> >> Project button. That'll get you started.
>> >>
>> >> --
>> >> Rich Bowen
>> >> rbowen@rcbowen.com <ma...@rcbowen.com>
>> :: @rbowen
>> >> rbowen@apache.org <ma...@apache.org>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> http://mtu.net/~jpschewe
>> >>
>> >
>> > --
>> > Rich Bowen
>> > rbowen@rcbowen.com <ma...@rcbowen.com> ::
>> @rbowen
>> > rbowen@apache.org <ma...@apache.org>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > http://mtu.net/~jpschewe
>> >
>> >
>> >
>> >
>> > --
>> > http://mtu.net/~jpschewe
>> >
>> >
>> >
>> >
>> > --
>> > http://mtu.net/~jpschewe
>> >
>> >
>> >
>> >
>> > --
>> > http://mtu.net/~jpschewe
>> >
>> >
>> >
>> >
>> > --
>> > http://mtu.net/~jpschewe
>> >
>>
>>
>>
>> --
>> Dave Brondsema : dave@brondsema.net
>> http://www.brondsema.net : personal
>> http://www.splike.com : programming
>> <><
>>
>
>
>
> --
> http://mtu.net/~jpschewe
>
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
The bulk edit worked well for me. I had 5 priorities and mapped them to 1-5
without any trouble. There could be some better user feedback, note that
it's working in the background or something like that. I wasn't sure if the
save button worked right away and I didn't see anything happing for about
30 seconds and then saw the updated message. Sometimes it gave me a message
and sometimes the page just reloaded.
On Mon, Apr 1, 2013 at 1:05 PM, Dave Brondsema <da...@brondsema.net> wrote:
> Three options come to mind, but you'll have to try them to see if they work
>
> 1) Do a ticket search for all tickets with priority X and then use bulk
> edit
> from that page to set a new priority. There might be bugs with bulk edit
> and
> custom fields though. https://sourceforge.net/p/allura/tickets/5673/reports a
> few issues
>
> 2) Use the regular (not import) API to set the priority fields.
> https://sourceforge.net/p/forge/documentation/Allura%20API/#tracker has
> docs. I
> don't know offhand how that API deals with data types
>
> 3) Make the import API handle different data types better, and do a fresh
> import. This would be nice for other people interested in doing imports,
> but
> would require some patches to Allura server-side, receiving the import
> data.
>
> On 3/29/13 2:25 PM, Jon Schewe wrote:
> > I don't suppose there's a way to batch convert all of my text priorities
> to
> > numbers is there?
> >
> >
> > On Fri, Mar 29, 2013 at 7:42 AM, Dave Brondsema <dave@brondsema.net
> > <ma...@brondsema.net>> wrote:
> >
> > To change the type of a field, go to Admin, Tools, Tickets - Field
> > Management.
> >
> > There's not a way to save a search with a default sort order. The
> > backend supports it, but when saving a search you can only specify
> the
> > criteria not the order. I can't find a ticket for that. I did find
> > https://sourceforge.net/p/allura/tickets/5758/ which is for the
> default
> > sort order (not a saved search) and
> > https://sourceforge.net/p/allura/tickets/5760/ which might affect
> you too.
> >
> > On 03/29/2013 07:53 AM, Jon Schewe wrote:
> > > How would I change the type of the column? I didn't create the
> column.
> > > My guess is that it came in from the Trac import. Once I do change
> the
> > > type, how do I save the sort with the search so that anyone
> viewing the
> > > search sees the same sort order by default?
> > >
> > >
> > > On Thu, Mar 28, 2013 at 4:17 PM, Dave Brondsema <
> dave@brondsema.net
> > <ma...@brondsema.net>
> > > <mailto:dave@brondsema.net <ma...@brondsema.net>>> wrote:
> > >
> > > Most fields can be added to the default list of columns shown,
> and
> > > then sorted
> > > on. It looks like your priority field is "text", which
> apparently
> > > Allura
> > > doesn't let you show in list view. Maybe you could try
> changing it
> > > to a select
> > > field? Or if you need it to be text, I think it'd be a
> reasonable
> > > enhancement
> > > to allow text fields to be shown as columns in list view
> > >
> > > On 3/27/13 11:48 AM, Jon Schewe wrote:
> > > > Thanks, it looks like all of the information went in. I'll be
> > > posting the steps
> > > > I used and references to the tickets I filed to get the
> import to
> > > work. I am
> > > > disappointed that the saved searches can't sort on priority.
> > > >
> > > >
> > > > On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema
> > > <dave@brondsema.net <ma...@brondsema.net>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>
> > > > <mailto:dave@brondsema.net <ma...@brondsema.net>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>>> wrote:
> > > >
> > > > It might take a minute or two for search indexes to be
> > > updated. It looks like
> > > > search includes your imported tickets now. Also, the API
> > > endpoint at
> > > > https://sourceforge.net/rest/p/fll-sw/issues just lists
> a
> > > little bit of info for
> > > > each ticket. If you want an API endpoint for full
> details on
> > > a ticket, just add
> > > > the number to the URL like:
> > > https://sourceforge.net/rest/p/fll-sw/issues/1
> > > >
> > > > On 3/26/13 7:24 PM, Jon Schewe wrote:
> > > > > Wait, I spoke too soon. In my email came a link to the
> > > ticket and that shows
> > > > > more information.
> > > > > https://sourceforge.net/p/fll-sw/issues/1/
> > > > >
> > > > >
> > > > > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe
> > > <jpschewe@mtu.net <ma...@mtu.net> <mailto:
> jpschewe@mtu.net
> > <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > > >
> > > > > OK, I hacked up a fix that creates a new hash for
> the
> > > document to import:
> > > > > doc_import={}
> > > > > doc_import['trackers'] = {}
> > > > > doc_import['trackers']['default'] = {}
> > > > >
> > > doc_import['trackers']['default']['artifacts'] = [ticket_in]
> > > > >
> > > > > Now I can import a ticket. I can see it
> > > > > at https://sourceforge.net/rest/p/fll-sw/issues,
> but not
> > > > > at
> > > >
> > >
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> > > > >
> > > > > It also looks like most of the information didn't
> get
> > > imported. That's not
> > > > > going to be very helpful. This is the raw JSON for
> the
> > > ticket that was
> > > > > imported. I would have expected the comments,
> milestone,
> > > status, submitter
> > > > > to make it in.
> > > > > {
> > > > > "assigned_to": "jpschewe",
> > > > > "cc": "",
> > > > > "class": "ARTIFACT",
> > > > > "comments": [
> > > > > {
> > > > > "class": "COMMENT",
> > > > > "comment": " * **milestone** set to
> _Parking
> > > Lot_\n\n",
> > > > > "date": "2010-10-02T21:41:54Z",
> > > > > "submitter": "jpschewe"
> > > > > },
> > > > > {
> > > > > "class": "COMMENT",
> > > > > "comment": " * **owner** set to
> _jpschewe_\n *
> > > **status**
> > > > changed
> > > > > from _new_ to _accepted_\n\n",
> > > > > "date": "2010-10-02T21:51:55Z",
> > > > > "submitter": "jpschewe"
> > > > > },
> > > > > {
> > > > > "class": "COMMENT",
> > > > > "comment": " * **status** changed from
> > > _accepted_ to
> > > > _closed_\n *
> > > > > **resolution** set to _invalid_\n * **component**
> set
> > > to _General_\n\n",
> > > > > "date": "2010-10-02T22:58:37Z",
> > > > > "submitter": "jpschewe"
> > > > > }
> > > > > ],
> > > > > "component": "General",
> > > > > "date": "2010-09-21T01:18:00Z",
> > > > > "date_updated": "2010-10-02T22:58:37Z",
> > > > > "description": "testing MyLyn",
> > > > > "id": 1,
> > > > > "keywords": "",
> > > > > "milestone": "Parking Lot",
> > > > > "priority": "major",
> > > > > "resolution": "invalid",
> > > > > "status": "closed",
> > > > > "submitter": "jpschewe",
> > > > > "summary": "test ticket",
> > > > > "type": "defect"
> > > > > }
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe
> > > <jpschewe@mtu.net <ma...@mtu.net> <mailto:
> jpschewe@mtu.net
> > <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > > >
> > > > > Looks like tickets_in should be set to doc in
> my
> > > case. Although
> > > > line 80
> > > > > is now giving me problems as it looks like
> you're
> > > trying to reuse the
> > > > > JSON document to submit and it's not working
> because
> > > it's not
> > > > formatted
> > > > > as expected.
> > > > >
> > > > >
> > > > > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe
> > > <jpschewe@mtu.net <ma...@mtu.net> <mailto:
> jpschewe@mtu.net
> > <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > > <mailto:jpschewe@mtu.net <mailto:
> jpschewe@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > > >
> > > > > So far it's going poorly:
> > > > >
> > > > > Traceback (most recent call last):
> > > > > File
> > > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > > line 123, in <module>
> > > > > main()
> > > > > File
> > > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > > line 51, in main
> > > > > verbose=options.verbose)
> > > > > File
> > > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > > line 69, in import_tracker
> > > > > tickets_in =
> > > doc['trackers']['default']['artifacts']
> > > > > TypeError: list indices must be integers,
> not str
> > > > >
> > > > > File to import is attached.
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> > > <jpschewe@mtu.net <ma...@mtu.net> <mailto:
> jpschewe@mtu.net
> > <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > > <mailto:jpschewe@mtu.net <mailto:
> jpschewe@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > > >
> > > > > I'll try. Should I post them back to
> the list?
> > > > >
> > > > >
> > > > > On Mon, Mar 25, 2013 at 9:54 AM, Rich
> Bowen
> > > > <rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > > > <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>>>
> > > > wrote:
> > > > >
> > > > > So, I see you've got a new ticket
> open
> > > about this, which
> > > > > seems to indicate that you're
> making
> > > progress. I was
> > > > > wondering if we could persuade you
> to
> > > take really good
> > > > notes
> > > > > and produce some docs of how this
> > > process works?
> > > > >
> > > > > --Rich
> > > > >
> > > > > On Feb 23, 2013, at 4:53 PM, Jon
> Schewe
> > > wrote:
> > > > >
> > > > >> Things have settled down on my
> project
> > > a bit now, so I've
> > > > >> gone ahead with the migration. I
> > > haven't migrated the
> > > > >> tickets yet because the code link
> is
> > > broken. If
> > > > anyone has
> > > > >> any insight into this, it would
> be much
> > > appreciated.
> > > > >>
> > > https://sourceforge.net/p/allura/tickets/5844/
> > > > >>
> > > > >> Once this is resolved I'll try the
> > > ticket import.
> > > > >>
> > > > >>
> > > > >> On Wed, Dec 5, 2012 at 2:41 PM,
> Rich Bowen
> > > > >> <rbowen@rcbowen.com
> > <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>>> wrote:
> > > > >>
> > > > >>
> > > > >> On Dec 5, 2012, at 3:17 PM,
> Jon
> > > Schewe wrote:
> > > > >>
> > > > >>> I'm not sure how I would go
> about
> > > creating a test
> > > > >>> project on SourceForge. I'm
> not
> > > setting up my own
> > > > >>> Allura instance, I'm using
> the one
> > > on SourceForge.
> > > > >>>
> > > > >>
> > > > >> Go to http://sf.net/createand
> > > click the Create Your
> > > > >> Project button. That'll get
> you
> > > started.
> > > > >>
> > > > >> --
> > > > >> Rich Bowen
> > > > >> rbowen@rcbowen.com
> > <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>> :: @rbowen
> > > > >> rbowen@apache.org
> > <ma...@apache.org>
> > > <mailto:rbowen@apache.org <ma...@apache.org>>
> > <mailto:rbowen@apache.org <ma...@apache.org>
> > > <mailto:rbowen@apache.org <ma...@apache.org>>>
> > > > <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> > > <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>>>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> http://mtu.net/~jpschewe
> > > > >>
> > > > >
> > > > > --
> > > > > Rich Bowen
> > > > > rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>> :: @rbowen
> > > > > rbowen@apache.org <mailto:
> rbowen@apache.org>
> > > <mailto:rbowen@apache.org <ma...@apache.org>>
> > <mailto:rbowen@apache.org <ma...@apache.org>
> > > <mailto:rbowen@apache.org <ma...@apache.org>>>
> > > > <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> > > <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>>>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > http://mtu.net/~jpschewe
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > http://mtu.net/~jpschewe
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > http://mtu.net/~jpschewe
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > http://mtu.net/~jpschewe
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > http://mtu.net/~jpschewe
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Dave Brondsema : dave@brondsema.net <mailto:
> dave@brondsema.net>
> > > <mailto:dave@brondsema.net <ma...@brondsema.net>>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>
> > > <mailto:dave@brondsema.net <ma...@brondsema.net>>>
> > > > http://www.brondsema.net : personal
> > > > http://www.splike.com : programming
> > > > <><
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > >
> > >
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net <mailto:dave@brondsema.net
> >
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > > <><
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Dave Brondsema <da...@brondsema.net>.
Three options come to mind, but you'll have to try them to see if they work
1) Do a ticket search for all tickets with priority X and then use bulk edit
from that page to set a new priority. There might be bugs with bulk edit and
custom fields though. https://sourceforge.net/p/allura/tickets/5673/ reports a
few issues
2) Use the regular (not import) API to set the priority fields.
https://sourceforge.net/p/forge/documentation/Allura%20API/#tracker has docs. I
don't know offhand how that API deals with data types
3) Make the import API handle different data types better, and do a fresh
import. This would be nice for other people interested in doing imports, but
would require some patches to Allura server-side, receiving the import data.
On 3/29/13 2:25 PM, Jon Schewe wrote:
> I don't suppose there's a way to batch convert all of my text priorities to
> numbers is there?
>
>
> On Fri, Mar 29, 2013 at 7:42 AM, Dave Brondsema <dave@brondsema.net
> <ma...@brondsema.net>> wrote:
>
> To change the type of a field, go to Admin, Tools, Tickets - Field
> Management.
>
> There's not a way to save a search with a default sort order. The
> backend supports it, but when saving a search you can only specify the
> criteria not the order. I can't find a ticket for that. I did find
> https://sourceforge.net/p/allura/tickets/5758/ which is for the default
> sort order (not a saved search) and
> https://sourceforge.net/p/allura/tickets/5760/ which might affect you too.
>
> On 03/29/2013 07:53 AM, Jon Schewe wrote:
> > How would I change the type of the column? I didn't create the column.
> > My guess is that it came in from the Trac import. Once I do change the
> > type, how do I save the sort with the search so that anyone viewing the
> > search sees the same sort order by default?
> >
> >
> > On Thu, Mar 28, 2013 at 4:17 PM, Dave Brondsema <dave@brondsema.net
> <ma...@brondsema.net>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>> wrote:
> >
> > Most fields can be added to the default list of columns shown, and
> > then sorted
> > on. It looks like your priority field is "text", which apparently
> > Allura
> > doesn't let you show in list view. Maybe you could try changing it
> > to a select
> > field? Or if you need it to be text, I think it'd be a reasonable
> > enhancement
> > to allow text fields to be shown as columns in list view
> >
> > On 3/27/13 11:48 AM, Jon Schewe wrote:
> > > Thanks, it looks like all of the information went in. I'll be
> > posting the steps
> > > I used and references to the tickets I filed to get the import to
> > work. I am
> > > disappointed that the saved searches can't sort on priority.
> > >
> > >
> > > On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema
> > <dave@brondsema.net <ma...@brondsema.net>
> <mailto:dave@brondsema.net <ma...@brondsema.net>>
> > > <mailto:dave@brondsema.net <ma...@brondsema.net>
> <mailto:dave@brondsema.net <ma...@brondsema.net>>>> wrote:
> > >
> > > It might take a minute or two for search indexes to be
> > updated. It looks like
> > > search includes your imported tickets now. Also, the API
> > endpoint at
> > > https://sourceforge.net/rest/p/fll-sw/issues just lists a
> > little bit of info for
> > > each ticket. If you want an API endpoint for full details on
> > a ticket, just add
> > > the number to the URL like:
> > https://sourceforge.net/rest/p/fll-sw/issues/1
> > >
> > > On 3/26/13 7:24 PM, Jon Schewe wrote:
> > > > Wait, I spoke too soon. In my email came a link to the
> > ticket and that shows
> > > > more information.
> > > > https://sourceforge.net/p/fll-sw/issues/1/
> > > >
> > > >
> > > > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net> <mailto:jpschewe@mtu.net
> <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > >
> > > > OK, I hacked up a fix that creates a new hash for the
> > document to import:
> > > > doc_import={}
> > > > doc_import['trackers'] = {}
> > > > doc_import['trackers']['default'] = {}
> > > >
> > doc_import['trackers']['default']['artifacts'] = [ticket_in]
> > > >
> > > > Now I can import a ticket. I can see it
> > > > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > > > at
> > >
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> > > >
> > > > It also looks like most of the information didn't get
> > imported. That's not
> > > > going to be very helpful. This is the raw JSON for the
> > ticket that was
> > > > imported. I would have expected the comments, milestone,
> > status, submitter
> > > > to make it in.
> > > > {
> > > > "assigned_to": "jpschewe",
> > > > "cc": "",
> > > > "class": "ARTIFACT",
> > > > "comments": [
> > > > {
> > > > "class": "COMMENT",
> > > > "comment": " * **milestone** set to _Parking
> > Lot_\n\n",
> > > > "date": "2010-10-02T21:41:54Z",
> > > > "submitter": "jpschewe"
> > > > },
> > > > {
> > > > "class": "COMMENT",
> > > > "comment": " * **owner** set to _jpschewe_\n *
> > **status**
> > > changed
> > > > from _new_ to _accepted_\n\n",
> > > > "date": "2010-10-02T21:51:55Z",
> > > > "submitter": "jpschewe"
> > > > },
> > > > {
> > > > "class": "COMMENT",
> > > > "comment": " * **status** changed from
> > _accepted_ to
> > > _closed_\n *
> > > > **resolution** set to _invalid_\n * **component** set
> > to _General_\n\n",
> > > > "date": "2010-10-02T22:58:37Z",
> > > > "submitter": "jpschewe"
> > > > }
> > > > ],
> > > > "component": "General",
> > > > "date": "2010-09-21T01:18:00Z",
> > > > "date_updated": "2010-10-02T22:58:37Z",
> > > > "description": "testing MyLyn",
> > > > "id": 1,
> > > > "keywords": "",
> > > > "milestone": "Parking Lot",
> > > > "priority": "major",
> > > > "resolution": "invalid",
> > > > "status": "closed",
> > > > "submitter": "jpschewe",
> > > > "summary": "test ticket",
> > > > "type": "defect"
> > > > }
> > > >
> > > >
> > > >
> > > > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net> <mailto:jpschewe@mtu.net
> <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > >
> > > > Looks like tickets_in should be set to doc in my
> > case. Although
> > > line 80
> > > > is now giving me problems as it looks like you're
> > trying to reuse the
> > > > JSON document to submit and it's not working because
> > it's not
> > > formatted
> > > > as expected.
> > > >
> > > >
> > > > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net> <mailto:jpschewe@mtu.net
> <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > >
> > > > So far it's going poorly:
> > > >
> > > > Traceback (most recent call last):
> > > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > line 123, in <module>
> > > > main()
> > > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > line 51, in main
> > > > verbose=options.verbose)
> > > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > line 69, in import_tracker
> > > > tickets_in =
> > doc['trackers']['default']['artifacts']
> > > > TypeError: list indices must be integers, not str
> > > >
> > > > File to import is attached.
> > > >
> > > >
> > > >
> > > > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net> <mailto:jpschewe@mtu.net
> <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>>> wrote:
> > > >
> > > > I'll try. Should I post them back to the list?
> > > >
> > > >
> > > > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> > > <rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > > <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>>>
> > > wrote:
> > > >
> > > > So, I see you've got a new ticket open
> > about this, which
> > > > seems to indicate that you're making
> > progress. I was
> > > > wondering if we could persuade you to
> > take really good
> > > notes
> > > > and produce some docs of how this
> > process works?
> > > >
> > > > --Rich
> > > >
> > > > On Feb 23, 2013, at 4:53 PM, Jon Schewe
> > wrote:
> > > >
> > > >> Things have settled down on my project
> > a bit now, so I've
> > > >> gone ahead with the migration. I
> > haven't migrated the
> > > >> tickets yet because the code link is
> > broken. If
> > > anyone has
> > > >> any insight into this, it would be much
> > appreciated.
> > > >>
> > https://sourceforge.net/p/allura/tickets/5844/
> > > >>
> > > >> Once this is resolved I'll try the
> > ticket import.
> > > >>
> > > >>
> > > >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> > > >> <rbowen@rcbowen.com
> <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>>> wrote:
> > > >>
> > > >>
> > > >> On Dec 5, 2012, at 3:17 PM, Jon
> > Schewe wrote:
> > > >>
> > > >>> I'm not sure how I would go about
> > creating a test
> > > >>> project on SourceForge. I'm not
> > setting up my own
> > > >>> Allura instance, I'm using the one
> > on SourceForge.
> > > >>>
> > > >>
> > > >> Go to http://sf.net/create and
> > click the Create Your
> > > >> Project button. That'll get you
> > started.
> > > >>
> > > >> --
> > > >> Rich Bowen
> > > >> rbowen@rcbowen.com
> <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>> :: @rbowen
> > > >> rbowen@apache.org
> <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>>
> > > <mailto:rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>
> > <mailto:rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>>>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> http://mtu.net/~jpschewe
> > > >>
> > > >
> > > > --
> > > > Rich Bowen
> > > > rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>> :: @rbowen
> > > > rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>>
> > > <mailto:rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>
> > <mailto:rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>>>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > >
> > >
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>
> <mailto:dave@brondsema.net <ma...@brondsema.net>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>>
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > > <><
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> <mailto:dave@brondsema.net <ma...@brondsema.net>>
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
> --
> Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
I don't suppose there's a way to batch convert all of my text priorities to
numbers is there?
On Fri, Mar 29, 2013 at 7:42 AM, Dave Brondsema <da...@brondsema.net> wrote:
> To change the type of a field, go to Admin, Tools, Tickets - Field
> Management.
>
> There's not a way to save a search with a default sort order. The
> backend supports it, but when saving a search you can only specify the
> criteria not the order. I can't find a ticket for that. I did find
> https://sourceforge.net/p/allura/tickets/5758/ which is for the default
> sort order (not a saved search) and
> https://sourceforge.net/p/allura/tickets/5760/ which might affect you too.
>
> On 03/29/2013 07:53 AM, Jon Schewe wrote:
> > How would I change the type of the column? I didn't create the column.
> > My guess is that it came in from the Trac import. Once I do change the
> > type, how do I save the sort with the search so that anyone viewing the
> > search sees the same sort order by default?
> >
> >
> > On Thu, Mar 28, 2013 at 4:17 PM, Dave Brondsema <dave@brondsema.net
> > <ma...@brondsema.net>> wrote:
> >
> > Most fields can be added to the default list of columns shown, and
> > then sorted
> > on. It looks like your priority field is "text", which apparently
> > Allura
> > doesn't let you show in list view. Maybe you could try changing it
> > to a select
> > field? Or if you need it to be text, I think it'd be a reasonable
> > enhancement
> > to allow text fields to be shown as columns in list view
> >
> > On 3/27/13 11:48 AM, Jon Schewe wrote:
> > > Thanks, it looks like all of the information went in. I'll be
> > posting the steps
> > > I used and references to the tickets I filed to get the import to
> > work. I am
> > > disappointed that the saved searches can't sort on priority.
> > >
> > >
> > > On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema
> > <dave@brondsema.net <ma...@brondsema.net>
> > > <mailto:dave@brondsema.net <ma...@brondsema.net>>> wrote:
> > >
> > > It might take a minute or two for search indexes to be
> > updated. It looks like
> > > search includes your imported tickets now. Also, the API
> > endpoint at
> > > https://sourceforge.net/rest/p/fll-sw/issues just lists a
> > little bit of info for
> > > each ticket. If you want an API endpoint for full details on
> > a ticket, just add
> > > the number to the URL like:
> > https://sourceforge.net/rest/p/fll-sw/issues/1
> > >
> > > On 3/26/13 7:24 PM, Jon Schewe wrote:
> > > > Wait, I spoke too soon. In my email came a link to the
> > ticket and that shows
> > > > more information.
> > > > https://sourceforge.net/p/fll-sw/issues/1/
> > > >
> > > >
> > > > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>> wrote:
> > > >
> > > > OK, I hacked up a fix that creates a new hash for the
> > document to import:
> > > > doc_import={}
> > > > doc_import['trackers'] = {}
> > > > doc_import['trackers']['default'] = {}
> > > >
> > doc_import['trackers']['default']['artifacts'] = [ticket_in]
> > > >
> > > > Now I can import a ticket. I can see it
> > > > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > > > at
> > >
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> > > >
> > > > It also looks like most of the information didn't get
> > imported. That's not
> > > > going to be very helpful. This is the raw JSON for the
> > ticket that was
> > > > imported. I would have expected the comments, milestone,
> > status, submitter
> > > > to make it in.
> > > > {
> > > > "assigned_to": "jpschewe",
> > > > "cc": "",
> > > > "class": "ARTIFACT",
> > > > "comments": [
> > > > {
> > > > "class": "COMMENT",
> > > > "comment": " * **milestone** set to _Parking
> > Lot_\n\n",
> > > > "date": "2010-10-02T21:41:54Z",
> > > > "submitter": "jpschewe"
> > > > },
> > > > {
> > > > "class": "COMMENT",
> > > > "comment": " * **owner** set to _jpschewe_\n *
> > **status**
> > > changed
> > > > from _new_ to _accepted_\n\n",
> > > > "date": "2010-10-02T21:51:55Z",
> > > > "submitter": "jpschewe"
> > > > },
> > > > {
> > > > "class": "COMMENT",
> > > > "comment": " * **status** changed from
> > _accepted_ to
> > > _closed_\n *
> > > > **resolution** set to _invalid_\n * **component** set
> > to _General_\n\n",
> > > > "date": "2010-10-02T22:58:37Z",
> > > > "submitter": "jpschewe"
> > > > }
> > > > ],
> > > > "component": "General",
> > > > "date": "2010-09-21T01:18:00Z",
> > > > "date_updated": "2010-10-02T22:58:37Z",
> > > > "description": "testing MyLyn",
> > > > "id": 1,
> > > > "keywords": "",
> > > > "milestone": "Parking Lot",
> > > > "priority": "major",
> > > > "resolution": "invalid",
> > > > "status": "closed",
> > > > "submitter": "jpschewe",
> > > > "summary": "test ticket",
> > > > "type": "defect"
> > > > }
> > > >
> > > >
> > > >
> > > > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>> wrote:
> > > >
> > > > Looks like tickets_in should be set to doc in my
> > case. Although
> > > line 80
> > > > is now giving me problems as it looks like you're
> > trying to reuse the
> > > > JSON document to submit and it's not working because
> > it's not
> > > formatted
> > > > as expected.
> > > >
> > > >
> > > > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>> wrote:
> > > >
> > > > So far it's going poorly:
> > > >
> > > > Traceback (most recent call last):
> > > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > line 123, in <module>
> > > > main()
> > > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > line 51, in main
> > > > verbose=options.verbose)
> > > > File
> > "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > > line 69, in import_tracker
> > > > tickets_in =
> > doc['trackers']['default']['artifacts']
> > > > TypeError: list indices must be integers, not str
> > > >
> > > > File to import is attached.
> > > >
> > > >
> > > >
> > > > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> > <jpschewe@mtu.net <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > > <mailto:jpschewe@mtu.net
> > <ma...@mtu.net> <mailto:jpschewe@mtu.net
> > <ma...@mtu.net>>>> wrote:
> > > >
> > > > I'll try. Should I post them back to the
> list?
> > > >
> > > >
> > > > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> > > <rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > > > <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>>>>
> > > wrote:
> > > >
> > > > So, I see you've got a new ticket open
> > about this, which
> > > > seems to indicate that you're making
> > progress. I was
> > > > wondering if we could persuade you to
> > take really good
> > > notes
> > > > and produce some docs of how this
> > process works?
> > > >
> > > > --Rich
> > > >
> > > > On Feb 23, 2013, at 4:53 PM, Jon Schewe
> > wrote:
> > > >
> > > >> Things have settled down on my project
> > a bit now, so I've
> > > >> gone ahead with the migration. I
> > haven't migrated the
> > > >> tickets yet because the code link is
> > broken. If
> > > anyone has
> > > >> any insight into this, it would be much
> > appreciated.
> > > >>
> > https://sourceforge.net/p/allura/tickets/5844/
> > > >>
> > > >> Once this is resolved I'll try the
> > ticket import.
> > > >>
> > > >>
> > > >> On Wed, Dec 5, 2012 at 2:41 PM, Rich
> Bowen
> > > >> <rbowen@rcbowen.com
> > <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>> wrote:
> > > >>
> > > >>
> > > >> On Dec 5, 2012, at 3:17 PM, Jon
> > Schewe wrote:
> > > >>
> > > >>> I'm not sure how I would go about
> > creating a test
> > > >>> project on SourceForge. I'm not
> > setting up my own
> > > >>> Allura instance, I'm using the one
> > on SourceForge.
> > > >>>
> > > >>
> > > >> Go to http://sf.net/create and
> > click the Create Your
> > > >> Project button. That'll get you
> > started.
> > > >>
> > > >> --
> > > >> Rich Bowen
> > > >> rbowen@rcbowen.com
> > <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> :: @rbowen
> > > >> rbowen@apache.org
> > <ma...@apache.org> <mailto:rbowen@apache.org
> > <ma...@apache.org>>
> > > <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> http://mtu.net/~jpschewe
> > > >>
> > > >
> > > > --
> > > > Rich Bowen
> > > > rbowen@rcbowen.com
> > <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> > <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> :: @rbowen
> > > > rbowen@apache.org
> > <ma...@apache.org> <mailto:rbowen@apache.org
> > <ma...@apache.org>>
> > > <mailto:rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > http://mtu.net/~jpschewe
> > > >
> > >
> > >
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net
> > <ma...@brondsema.net> <mailto:dave@brondsema.net
> > <ma...@brondsema.net>>
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > > <><
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Dave Brondsema <da...@brondsema.net>.
To change the type of a field, go to Admin, Tools, Tickets - Field
Management.
There's not a way to save a search with a default sort order. The
backend supports it, but when saving a search you can only specify the
criteria not the order. I can't find a ticket for that. I did find
https://sourceforge.net/p/allura/tickets/5758/ which is for the default
sort order (not a saved search) and
https://sourceforge.net/p/allura/tickets/5760/ which might affect you too.
On 03/29/2013 07:53 AM, Jon Schewe wrote:
> How would I change the type of the column? I didn't create the column.
> My guess is that it came in from the Trac import. Once I do change the
> type, how do I save the sort with the search so that anyone viewing the
> search sees the same sort order by default?
>
>
> On Thu, Mar 28, 2013 at 4:17 PM, Dave Brondsema <dave@brondsema.net
> <ma...@brondsema.net>> wrote:
>
> Most fields can be added to the default list of columns shown, and
> then sorted
> on. It looks like your priority field is "text", which apparently
> Allura
> doesn't let you show in list view. Maybe you could try changing it
> to a select
> field? Or if you need it to be text, I think it'd be a reasonable
> enhancement
> to allow text fields to be shown as columns in list view
>
> On 3/27/13 11:48 AM, Jon Schewe wrote:
> > Thanks, it looks like all of the information went in. I'll be
> posting the steps
> > I used and references to the tickets I filed to get the import to
> work. I am
> > disappointed that the saved searches can't sort on priority.
> >
> >
> > On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema
> <dave@brondsema.net <ma...@brondsema.net>
> > <mailto:dave@brondsema.net <ma...@brondsema.net>>> wrote:
> >
> > It might take a minute or two for search indexes to be
> updated. It looks like
> > search includes your imported tickets now. Also, the API
> endpoint at
> > https://sourceforge.net/rest/p/fll-sw/issues just lists a
> little bit of info for
> > each ticket. If you want an API endpoint for full details on
> a ticket, just add
> > the number to the URL like:
> https://sourceforge.net/rest/p/fll-sw/issues/1
> >
> > On 3/26/13 7:24 PM, Jon Schewe wrote:
> > > Wait, I spoke too soon. In my email came a link to the
> ticket and that shows
> > > more information.
> > > https://sourceforge.net/p/fll-sw/issues/1/
> > >
> > >
> > > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe
> <jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>> wrote:
> > >
> > > OK, I hacked up a fix that creates a new hash for the
> document to import:
> > > doc_import={}
> > > doc_import['trackers'] = {}
> > > doc_import['trackers']['default'] = {}
> > >
> doc_import['trackers']['default']['artifacts'] = [ticket_in]
> > >
> > > Now I can import a ticket. I can see it
> > > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > > at
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> > >
> > > It also looks like most of the information didn't get
> imported. That's not
> > > going to be very helpful. This is the raw JSON for the
> ticket that was
> > > imported. I would have expected the comments, milestone,
> status, submitter
> > > to make it in.
> > > {
> > > "assigned_to": "jpschewe",
> > > "cc": "",
> > > "class": "ARTIFACT",
> > > "comments": [
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **milestone** set to _Parking
> Lot_\n\n",
> > > "date": "2010-10-02T21:41:54Z",
> > > "submitter": "jpschewe"
> > > },
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **owner** set to _jpschewe_\n *
> **status**
> > changed
> > > from _new_ to _accepted_\n\n",
> > > "date": "2010-10-02T21:51:55Z",
> > > "submitter": "jpschewe"
> > > },
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **status** changed from
> _accepted_ to
> > _closed_\n *
> > > **resolution** set to _invalid_\n * **component** set
> to _General_\n\n",
> > > "date": "2010-10-02T22:58:37Z",
> > > "submitter": "jpschewe"
> > > }
> > > ],
> > > "component": "General",
> > > "date": "2010-09-21T01:18:00Z",
> > > "date_updated": "2010-10-02T22:58:37Z",
> > > "description": "testing MyLyn",
> > > "id": 1,
> > > "keywords": "",
> > > "milestone": "Parking Lot",
> > > "priority": "major",
> > > "resolution": "invalid",
> > > "status": "closed",
> > > "submitter": "jpschewe",
> > > "summary": "test ticket",
> > > "type": "defect"
> > > }
> > >
> > >
> > >
> > > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe
> <jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>> wrote:
> > >
> > > Looks like tickets_in should be set to doc in my
> case. Although
> > line 80
> > > is now giving me problems as it looks like you're
> trying to reuse the
> > > JSON document to submit and it's not working because
> it's not
> > formatted
> > > as expected.
> > >
> > >
> > > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe
> <jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>
> <mailto:jpschewe@mtu.net <ma...@mtu.net>>>> wrote:
> > >
> > > So far it's going poorly:
> > >
> > > Traceback (most recent call last):
> > > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 123, in <module>
> > > main()
> > > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 51, in main
> > > verbose=options.verbose)
> > > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 69, in import_tracker
> > > tickets_in =
> doc['trackers']['default']['artifacts']
> > > TypeError: list indices must be integers, not str
> > >
> > > File to import is attached.
> > >
> > >
> > >
> > > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe
> <jpschewe@mtu.net <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>
> > > <mailto:jpschewe@mtu.net
> <ma...@mtu.net> <mailto:jpschewe@mtu.net
> <ma...@mtu.net>>>> wrote:
> > >
> > > I'll try. Should I post them back to the list?
> > >
> > >
> > > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> > <rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>
> > > <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>>>>
> > wrote:
> > >
> > > So, I see you've got a new ticket open
> about this, which
> > > seems to indicate that you're making
> progress. I was
> > > wondering if we could persuade you to
> take really good
> > notes
> > > and produce some docs of how this
> process works?
> > >
> > > --Rich
> > >
> > > On Feb 23, 2013, at 4:53 PM, Jon Schewe
> wrote:
> > >
> > >> Things have settled down on my project
> a bit now, so I've
> > >> gone ahead with the migration. I
> haven't migrated the
> > >> tickets yet because the code link is
> broken. If
> > anyone has
> > >> any insight into this, it would be much
> appreciated.
> > >>
> https://sourceforge.net/p/allura/tickets/5844/
> > >>
> > >> Once this is resolved I'll try the
> ticket import.
> > >>
> > >>
> > >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> > >> <rbowen@rcbowen.com
> <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>> wrote:
> > >>
> > >>
> > >> On Dec 5, 2012, at 3:17 PM, Jon
> Schewe wrote:
> > >>
> > >>> I'm not sure how I would go about
> creating a test
> > >>> project on SourceForge. I'm not
> setting up my own
> > >>> Allura instance, I'm using the one
> on SourceForge.
> > >>>
> > >>
> > >> Go to http://sf.net/create and
> click the Create Your
> > >> Project button. That'll get you
> started.
> > >>
> > >> --
> > >> Rich Bowen
> > >> rbowen@rcbowen.com
> <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> :: @rbowen
> > >> rbowen@apache.org
> <ma...@apache.org> <mailto:rbowen@apache.org
> <ma...@apache.org>>
> > <mailto:rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> http://mtu.net/~jpschewe
> > >>
> > >
> > > --
> > > Rich Bowen
> > > rbowen@rcbowen.com
> <ma...@rcbowen.com> <mailto:rbowen@rcbowen.com
> <ma...@rcbowen.com>>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> :: @rbowen
> > > rbowen@apache.org
> <ma...@apache.org> <mailto:rbowen@apache.org
> <ma...@apache.org>>
> > <mailto:rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net
> <ma...@brondsema.net> <mailto:dave@brondsema.net
> <ma...@brondsema.net>>
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
How would I change the type of the column? I didn't create the column. My
guess is that it came in from the Trac import. Once I do change the type,
how do I save the sort with the search so that anyone viewing the search
sees the same sort order by default?
On Thu, Mar 28, 2013 at 4:17 PM, Dave Brondsema <da...@brondsema.net> wrote:
> Most fields can be added to the default list of columns shown, and then
> sorted
> on. It looks like your priority field is "text", which apparently Allura
> doesn't let you show in list view. Maybe you could try changing it to a
> select
> field? Or if you need it to be text, I think it'd be a reasonable
> enhancement
> to allow text fields to be shown as columns in list view
>
> On 3/27/13 11:48 AM, Jon Schewe wrote:
> > Thanks, it looks like all of the information went in. I'll be posting
> the steps
> > I used and references to the tickets I filed to get the import to work.
> I am
> > disappointed that the saved searches can't sort on priority.
> >
> >
> > On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <dave@brondsema.net
> > <ma...@brondsema.net>> wrote:
> >
> > It might take a minute or two for search indexes to be updated. It
> looks like
> > search includes your imported tickets now. Also, the API endpoint at
> > https://sourceforge.net/rest/p/fll-sw/issues just lists a little
> bit of info for
> > each ticket. If you want an API endpoint for full details on a
> ticket, just add
> > the number to the URL like:
> https://sourceforge.net/rest/p/fll-sw/issues/1
> >
> > On 3/26/13 7:24 PM, Jon Schewe wrote:
> > > Wait, I spoke too soon. In my email came a link to the ticket and
> that shows
> > > more information.
> > > https://sourceforge.net/p/fll-sw/issues/1/
> > >
> > >
> > > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> > >
> > > OK, I hacked up a fix that creates a new hash for the document
> to import:
> > > doc_import={}
> > > doc_import['trackers'] = {}
> > > doc_import['trackers']['default'] = {}
> > > doc_import['trackers']['default']['artifacts'] =
> [ticket_in]
> > >
> > > Now I can import a ticket. I can see it
> > > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > > at
> >
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> > >
> > > It also looks like most of the information didn't get
> imported. That's not
> > > going to be very helpful. This is the raw JSON for the ticket
> that was
> > > imported. I would have expected the comments, milestone,
> status, submitter
> > > to make it in.
> > > {
> > > "assigned_to": "jpschewe",
> > > "cc": "",
> > > "class": "ARTIFACT",
> > > "comments": [
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **milestone** set to _Parking
> Lot_\n\n",
> > > "date": "2010-10-02T21:41:54Z",
> > > "submitter": "jpschewe"
> > > },
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **owner** set to _jpschewe_\n *
> **status**
> > changed
> > > from _new_ to _accepted_\n\n",
> > > "date": "2010-10-02T21:51:55Z",
> > > "submitter": "jpschewe"
> > > },
> > > {
> > > "class": "COMMENT",
> > > "comment": " * **status** changed from _accepted_ to
> > _closed_\n *
> > > **resolution** set to _invalid_\n * **component** set to
> _General_\n\n",
> > > "date": "2010-10-02T22:58:37Z",
> > > "submitter": "jpschewe"
> > > }
> > > ],
> > > "component": "General",
> > > "date": "2010-09-21T01:18:00Z",
> > > "date_updated": "2010-10-02T22:58:37Z",
> > > "description": "testing MyLyn",
> > > "id": 1,
> > > "keywords": "",
> > > "milestone": "Parking Lot",
> > > "priority": "major",
> > > "resolution": "invalid",
> > > "status": "closed",
> > > "submitter": "jpschewe",
> > > "summary": "test ticket",
> > > "type": "defect"
> > > }
> > >
> > >
> > >
> > > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> > >
> > > Looks like tickets_in should be set to doc in my case.
> Although
> > line 80
> > > is now giving me problems as it looks like you're trying
> to reuse the
> > > JSON document to submit and it's not working because it's
> not
> > formatted
> > > as expected.
> > >
> > >
> > > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <
> jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> wrote:
> > >
> > > So far it's going poorly:
> > >
> > > Traceback (most recent call last):
> > > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 123, in <module>
> > > main()
> > > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 51, in main
> > > verbose=options.verbose)
> > > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > > line 69, in import_tracker
> > > tickets_in =
> doc['trackers']['default']['artifacts']
> > > TypeError: list indices must be integers, not str
> > >
> > > File to import is attached.
> > >
> > >
> > >
> > > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <
> jpschewe@mtu.net
> > <ma...@mtu.net>
> > > <mailto:jpschewe@mtu.net <ma...@mtu.net>>>
> wrote:
> > >
> > > I'll try. Should I post them back to the list?
> > >
> > >
> > > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> > <rbowen@rcbowen.com <ma...@rcbowen.com>
> > > <mailto:rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>>>
> > wrote:
> > >
> > > So, I see you've got a new ticket open about
> this, which
> > > seems to indicate that you're making progress.
> I was
> > > wondering if we could persuade you to take
> really good
> > notes
> > > and produce some docs of how this process
> works?
> > >
> > > --Rich
> > >
> > > On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
> > >
> > >> Things have settled down on my project a bit
> now, so I've
> > >> gone ahead with the migration. I haven't
> migrated the
> > >> tickets yet because the code link is broken.
> If
> > anyone has
> > >> any insight into this, it would be much
> appreciated.
> > >>
> https://sourceforge.net/p/allura/tickets/5844/
> > >>
> > >> Once this is resolved I'll try the ticket
> import.
> > >>
> > >>
> > >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> > >> <rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> wrote:
> > >>
> > >>
> > >> On Dec 5, 2012, at 3:17 PM, Jon Schewe
> wrote:
> > >>
> > >>> I'm not sure how I would go about
> creating a test
> > >>> project on SourceForge. I'm not setting
> up my own
> > >>> Allura instance, I'm using the one on
> SourceForge.
> > >>>
> > >>
> > >> Go to http://sf.net/create and click the
> Create Your
> > >> Project button. That'll get you started.
> > >>
> > >> --
> > >> Rich Bowen
> > >> rbowen@rcbowen.com <mailto:
> rbowen@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>> :: @rbowen
> > >> rbowen@apache.org <mailto:
> rbowen@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> http://mtu.net/~jpschewe
> > >>
> > >
> > > --
> > > Rich Bowen
> > > rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>> :: @rbowen
> > > rbowen@apache.org <ma...@apache.org>
> > <mailto:rbowen@apache.org <ma...@apache.org>>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> > >
> > >
> > >
> > > --
> > > http://mtu.net/~jpschewe
> > >
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Dave Brondsema <da...@brondsema.net>.
Most fields can be added to the default list of columns shown, and then sorted
on. It looks like your priority field is "text", which apparently Allura
doesn't let you show in list view. Maybe you could try changing it to a select
field? Or if you need it to be text, I think it'd be a reasonable enhancement
to allow text fields to be shown as columns in list view
On 3/27/13 11:48 AM, Jon Schewe wrote:
> Thanks, it looks like all of the information went in. I'll be posting the steps
> I used and references to the tickets I filed to get the import to work. I am
> disappointed that the saved searches can't sort on priority.
>
>
> On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <dave@brondsema.net
> <ma...@brondsema.net>> wrote:
>
> It might take a minute or two for search indexes to be updated. It looks like
> search includes your imported tickets now. Also, the API endpoint at
> https://sourceforge.net/rest/p/fll-sw/issues just lists a little bit of info for
> each ticket. If you want an API endpoint for full details on a ticket, just add
> the number to the URL like: https://sourceforge.net/rest/p/fll-sw/issues/1
>
> On 3/26/13 7:24 PM, Jon Schewe wrote:
> > Wait, I spoke too soon. In my email came a link to the ticket and that shows
> > more information.
> > https://sourceforge.net/p/fll-sw/issues/1/
> >
> >
> > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > OK, I hacked up a fix that creates a new hash for the document to import:
> > doc_import={}
> > doc_import['trackers'] = {}
> > doc_import['trackers']['default'] = {}
> > doc_import['trackers']['default']['artifacts'] = [ticket_in]
> >
> > Now I can import a ticket. I can see it
> > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > at
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> >
> > It also looks like most of the information didn't get imported. That's not
> > going to be very helpful. This is the raw JSON for the ticket that was
> > imported. I would have expected the comments, milestone, status, submitter
> > to make it in.
> > {
> > "assigned_to": "jpschewe",
> > "cc": "",
> > "class": "ARTIFACT",
> > "comments": [
> > {
> > "class": "COMMENT",
> > "comment": " * **milestone** set to _Parking Lot_\n\n",
> > "date": "2010-10-02T21:41:54Z",
> > "submitter": "jpschewe"
> > },
> > {
> > "class": "COMMENT",
> > "comment": " * **owner** set to _jpschewe_\n * **status**
> changed
> > from _new_ to _accepted_\n\n",
> > "date": "2010-10-02T21:51:55Z",
> > "submitter": "jpschewe"
> > },
> > {
> > "class": "COMMENT",
> > "comment": " * **status** changed from _accepted_ to
> _closed_\n *
> > **resolution** set to _invalid_\n * **component** set to _General_\n\n",
> > "date": "2010-10-02T22:58:37Z",
> > "submitter": "jpschewe"
> > }
> > ],
> > "component": "General",
> > "date": "2010-09-21T01:18:00Z",
> > "date_updated": "2010-10-02T22:58:37Z",
> > "description": "testing MyLyn",
> > "id": 1,
> > "keywords": "",
> > "milestone": "Parking Lot",
> > "priority": "major",
> > "resolution": "invalid",
> > "status": "closed",
> > "submitter": "jpschewe",
> > "summary": "test ticket",
> > "type": "defect"
> > }
> >
> >
> >
> > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > Looks like tickets_in should be set to doc in my case. Although
> line 80
> > is now giving me problems as it looks like you're trying to reuse the
> > JSON document to submit and it's not working because it's not
> formatted
> > as expected.
> >
> >
> > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > So far it's going poorly:
> >
> > Traceback (most recent call last):
> > File "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 123, in <module>
> > main()
> > File "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 51, in main
> > verbose=options.verbose)
> > File "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 69, in import_tracker
> > tickets_in = doc['trackers']['default']['artifacts']
> > TypeError: list indices must be integers, not str
> >
> > File to import is attached.
> >
> >
> >
> > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>
> > <mailto:jpschewe@mtu.net <ma...@mtu.net>>> wrote:
> >
> > I'll try. Should I post them back to the list?
> >
> >
> > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen
> <rbowen@rcbowen.com <ma...@rcbowen.com>
> > <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>>
> wrote:
> >
> > So, I see you've got a new ticket open about this, which
> > seems to indicate that you're making progress. I was
> > wondering if we could persuade you to take really good
> notes
> > and produce some docs of how this process works?
> >
> > --Rich
> >
> > On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
> >
> >> Things have settled down on my project a bit now, so I've
> >> gone ahead with the migration. I haven't migrated the
> >> tickets yet because the code link is broken. If
> anyone has
> >> any insight into this, it would be much appreciated.
> >> https://sourceforge.net/p/allura/tickets/5844/
> >>
> >> Once this is resolved I'll try the ticket import.
> >>
> >>
> >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> >> <rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>>> wrote:
> >>
> >>
> >> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
> >>
> >>> I'm not sure how I would go about creating a test
> >>> project on SourceForge. I'm not setting up my own
> >>> Allura instance, I'm using the one on SourceForge.
> >>>
> >>
> >> Go to http://sf.net/create and click the Create Your
> >> Project button. That'll get you started.
> >>
> >> --
> >> Rich Bowen
> >> rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>> :: @rbowen
> >> rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> http://mtu.net/~jpschewe
> >>
> >
> > --
> > Rich Bowen
> > rbowen@rcbowen.com <ma...@rcbowen.com>
> <mailto:rbowen@rcbowen.com <ma...@rcbowen.com>> :: @rbowen
> > rbowen@apache.org <ma...@apache.org>
> <mailto:rbowen@apache.org <ma...@apache.org>>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net <ma...@brondsema.net>
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
Thanks, it looks like all of the information went in. I'll be posting the
steps I used and references to the tickets I filed to get the import to
work. I am disappointed that the saved searches can't sort on priority.
On Wed, Mar 27, 2013 at 8:10 AM, Dave Brondsema <da...@brondsema.net> wrote:
> It might take a minute or two for search indexes to be updated. It looks
> like
> search includes your imported tickets now. Also, the API endpoint at
> https://sourceforge.net/rest/p/fll-sw/issues just lists a little bit of
> info for
> each ticket. If you want an API endpoint for full details on a ticket,
> just add
> the number to the URL like: https://sourceforge.net/rest/p/fll-sw/issues/1
>
> On 3/26/13 7:24 PM, Jon Schewe wrote:
> > Wait, I spoke too soon. In my email came a link to the ticket and that
> shows
> > more information.
> > https://sourceforge.net/p/fll-sw/issues/1/
> >
> >
> > On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>> wrote:
> >
> > OK, I hacked up a fix that creates a new hash for the document to
> import:
> > doc_import={}
> > doc_import['trackers'] = {}
> > doc_import['trackers']['default'] = {}
> > doc_import['trackers']['default']['artifacts'] =
> [ticket_in]
> >
> > Now I can import a ticket. I can see it
> > at https://sourceforge.net/rest/p/fll-sw/issues, but not
> > at
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
> >
> > It also looks like most of the information didn't get imported.
> That's not
> > going to be very helpful. This is the raw JSON for the ticket that
> was
> > imported. I would have expected the comments, milestone, status,
> submitter
> > to make it in.
> > {
> > "assigned_to": "jpschewe",
> > "cc": "",
> > "class": "ARTIFACT",
> > "comments": [
> > {
> > "class": "COMMENT",
> > "comment": " * **milestone** set to _Parking Lot_\n\n",
> > "date": "2010-10-02T21:41:54Z",
> > "submitter": "jpschewe"
> > },
> > {
> > "class": "COMMENT",
> > "comment": " * **owner** set to _jpschewe_\n * **status**
> changed
> > from _new_ to _accepted_\n\n",
> > "date": "2010-10-02T21:51:55Z",
> > "submitter": "jpschewe"
> > },
> > {
> > "class": "COMMENT",
> > "comment": " * **status** changed from _accepted_ to
> _closed_\n *
> > **resolution** set to _invalid_\n * **component** set to
> _General_\n\n",
> > "date": "2010-10-02T22:58:37Z",
> > "submitter": "jpschewe"
> > }
> > ],
> > "component": "General",
> > "date": "2010-09-21T01:18:00Z",
> > "date_updated": "2010-10-02T22:58:37Z",
> > "description": "testing MyLyn",
> > "id": 1,
> > "keywords": "",
> > "milestone": "Parking Lot",
> > "priority": "major",
> > "resolution": "invalid",
> > "status": "closed",
> > "submitter": "jpschewe",
> > "summary": "test ticket",
> > "type": "defect"
> > }
> >
> >
> >
> > On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>> wrote:
> >
> > Looks like tickets_in should be set to doc in my case. Although
> line 80
> > is now giving me problems as it looks like you're trying to
> reuse the
> > JSON document to submit and it's not working because it's not
> formatted
> > as expected.
> >
> >
> > On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jpschewe@mtu.net
> > <ma...@mtu.net>> wrote:
> >
> > So far it's going poorly:
> >
> > Traceback (most recent call last):
> > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 123, in <module>
> > main()
> > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 51, in main
> > verbose=options.verbose)
> > File
> "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> > line 69, in import_tracker
> > tickets_in = doc['trackers']['default']['artifacts']
> > TypeError: list indices must be integers, not str
> >
> > File to import is attached.
> >
> >
> >
> > On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <
> jpschewe@mtu.net
> > <ma...@mtu.net>> wrote:
> >
> > I'll try. Should I post them back to the list?
> >
> >
> > On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <
> rbowen@rcbowen.com
> > <ma...@rcbowen.com>> wrote:
> >
> > So, I see you've got a new ticket open about this,
> which
> > seems to indicate that you're making progress. I was
> > wondering if we could persuade you to take really
> good notes
> > and produce some docs of how this process works?
> >
> > --Rich
> >
> > On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
> >
> >> Things have settled down on my project a bit now,
> so I've
> >> gone ahead with the migration. I haven't migrated
> the
> >> tickets yet because the code link is broken. If
> anyone has
> >> any insight into this, it would be much appreciated.
> >> https://sourceforge.net/p/allura/tickets/5844/
> >>
> >> Once this is resolved I'll try the ticket import.
> >>
> >>
> >> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
> >> <rbowen@rcbowen.com <ma...@rcbowen.com>>
> wrote:
> >>
> >>
> >> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
> >>
> >>> I'm not sure how I would go about creating a
> test
> >>> project on SourceForge. I'm not setting up my
> own
> >>> Allura instance, I'm using the one on
> SourceForge.
> >>>
> >>
> >> Go to http://sf.net/create and click the
> Create Your
> >> Project button. That'll get you started.
> >>
> >> --
> >> Rich Bowen
> >> rbowen@rcbowen.com <ma...@rcbowen.com>
> :: @rbowen
> >> rbowen@apache.org <ma...@apache.org>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> http://mtu.net/~jpschewe
> >>
> >
> > --
> > Rich Bowen
> > rbowen@rcbowen.com <ma...@rcbowen.com> ::
> @rbowen
> > rbowen@apache.org <ma...@apache.org>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
> >
> >
> >
> > --
> > http://mtu.net/~jpschewe
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Dave Brondsema <da...@brondsema.net>.
It might take a minute or two for search indexes to be updated. It looks like
search includes your imported tickets now. Also, the API endpoint at
https://sourceforge.net/rest/p/fll-sw/issues just lists a little bit of info for
each ticket. If you want an API endpoint for full details on a ticket, just add
the number to the URL like: https://sourceforge.net/rest/p/fll-sw/issues/1
On 3/26/13 7:24 PM, Jon Schewe wrote:
> Wait, I spoke too soon. In my email came a link to the ticket and that shows
> more information.
> https://sourceforge.net/p/fll-sw/issues/1/
>
>
> On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>> wrote:
>
> OK, I hacked up a fix that creates a new hash for the document to import:
> doc_import={}
> doc_import['trackers'] = {}
> doc_import['trackers']['default'] = {}
> doc_import['trackers']['default']['artifacts'] = [ticket_in]
>
> Now I can import a ticket. I can see it
> at https://sourceforge.net/rest/p/fll-sw/issues, but not
> at https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
>
> It also looks like most of the information didn't get imported. That's not
> going to be very helpful. This is the raw JSON for the ticket that was
> imported. I would have expected the comments, milestone, status, submitter
> to make it in.
> {
> "assigned_to": "jpschewe",
> "cc": "",
> "class": "ARTIFACT",
> "comments": [
> {
> "class": "COMMENT",
> "comment": " * **milestone** set to _Parking Lot_\n\n",
> "date": "2010-10-02T21:41:54Z",
> "submitter": "jpschewe"
> },
> {
> "class": "COMMENT",
> "comment": " * **owner** set to _jpschewe_\n * **status** changed
> from _new_ to _accepted_\n\n",
> "date": "2010-10-02T21:51:55Z",
> "submitter": "jpschewe"
> },
> {
> "class": "COMMENT",
> "comment": " * **status** changed from _accepted_ to _closed_\n *
> **resolution** set to _invalid_\n * **component** set to _General_\n\n",
> "date": "2010-10-02T22:58:37Z",
> "submitter": "jpschewe"
> }
> ],
> "component": "General",
> "date": "2010-09-21T01:18:00Z",
> "date_updated": "2010-10-02T22:58:37Z",
> "description": "testing MyLyn",
> "id": 1,
> "keywords": "",
> "milestone": "Parking Lot",
> "priority": "major",
> "resolution": "invalid",
> "status": "closed",
> "submitter": "jpschewe",
> "summary": "test ticket",
> "type": "defect"
> }
>
>
>
> On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>> wrote:
>
> Looks like tickets_in should be set to doc in my case. Although line 80
> is now giving me problems as it looks like you're trying to reuse the
> JSON document to submit and it's not working because it's not formatted
> as expected.
>
>
> On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>> wrote:
>
> So far it's going poorly:
>
> Traceback (most recent call last):
> File "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> line 123, in <module>
> main()
> File "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> line 51, in main
> verbose=options.verbose)
> File "/home/jpschewe/src/allura-git/scripts/allura_import.py",
> line 69, in import_tracker
> tickets_in = doc['trackers']['default']['artifacts']
> TypeError: list indices must be integers, not str
>
> File to import is attached.
>
>
>
> On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <jpschewe@mtu.net
> <ma...@mtu.net>> wrote:
>
> I'll try. Should I post them back to the list?
>
>
> On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <rbowen@rcbowen.com
> <ma...@rcbowen.com>> wrote:
>
> So, I see you've got a new ticket open about this, which
> seems to indicate that you're making progress. I was
> wondering if we could persuade you to take really good notes
> and produce some docs of how this process works?
>
> --Rich
>
> On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>
>> Things have settled down on my project a bit now, so I've
>> gone ahead with the migration. I haven't migrated the
>> tickets yet because the code link is broken. If anyone has
>> any insight into this, it would be much appreciated.
>> https://sourceforge.net/p/allura/tickets/5844/
>>
>> Once this is resolved I'll try the ticket import.
>>
>>
>> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen
>> <rbowen@rcbowen.com <ma...@rcbowen.com>> wrote:
>>
>>
>> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>>
>>> I'm not sure how I would go about creating a test
>>> project on SourceForge. I'm not setting up my own
>>> Allura instance, I'm using the one on SourceForge.
>>>
>>
>> Go to http://sf.net/create and click the Create Your
>> Project button. That'll get you started.
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com <ma...@rcbowen.com> :: @rbowen
>> rbowen@apache.org <ma...@apache.org>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> http://mtu.net/~jpschewe
>>
>
> --
> Rich Bowen
> rbowen@rcbowen.com <ma...@rcbowen.com> :: @rbowen
> rbowen@apache.org <ma...@apache.org>
>
>
>
>
>
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
>
>
>
> --
> http://mtu.net/~jpschewe
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
Wait, I spoke too soon. In my email came a link to the ticket and that
shows more information.
https://sourceforge.net/p/fll-sw/issues/1/
On Tue, Mar 26, 2013 at 6:23 PM, Jon Schewe <jp...@mtu.net> wrote:
> OK, I hacked up a fix that creates a new hash for the document to import:
> doc_import={}
> doc_import['trackers'] = {}
> doc_import['trackers']['default'] = {}
> doc_import['trackers']['default']['artifacts'] = [ticket_in]
>
> Now I can import a ticket. I can see it at
> https://sourceforge.net/rest/p/fll-sw/issues, but not at
> https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
>
> It also looks like most of the information didn't get imported. That's not
> going to be very helpful. This is the raw JSON for the ticket that was
> imported. I would have expected the comments, milestone, status, submitter
> to make it in.
> {
> "assigned_to": "jpschewe",
> "cc": "",
> "class": "ARTIFACT",
> "comments": [
> {
> "class": "COMMENT",
> "comment": " * **milestone** set to _Parking Lot_\n\n",
> "date": "2010-10-02T21:41:54Z",
> "submitter": "jpschewe"
> },
> {
> "class": "COMMENT",
> "comment": " * **owner** set to _jpschewe_\n * **status**
> changed from _new_ to _accepted_\n\n",
> "date": "2010-10-02T21:51:55Z",
> "submitter": "jpschewe"
> },
> {
> "class": "COMMENT",
> "comment": " * **status** changed from _accepted_ to _closed_\n
> * **resolution** set to _invalid_\n * **component** set to
> _General_\n\n",
> "date": "2010-10-02T22:58:37Z",
> "submitter": "jpschewe"
> }
> ],
> "component": "General",
> "date": "2010-09-21T01:18:00Z",
> "date_updated": "2010-10-02T22:58:37Z",
> "description": "testing MyLyn",
> "id": 1,
> "keywords": "",
> "milestone": "Parking Lot",
> "priority": "major",
> "resolution": "invalid",
> "status": "closed",
> "submitter": "jpschewe",
> "summary": "test ticket",
> "type": "defect"
> }
>
>
>
> On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jp...@mtu.net> wrote:
>
>> Looks like tickets_in should be set to doc in my case. Although line 80
>> is now giving me problems as it looks like you're trying to reuse the JSON
>> document to submit and it's not working because it's not formatted as
>> expected.
>>
>>
>> On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jp...@mtu.net> wrote:
>>
>>> So far it's going poorly:
>>>
>>> Traceback (most recent call last):
>>> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line
>>> 123, in <module>
>>> main()
>>> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line
>>> 51, in main
>>> verbose=options.verbose)
>>> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line
>>> 69, in import_tracker
>>> tickets_in = doc['trackers']['default']['artifacts']
>>> TypeError: list indices must be integers, not str
>>>
>>> File to import is attached.
>>>
>>>
>>>
>>> On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <jp...@mtu.net> wrote:
>>>
>>>> I'll try. Should I post them back to the list?
>>>>
>>>>
>>>> On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <rb...@rcbowen.com> wrote:
>>>>
>>>>> So, I see you've got a new ticket open about this, which seems to
>>>>> indicate that you're making progress. I was wondering if we could persuade
>>>>> you to take really good notes and produce some docs of how this process
>>>>> works?
>>>>>
>>>>> --Rich
>>>>>
>>>>> On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>>>>>
>>>>> Things have settled down on my project a bit now, so I've gone ahead
>>>>> with the migration. I haven't migrated the tickets yet because the code
>>>>> link is broken. If anyone has any insight into this, it would be much
>>>>> appreciated.
>>>>> https://sourceforge.net/p/allura/tickets/5844/
>>>>>
>>>>> Once this is resolved I'll try the ticket import.
>>>>>
>>>>>
>>>>> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>>>>
>>>>>>
>>>>>> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>>>>>>
>>>>>> I'm not sure how I would go about creating a test project on
>>>>>> SourceForge. I'm not setting up my own Allura instance, I'm using the one
>>>>>> on SourceForge.
>>>>>>
>>>>>>
>>>>>> Go to http://sf.net/create and click the Create Your Project button.
>>>>>> That'll get you started.
>>>>>>
>>>>>> --
>>>>>> Rich Bowen
>>>>>> rbowen@rcbowen.com :: @rbowen
>>>>>> rbowen@apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://mtu.net/~jpschewe
>>>>>
>>>>>
>>>>> --
>>>>> Rich Bowen
>>>>> rbowen@rcbowen.com :: @rbowen
>>>>> rbowen@apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> http://mtu.net/~jpschewe
>>>>
>>>>
>>>
>>>
>>> --
>>> http://mtu.net/~jpschewe
>>>
>>>
>>
>>
>> --
>> http://mtu.net/~jpschewe
>>
>>
>
>
> --
> http://mtu.net/~jpschewe
>
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
OK, I hacked up a fix that creates a new hash for the document to import:
doc_import={}
doc_import['trackers'] = {}
doc_import['trackers']['default'] = {}
doc_import['trackers']['default']['artifacts'] = [ticket_in]
Now I can import a ticket. I can see it at
https://sourceforge.net/rest/p/fll-sw/issues, but not at
https://sourceforge.net/p/fll-sw/issues/search/?q=status%3Awont-fix+or+status%3Aclosed
It also looks like most of the information didn't get imported. That's not
going to be very helpful. This is the raw JSON for the ticket that was
imported. I would have expected the comments, milestone, status, submitter
to make it in.
{
"assigned_to": "jpschewe",
"cc": "",
"class": "ARTIFACT",
"comments": [
{
"class": "COMMENT",
"comment": " * **milestone** set to _Parking Lot_\n\n",
"date": "2010-10-02T21:41:54Z",
"submitter": "jpschewe"
},
{
"class": "COMMENT",
"comment": " * **owner** set to _jpschewe_\n * **status** changed
from _new_ to _accepted_\n\n",
"date": "2010-10-02T21:51:55Z",
"submitter": "jpschewe"
},
{
"class": "COMMENT",
"comment": " * **status** changed from _accepted_ to _closed_\n *
**resolution** set to _invalid_\n * **component** set to _General_\n\n",
"date": "2010-10-02T22:58:37Z",
"submitter": "jpschewe"
}
],
"component": "General",
"date": "2010-09-21T01:18:00Z",
"date_updated": "2010-10-02T22:58:37Z",
"description": "testing MyLyn",
"id": 1,
"keywords": "",
"milestone": "Parking Lot",
"priority": "major",
"resolution": "invalid",
"status": "closed",
"submitter": "jpschewe",
"summary": "test ticket",
"type": "defect"
}
On Tue, Mar 26, 2013 at 5:54 PM, Jon Schewe <jp...@mtu.net> wrote:
> Looks like tickets_in should be set to doc in my case. Although line 80 is
> now giving me problems as it looks like you're trying to reuse the JSON
> document to submit and it's not working because it's not formatted as
> expected.
>
>
> On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jp...@mtu.net> wrote:
>
>> So far it's going poorly:
>>
>> Traceback (most recent call last):
>> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line
>> 123, in <module>
>> main()
>> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 51,
>> in main
>> verbose=options.verbose)
>> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 69,
>> in import_tracker
>> tickets_in = doc['trackers']['default']['artifacts']
>> TypeError: list indices must be integers, not str
>>
>> File to import is attached.
>>
>>
>>
>> On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <jp...@mtu.net> wrote:
>>
>>> I'll try. Should I post them back to the list?
>>>
>>>
>>> On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <rb...@rcbowen.com> wrote:
>>>
>>>> So, I see you've got a new ticket open about this, which seems to
>>>> indicate that you're making progress. I was wondering if we could persuade
>>>> you to take really good notes and produce some docs of how this process
>>>> works?
>>>>
>>>> --Rich
>>>>
>>>> On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>>>>
>>>> Things have settled down on my project a bit now, so I've gone ahead
>>>> with the migration. I haven't migrated the tickets yet because the code
>>>> link is broken. If anyone has any insight into this, it would be much
>>>> appreciated.
>>>> https://sourceforge.net/p/allura/tickets/5844/
>>>>
>>>> Once this is resolved I'll try the ticket import.
>>>>
>>>>
>>>> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>>>
>>>>>
>>>>> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>>>>>
>>>>> I'm not sure how I would go about creating a test project on
>>>>> SourceForge. I'm not setting up my own Allura instance, I'm using the one
>>>>> on SourceForge.
>>>>>
>>>>>
>>>>> Go to http://sf.net/create and click the Create Your Project button.
>>>>> That'll get you started.
>>>>>
>>>>> --
>>>>> Rich Bowen
>>>>> rbowen@rcbowen.com :: @rbowen
>>>>> rbowen@apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> http://mtu.net/~jpschewe
>>>>
>>>>
>>>> --
>>>> Rich Bowen
>>>> rbowen@rcbowen.com :: @rbowen
>>>> rbowen@apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> http://mtu.net/~jpschewe
>>>
>>>
>>
>>
>> --
>> http://mtu.net/~jpschewe
>>
>>
>
>
> --
> http://mtu.net/~jpschewe
>
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
Looks like tickets_in should be set to doc in my case. Although line 80 is
now giving me problems as it looks like you're trying to reuse the JSON
document to submit and it's not working because it's not formatted as
expected.
On Tue, Mar 26, 2013 at 5:47 PM, Jon Schewe <jp...@mtu.net> wrote:
> So far it's going poorly:
>
> Traceback (most recent call last):
> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 123,
> in <module>
> main()
> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 51,
> in main
> verbose=options.verbose)
> File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 69,
> in import_tracker
> tickets_in = doc['trackers']['default']['artifacts']
> TypeError: list indices must be integers, not str
>
> File to import is attached.
>
>
>
> On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <jp...@mtu.net> wrote:
>
>> I'll try. Should I post them back to the list?
>>
>>
>> On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <rb...@rcbowen.com> wrote:
>>
>>> So, I see you've got a new ticket open about this, which seems to
>>> indicate that you're making progress. I was wondering if we could persuade
>>> you to take really good notes and produce some docs of how this process
>>> works?
>>>
>>> --Rich
>>>
>>> On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>>>
>>> Things have settled down on my project a bit now, so I've gone ahead
>>> with the migration. I haven't migrated the tickets yet because the code
>>> link is broken. If anyone has any insight into this, it would be much
>>> appreciated.
>>> https://sourceforge.net/p/allura/tickets/5844/
>>>
>>> Once this is resolved I'll try the ticket import.
>>>
>>>
>>> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>>
>>>>
>>>> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>>>>
>>>> I'm not sure how I would go about creating a test project on
>>>> SourceForge. I'm not setting up my own Allura instance, I'm using the one
>>>> on SourceForge.
>>>>
>>>>
>>>> Go to http://sf.net/create and click the Create Your Project button.
>>>> That'll get you started.
>>>>
>>>> --
>>>> Rich Bowen
>>>> rbowen@rcbowen.com :: @rbowen
>>>> rbowen@apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> http://mtu.net/~jpschewe
>>>
>>>
>>> --
>>> Rich Bowen
>>> rbowen@rcbowen.com :: @rbowen
>>> rbowen@apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> http://mtu.net/~jpschewe
>>
>>
>
>
> --
> http://mtu.net/~jpschewe
>
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
So far it's going poorly:
Traceback (most recent call last):
File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 123,
in <module>
main()
File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 51,
in main
verbose=options.verbose)
File "/home/jpschewe/src/allura-git/scripts/allura_import.py", line 69,
in import_tracker
tickets_in = doc['trackers']['default']['artifacts']
TypeError: list indices must be integers, not str
File to import is attached.
On Mon, Mar 25, 2013 at 8:04 PM, Jon Schewe <jp...@mtu.net> wrote:
> I'll try. Should I post them back to the list?
>
>
> On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <rb...@rcbowen.com> wrote:
>
>> So, I see you've got a new ticket open about this, which seems to
>> indicate that you're making progress. I was wondering if we could persuade
>> you to take really good notes and produce some docs of how this process
>> works?
>>
>> --Rich
>>
>> On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>>
>> Things have settled down on my project a bit now, so I've gone ahead with
>> the migration. I haven't migrated the tickets yet because the code link is
>> broken. If anyone has any insight into this, it would be much appreciated.
>> https://sourceforge.net/p/allura/tickets/5844/
>>
>> Once this is resolved I'll try the ticket import.
>>
>>
>> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>
>>>
>>> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>>>
>>> I'm not sure how I would go about creating a test project on
>>> SourceForge. I'm not setting up my own Allura instance, I'm using the one
>>> on SourceForge.
>>>
>>>
>>> Go to http://sf.net/create and click the Create Your Project button.
>>> That'll get you started.
>>>
>>> --
>>> Rich Bowen
>>> rbowen@rcbowen.com :: @rbowen
>>> rbowen@apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> http://mtu.net/~jpschewe
>>
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com :: @rbowen
>> rbowen@apache.org
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> http://mtu.net/~jpschewe
>
>
--
http://mtu.net/~jpschewe
Re: Status of allura import
Posted by Jon Schewe <jp...@mtu.net>.
I'll try. Should I post them back to the list?
On Mon, Mar 25, 2013 at 9:54 AM, Rich Bowen <rb...@rcbowen.com> wrote:
> So, I see you've got a new ticket open about this, which seems to indicate
> that you're making progress. I was wondering if we could persuade you to
> take really good notes and produce some docs of how this process works?
>
> --Rich
>
> On Feb 23, 2013, at 4:53 PM, Jon Schewe wrote:
>
> Things have settled down on my project a bit now, so I've gone ahead with
> the migration. I haven't migrated the tickets yet because the code link is
> broken. If anyone has any insight into this, it would be much appreciated.
> https://sourceforge.net/p/allura/tickets/5844/
>
> Once this is resolved I'll try the ticket import.
>
>
> On Wed, Dec 5, 2012 at 2:41 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>
>>
>> On Dec 5, 2012, at 3:17 PM, Jon Schewe wrote:
>>
>> I'm not sure how I would go about creating a test project on SourceForge.
>> I'm not setting up my own Allura instance, I'm using the one on SourceForge.
>>
>>
>> Go to http://sf.net/create and click the Create Your Project button.
>> That'll get you started.
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com :: @rbowen
>> rbowen@apache.org
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> http://mtu.net/~jpschewe
>
>
> --
> Rich Bowen
> rbowen@rcbowen.com :: @rbowen
> rbowen@apache.org
>
>
>
>
>
>
>
--
http://mtu.net/~jpschewe