OASIS Open Document Format for Office Applications (OpenDocument) TC

 View Only

  • 1.  office-comment -> JIRA migration

    Posted 05-05-2009 19:24 
    I have the python script working now to migrate comments from the 
office-comment list into JIRA.  Mary set up a sandbox project for me to 
experiment in and you can see the results there:

http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10028

What I have done is:

JIRA summary = "Public Comment: " + original comment subject line
JIRA data = current date (unfortunately there is no ability to set the 
JIRA data back to the original date)
JIRA reporter = me (again, JIRA does not allow me to set it to the name of 
the original comment author)
JIRA type=bug (the default) 
JIRA description = a paragraph indicating the original date and author of 
the comment, as well as a navigable link back to the original post

Once I kick this off on the TC's production JIRA project, I'll need to go 
back and reapply the decisions from the Registry of Comments spreadsheet. 
But that should be straightforward, just a lot of clicking.  We should be 
able to start processing new comments in JIRA on the next TC call, or 
maybe the one after that.

Please take a quick look at the test project and let me know if anything 
looks horribly wrong.  If the test migration goes well I will kick off a 
real one overnight.  This may generate 100's of notification emails to the 
list, and if so I apologize in advance.   Luckily this will be a one time 
conversion.


-Rob


  • 2.  RE: [office] office-comment -> JIRA migration

    Posted 05-05-2009 21:46 
    1. Looks interesting.  It is difficult to know exactly what all the
materials and repetitions are in the test database.  I do notice they seem
to be in reverse order.  (That is, the most-recent ones tend to have the
lowest numbers, based on my examination of all the "Public Comment:
mix-height( ODF 1.2)" ones.  The information seems to be as you describe it,
below.

2. I assume that it is possible to edit other aspects of the entry, such as
components, affects versions, the description, the priority, etc.

3. It would be good to allow sub-tasks.  I don't see a button for that, but
it may be that is because I am not the reporter.  But subtasks will be
useful, especially for comments that have multiple parts and/or apply
differently to different versions of specifications.

4. I have added some issues to the main repository, but I have not seen any
e-mail notices.  They may have gone un-noticed in my junk mail filter, but I
don't think so.  I just added another and it hasn't shown up anywhere that I
can see.  

 - Dennis 


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 3.  RE: [office] office-comment -> JIRA migration

    Posted 05-06-2009 01:12 
    "Dennis E. Hamilton"


  • 4.  RE: [office] office-comment -> JIRA migration

    Posted 05-06-2009 03:41 
    Sounds good about the numbering.

I am logged in (my name is at the top of the view).

1. Looking at


  • 5.  RE: [office] office-comment -> JIRA migration

    Posted 05-06-2009 04:18 
    "Dennis E. Hamilton"


  • 6.  RE: [office] office-comment -> JIRA migration

    Posted 05-06-2009 06:33 
    I don't want any special privileges.

I used "Close" because it is all I see available.  Can't see any of the
other workflow cases or actions so far.  Maybe that changes once the issue
has been accepted?

Re sub-tasking: When there is an action to be retained with regard to more
than one specification, we need a way to keep some alive while ones are
completed.

But I agree, probably should not be done by the proposer.  Can be reflected
in the initial issue proposal and the rest worked out later.

So, the JIRA set up is oriented to project management, and in our context
that means the officers of the TC are the managers.

 - Dennis 


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 7.  Re: [office] office-comment -> JIRA migration

    Posted 05-13-2009 13:29 
    Rob,

sorry, but didn't find time to commenting this thread before before.

robert_weir@us.ibm.com wrote:
> I have the python script working now to migrate comments from the 
> office-comment list into JIRA.  Mary set up a sandbox project for me to 
> experiment in and you can see the results there:
> 
> http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10028
> 
> What I have done is:
> 
> JIRA summary = "Public Comment: " + original comment subject line
> JIRA data = current date (unfortunately there is no ability to set the 
> JIRA data back to the original date)

I guess this is not a feature of any bug tracker because it would allow
corrupting the database to some extend.

> JIRA reporter = me (again, JIRA does not allow me to set it to the name of 
> the original comment author)

I see three ways to resolve this:
1) JIRA summary = "Public Comment: " + *Original Comment Author* +
original comment subject line
2) Adding a custom field if possible.
3) Adding this information as header of the description, as you in fact
did as far as I have been observing.


[...]

> But that should be straightforward, just a lot of clicking.  We should be 
> able to start processing new comments in JIRA on the next TC call, or 
> maybe the one after that.

That would be great.

> 
> Please take a quick look at the test project and let me know if anything 
> looks horribly wrong. [...]

Did not find any issue so far.

Best regards,
Peter


-- 
Peter Junge
Open Source Strategy Director

Beijing Redflag Chinese 2000 Software Co., Ltd.
Building No.2, Block A, Huilongsen, 18 Xihuan Nanlu
Beijing Economic-Technological Development Area
100176 Beijing - P.R.China

北京红旗中文贰仟软件技术有限公司
地址：北京经济技术开发区（亦庄）西环南路18号汇龙森A座二层
邮编：100176

电话/Tel: +86-10-51570010 ext.6183
邮箱/e-mail： peterjunge@RedOffice.com
http://www.RedOffice.com


Related Content