You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Joe Ocaba (JIRA)" <ji...@apache.org> on 2010/08/20 02:09:16 UTC
[jira] Created: (INFRA-2940) brings Maven to the .NET developer
brings Maven to the .NET developer
----------------------------------
Key: INFRA-2940
URL: https://issues.apache.org/jira/browse/INFRA-2940
Project: Infrastructure
Issue Type: New JIRA Project
Security Level: public (Regular issues)
Components: JIRA
Reporter: Joe Ocaba
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917424#action_12917424 ]
Brett Porter commented on INFRA-2940:
-------------------------------------
yep, I expect the resolved ones will only have those two values anyway.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908266#action_12908266 ]
Gavin commented on INFRA-2940:
------------------------------
I would say, to keep reporter information, that we should create new jira accounts.
I am not sure why you need the extra 'Work Item' field, please explain?
I would use a bogus suffix or use @npanday.org - if any users actually then use the account we can change it more appropriate.
Let me have the csv when you got it so I can test it myself on a test instance.
Thanks
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915221#action_12915221 ]
Gavin commented on INFRA-2940:
------------------------------
I've tried importing into a test Jira and failed so far.
I suspect the CSV file may be to blame, I'll investigate, error below:
Cause:
org.apache.commons.configuration.ConfigurationException: Unable to parse unicode value: ac\g
Stack Trace: [hide]
org.apache.commons.configuration.ConfigurationException: Unable to parse unicode value: ac\g
at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:128)
at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:63)
at org.apache.commons.configuration.PropertiesConfiguration.<init>(PropertiesConfiguration.java:199)
at com.atlassian.jira.imports.csv.CsvConfiguration.<init>(CsvConfiguration.java:32)
at com.atlassian.jira.web.action.util.CsvImporter.doSettings(CsvImporter.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:61)
at webwork.util.InjectionUtils.invoke(InjectionUtils.java:52)
at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:417)
at webwork.action.ActionSupport.execute(ActionSupport.java:146)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:178)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)
at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:204)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:120)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:47)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.gzipfilter.GzipFilter.doFilterInternal(GzipFilter.java:81)
at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:33)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: Unable to parse unicode value: ac\g
at org.apache.commons.configuration.PropertiesConfiguration.unescapeJava(PropertiesConfiguration.java:543)
at org.apache.commons.configuration.PropertiesConfiguration.load(PropertiesConfiguration.java:314)
at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:190)
at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:157)
at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:124)
... 74 more
Caused by: java.lang.NumberFormatException: For input string: "ac\g"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:458)
at org.apache.commons.configuration.PropertiesConfiguration.unescapeJava(PropertiesConfiguration.java:535)
... 78 more
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated INFRA-2940:
-----------------------------------
Attachment: npanday-jira-import.conf
Attaching an attempt of an import configuration file. I'll attach the data file when we have sorted out the remaining questions.
Gavin, could you check to see if it's missing something vital?
Two things that I'm not 100% sure about are:
In the wizard I choose to create a new custom field of type "Text" called "Work Item". The line below doesn't contain "Text", but perhaps it is the default data type.
field.ID = customfield_Work Item
I think this has to do with creating new users, so perhaps it should be removed from the configuration if we decide not to create new users on import.
user.email.suffix = @apache.org
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918493#action_12918493 ]
Brett Porter commented on INFRA-2940:
-------------------------------------
I've added all the listed members to the project, set the default permission scheme, and set up a notification scheme.
I also renamed ID to Codeplex ID, and marked the releases with their release date (stripping "NPanday" from the start of the version numbers).
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-03 2.csv, NPanday Work Items 2010-09-12.csv, npanday-jira-import-2010-10-05.conf, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917320#action_12917320 ]
Gavin commented on INFRA-2940:
------------------------------
So who are we waiting on currently (just checking not me :) )
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917399#action_12917399 ]
Dennis Lundberg commented on INFRA-2940:
----------------------------------------
Changing the "ID" custom field to "Codeplex ID" is easy to fix.
Fixing the resolutions on closed issues is another thing. There is a column available in the original Excel export called "Reason". Can we use that?
The used values for that column are:
For state=Closed - "Completed"
For state=Fixed - "Fixed"
For state=Active - "Accepted" or "Wrong Fix"
For state=Proposed - "New" or "Triage"
I guess we only need to have values for the first two?
We'd need to map those to suitable JIRA values instead. My local JIRA installation has these possible resolutions, with accompanying help texts:
Fixed
A fix for this issue is checked into the tree and tested.
Won't Fix
The problem described is an issue which will never be fixed.
Duplicate
The problem is a duplicate of an existing issue.
Incomplete
The problem is not completely described.
Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
It seems to me that we can use the resolution "Fixed" for both reasons "Completed" and "Fixed".
After we have agreed on a suitable mapping I can create a new CSV file and configuration file.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated INFRA-2940:
-----------------------------------
Attachment: NPanday Work Items 2010-09-12.csv
npanday-jira-import.conf
A new configuration file and a CSV file with the actual data in it.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (INFRA-2940) Create JIRA project for
the NPanday podling
Posted by "Maria Odea Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916035#action_12916035 ]
Maria Odea Ching edited comment on INFRA-2940 at 9/29/10 1:58 AM:
------------------------------------------------------------------
Attaching import stats and logs from successful import of CSV file. We can track the issues that failed the import from the logs so maybe we can just clean it up in the CSV file or we can just file them manually?
was (Author: oching):
Attaching import stats and logs from successful import of CSV file. We can track the issues that failed the import from the logs so maybe we can just clean it up in the CSV file or just file it manually?
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated INFRA-2940:
--------------------------------
Summary: Create JIRA project for the NPanday podling (was: brings Maven to the .NET developer)
Initial Developers: [brettporter, dennisl@apache.org, ipv6guru, jocaba, oching, wsmoak] (was: [jocaba])
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909527#action_12909527 ]
Brett Porter commented on INFRA-2940:
-------------------------------------
Hi Dennis, what's the next steps here? Is there anything you need help with?
A user was asking where to file an issue and I wasn't sure whether to point to the old tracker or wait. Can we set up the JIRA project and start using it, even if the import will happen later?
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-2940.
------------------------
Resolution: Fixed
Assignee: (was: Gavin)
Thanks for your files Dennis, all imported.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-03 2.csv, NPanday Work Items 2010-09-12.csv, npanday-jira-import-2010-10-05.conf, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Maria Odea Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916029#action_12916029 ]
Maria Odea Ching commented on INFRA-2940:
-----------------------------------------
We were able to import the CSV file successfully into the test jira but there were a couple of issues that failed the import. I'll attach the logs and the import stats.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909798#action_12909798 ]
Dennis Lundberg commented on INFRA-2940:
----------------------------------------
The next step is for Gavin to test the configuration and data files I attached to see if they work as planned, in a test JIRA installation. If that goes OK we are ready for the real import.
IIRC the JIRA import can accept data in header-less columns and import them as comments. These should be the right-most columns, to the right of the columns that have headers. I don't remember if that will put everything in a single comment, but that'd be better than nothing. Perhaps it'll create one comment per column. See http://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV#ImportingDataFromCSV-ImportingCommentsfromCSV
You could try to append header-less columns with comments to the CSV-file I attached.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated INFRA-2940:
-----------------------------------
Attachment: (was: npanday-jira-import.conf)
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917409#action_12917409 ]
Gavin commented on INFRA-2940:
------------------------------
Sounds good, carry on, lets get this done.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908524#action_12908524 ]
Dennis Lundberg commented on INFRA-2940:
----------------------------------------
I want to be able to create links back to the Codeplex Issue tracker. By keeping the id of each Work Item in the new JIRA issues allows us to create such links. I've seen this done for projects moving from Bugzilla to JIRA, and I did it at my day job when we switched to JIRA. The links are useful for getting hold of the information that is lost in translation when moving to JIRA, stuff like comments for instance.
Using a suffix of @npanday.org seems like a good way to do it.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Joe Ocaba (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Ocaba updated INFRA-2940:
-----------------------------
Initial Developers: [brettporter, dennisl@apache.org, ipv6guru, jocaba, lcorneliussen, oching, wsmoak] (was: [brettporter, dennisl@apache.org, ipv6guru, jocaba, oching, wsmoak])
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-2940:
----------------------------
Assignee: Gavin
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Joe Ocaba (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Ocaba updated INFRA-2940:
-----------------------------
Initial Developers: [apadilla, brettporter, dennisl@apache.org, ipv6guru, jocaba, lcorneliussen, oching, wsmoak] (was: [brettporter, dennisl@apache.org, ipv6guru, jocaba, lcorneliussen, oching, wsmoak])
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909591#action_12909591 ]
Brett Porter commented on INFRA-2940:
-------------------------------------
Dennis, next question :) If I can extract more history (comments + change history) from Codeplex, is there a format JIRA will accept to import it as well? What should the format & data be?
I found that I was able to write a short app that could query Codeplex's TFS to extract all the history and comments from the tracker.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910283#action_12910283 ]
Dennis Lundberg commented on INFRA-2940:
----------------------------------------
It is possible to create the project first and import issues later.
The only downside of doing that is that issue numbers will be in the wrong order, with new issues at NPANDAY-1 and so on, and the older issues coming in with higher numbers.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Maria Odea Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated INFRA-2940:
------------------------------------
Attachment: JIRA_import_stats.rtf
JIRA_import_logs.rtf
Attaching import stats and logs from successful import of CSV file. We can track the issues that failed the import from the logs so maybe we can just clean it up in the CSV file or just file it manually?
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910016#action_12910016 ]
Brett Porter commented on INFRA-2940:
-------------------------------------
ok, so it seems we can concurrently create the JIRA project in this instance and use it for new issues, and load the data into a test instance until we're happy with it, then load that into the existing project
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906298#action_12906298 ]
Dennis Lundberg commented on INFRA-2940:
----------------------------------------
I'm almost done with the import data files. I have one question though:
What happens if not all Reporters have JIRA accounts? I've tried this on my local JIRA instance and it stops if I tell it not to create the users. Not all reporters in the Codeplex issue tracker have accounts in ASF JIRA. It would be a shame to loose the Reporter data.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated INFRA-2940:
-----------------------------------
Attachment: npanday-jira-import-2010-10-05.conf
NPanday Work Items 2010-09-03 2.csv
Another try with new configuration and CSV files.
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-03 2.csv, NPanday Work Items 2010-09-12.csv, npanday-jira-import-2010-10-05.conf, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2940) Create JIRA project for the NPanday
podling
Posted by "Maria Odea Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916340#action_12916340 ]
Maria Odea Ching commented on INFRA-2940:
-----------------------------------------
>From our conversation in #asfinfra, Brett listed the following things that need to be changed/corrected based from the test import before proceeding with the actual import:
* set resolutions on closed issues
* change "ID" custom field to "Codeplex ID"
> Create JIRA project for the NPanday podling
> -------------------------------------------
>
> Key: INFRA-2940
> URL: https://issues.apache.org/jira/browse/INFRA-2940
> Project: Infrastructure
> Issue Type: New JIRA Project
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Joe Ocaba
> Assignee: Gavin
> Attachments: JIRA_import_logs.rtf, JIRA_import_stats.rtf, NPanday Work Items 2010-09-12.csv, npanday-jira-import.conf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.