112646 - Moving/Exporting Bug Activity

Status: NEW

(Bugzilla :: Bug Import/Export & Moving, enhancement)

Description

[GavinS]

The XML import/export/moving of bugs is great, but what about all the associated
bug activity?

Has anyone ever considered or wanted to move the activity data?

Comment 1

[Matthew Tuck [:CodeMachine]]

Probably not.

Comment 2

[Dave Miller [:justdave]]

I think there's a good case for this.  There should be more than one way to move
a bug, and this ought to be included in one of them.

Comment 3

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 4

[Guzmán Brasó]

I'm intrested in taking care of add such functionality (With no hurry).

But first let's be clear on what we want.

1. Export bugs_activity.

1.1 Change current DTD

Should we always export this information, and then change bugzilla.dtd, xml.cgi, etc to support the new dtd with bug_ativities on it.

1.2 Give it as optional feature

Should we add an enable/disable button for this and in case of enable use a different dtd like bugzilla-full.dtd and a different template for this instead of bug/show.xml.tmpl




1. Import bugs_activity as comment

I think we can not import bug_activity information as real bug_activity data. The most important information would be invalid: user id. We can't save another insallation user id in the who field of bugs_activity. 

So for me import would be only process it as more readable as possible and append it as comment on the imported bug.

Please tell me what you think.

Also there are a lot of dupe bugs of this one. Should I work on this one and set dupe the others?.

Comment 7

[Kent Rogers [:mrbball]]

Attachment: Add XML output for show_activity.cgi

Here is a patch to add XML output capability for show_activity.cgi, which
is what bug 724970 was about.

Comment 8

[Kent Rogers [:mrbball]]

Comment on attachment 596308 [details] [diff] [review]
Add XML output for show_activity.cgi

This patch was inadvertently built against 4.0.  I will re-work for trunk.

Comment 9

[Kent Rogers [:mrbball]]

Attachment: Add XML output for show_activity.cgi

Let's try this again; patch against trunk.

This is a patch to add XML output capability for show_activity.cgi, which
is what bug 724970 is asking for.

Comment 10

[Frédéric Buclin]

Comment on attachment 596334 [details] [diff] [review]
Add XML output for show_activity.cgi

>=== added file 'template/en/default/bug/activity/show.xml.tmpl'

>+<!DOCTYPE bugzilla SYSTEM "[% urlbase FILTER html %]bugzilla.dtd">

Instead of messing bugzilla.dtd, you should include the DTD in this XML file directly. bugzilla.dtd is really for bugs themselves.


>+<bugzilla version="[% constants.BUGZILLA_VERSION %]"

Please filter this constant too.


>+[% PROCESS bug/activity/table.xml.tmpl %]

There is no reason to have a separate template for the table, as it's not used somewhere else. Just merge both.



>=== added file 'template/en/default/bug/activity/table.xml.tmpl'

>+  # incomplete_data: boolean. True if some of the data is incomplete (because
>+  #                  it was affected by an old Bugzilla bug.)

incomplete_data is used nowhere, it looks like.



>=== modified file 'template/en/default/filterexceptions.pl'

>+'bug/activity/show.xml.tmpl' => [
>+  'constants.BUGZILLA_VERSION', 
>+],

No exception for it, see above.


>=== modified file 'template/en/default/pages/bugzilla.dtd.tmpl'

No need to alter this file, see above.


That was a very quick review, so I may have more to say when reviewing the updated patch. :)