[#560] SQL dump of GRASS trackers request

Date:
2007-12-08 13:47
Priority:
4
State:
Closed
Submitted by:
Maciej Sieczka (msieczka)
Assigned to:
Sascha Wilde (wilde)
Summary:
SQL dump of GRASS trackers request

Detailed description
GRASS migration to Trac at OSGeo is scheduled. In order to import GRASS trackers content to our new tracker, we'd need an SQL dump or access to a database where they are stored at Wald GForge. It would be great if GForge admins could help in this regard. Thanks.
Message  ↓
Date: 2010-01-05 10:27
Sender: Sascha Wilde

Seems to be resolved or deprecated at least.
In case of open questions please reopen.

Date: 2008-04-07 14:37
Sender: Markus Neteler

Sascha fixed XML export of GForge today (thanks!):

http://wald.intevation.org/export/tracker.php?group_id=21&atid=204

Now we need to process this XML to generate something useful for trac.

Markus

Date: 2008-02-04 13:26
Sender: Sascha Wilde

Hi Maciej,

unfortunately the export of custom fields is not implemented in gforge
(at least not in the version we are currently using.

I can try to hack something up, to include custom fields but as I'm
still short of time this will certainly take some time...

cheers
sascha

Date: 2008-02-04 12:17
Sender: Maciej Sieczka

Hi Sascha

That's excellent. Most important bits are there in the xml dump. And all the followup discussion too! Great.

Missing are all my custom fields though. That's not critical, but would be very usefull to have them preserved. Eg. in the "Code issues" [1], after you log in, you can also see: the "Operating system:", "Operating system version:", "GRASS component:", "Issue status:" "Issue type:" fields. Is it possible to have them exported too?

[1]http://wald.intevation.org/tracker/index.php?func=detail&aid=290&group_id=21&atid=204

Date: 2008-02-04 10:01
Sender: Sascha Wilde

Hi Maciek,

Ok, so I have simply removed the <resolution> output from the export function.

http://wald.intevation.org/tracker/index.php?func=detail&aid=560&group_id=1&atid=162

now works as expected, and so should the equivalent URLs for the other GRASS trackers.

Does this solves this issue?

cheers
sascha

Date: 2008-02-01 17:29
Sender: Maciej Sieczka

Hi Sascha

I guess we don't need the "resolution" tag. No trace of any "resolution" in the trackers. According to GForge doc, it's a sort of a built-in field, like "Data Type" and "Status". Apperently your GForge setup just doesn't use it, ?

Big thanks for looking into this.

Maciek

Date: 2008-02-01 17:08
Sender: Sascha Wilde

Hi *,

I finally got to have a look at this issue, the problem is, that the method used to get the resolution name (which is the value of the <resolution> tag in the XML export) does not exist...

The simples solution would be to ditch the <resolution> from the XML export -- if you don't need it's value I'll do this and you should be able to use the export function immediately. :)

However, if you need the resolution value I have to research a real fix.

Anyway, I have to admit that I don't even know what the meaning of the resolution value in the Gforge trackers are... :-/

cheers
and sorry for the big delay
sascha

Date: 2007-12-19 14:24
Sender: Sascha Wilde

Hi Maciej,

this indeed looks like an very interesting option. I didn't know about this feature of gforge, thank you for pointing it out.

I'll have a look, why it doesn't work like expected on wald.

cheers
sascha

Date: 2007-12-18 19:02
Sender: Maciej Sieczka

Sascha

Thanks for the details. That sounds complicated. Before proceeding this way, I'm still hoping there might an easier one.

I've learned from Martin Landa [1] that GForge can provide a "ticket export to xml" feature. However, it does not work as expected on Wald. Try the following link [2]. I hoped it would dump full ticket content, but it merely lists few tags. Could it work like eg. this beautiful example [3], where all the comments and other content are preserved?

[1]http://www.nabble.com/gforge2trac-migration-(export-problem)-td14253277.html
[2]http://wald.intevation.org/export/tracker.php?group_id=21&atid=188
[3]http://rubyforge.org/export/tracker.php?group_id=5&atid=101

Date: 2007-12-18 14:38
Sender: Sascha Wilde

Hi Maciek,

sorry for the late answer.

In fact it isn't that easy (maybe my last mail wasn't clear enough).

The Information you need (description, author, flags of the issues, comments on the issues, mail addresses of the authors etc.) is scattered over many tables in the database. There are no less than 17 artifact related tables in the gforge database (artifact is the gforge term for tracker entries). And the information on users (email, real
name) is in yet another table, maybe even more tables are involved...

I'm pretty sure that not all of these tables are needed, but I
currently don't have the time to figure out which. Further more: I don't know how to extract all the information in a way, so that you can use it for import in your new system.

So what I hoped you would do is this:

- Setup a minimal gforge test installation, and have a look
where information in the Trackers ends up -- I can give
you some hints which parts of the code and which database
tables might be involved, but after all I don't know all
the details, too.
- Develop a way to export the tracker content from gforge
and import it to your new system.
- Tell me what data you need and in which form I shall
provide it.
As said in my last mail: I can give you selective dumps
(I don't care to give you the complete tables with the
tracer stuff from all projects on wald, as they are public
anyway). Or I could run a
bunch of SQL statements according to your instructions, to
extract the information in a customized way for you.

As you can see, extracting the needed information from the gforge (and preparing it for import in an other system) is a somewhat demanding task, and I hope you understand that I currently don't have the time to do it without your help.

Date: 2007-12-17 20:28
Sender: Maciej Sieczka

Sascha

Me again. Please advice how to prepare the list of tables. I really would love to do that, but just don't know how.

Maciek

Date: 2007-12-10 19:25
Sender: Maciej Sieczka

Hi Sascha

Thanks for your help. How should the list of tables I need look like? Would a list of tracker "Description:" tags be enough or the "atid=" IDs?

Date: 2007-12-10 11:58
Sender: Sascha Wilde

Hi *,

sure enough we will help you with this issue.

Anyway I'm sure you understand that I can't provide you unrestricted access to the database or a complete dump, not only that this would be several gigabytes of data, it would include all user and project data including all (encrypted) passwords. For obvious reasons I can't give you that.

Unfortunately the content of the issue trackers is spread over several tables in the gforge database.

As you will have to figure out how to gather the needed information form the various places anyway it would be tremendous helpful if you could send me a list of the tables you need, so that I could make a selective dump for you.

Alternatively you can send me a bunch of SQL statements which generate the output you need, which I would run and send the results to you.

cheers
sascha

No attached documents

Field Old Value Date By
status_idOpen2010-01-05 10:27Sascha Wilde
close_date2010-01-05 10:272010-01-05 10:27Sascha Wilde
priority32007-12-10 13:17Bernhard Reiter
assigned_tonone2007-12-10 13:17Bernhard Reiter