[Bro-Dev] JIRA to GitHub ticket migration plan

Jon Siwek jsiwek at corelight.com
Thu Sep 13 17:39:35 PDT 2018

A preview of what migrated issues will look like along with new labeling scheme:


The selection strategy of which tickets to migrate is something like
"anything that is a reproducible bug or a simple/uncontroversial
enhancement".  Any tickets not in that preview list will be left open
in JIRA, but frozen as read-only.  Going forward, JIRA will serve as a
historical archive or Good Idea Backlog that we can occasionally pull
from, but that can be done manually whenever the situation comes up
(just create a GH issue and link to old JIRA ticket).

Remaining tasks:

* Perform the actual migration
* Update website/docs with new directions/process for issues
* Email bro + bro-dev mailing lists once tickets are migration
* Adapt workflow permissions for JIRA "BIT" project so it's read-only

I expect I'll do those next Monday unless there's objections or
feedback to address.

- Jon

More information about the bro-dev mailing list