You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@senssoft.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2016/08/15 21:29:20 UTC

[jira] [Commented] (SENSSOFT-1) Move Draper Jira Tickets to Apache Jira

    [ https://issues.apache.org/jira/browse/SENSSOFT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421708#comment-15421708 ] 

Joshua Poore commented on SENSSOFT-1:
-------------------------------------

Yep. I think tags or labels are the best bet for managing.

We use JIRA internally at Draper. Previously, we have done a clean JIRA ticket export, in bulk. We'll save our existing tickets in an xls format, edit them, then save as csv and import to this instance. We can test this internally at Draper on our test server. 

We are planning to keep as many tickets as possible public. We will omit things that are purely programmatic in nature.



> Move Draper Jira Tickets to Apache Jira
> ---------------------------------------
>
>                 Key: SENSSOFT-1
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-1
>             Project: SensSoft
>          Issue Type: Task
>            Reporter: Joshua Poore
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Move Draper Jira Tickets to Apache Jira



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)