> Totally agree. The history of closed issues answer “when did this change
> and why?”. Migrate them all. Computers can do that. It avoids asking humans
> to think about where stuff is.
>
We do have different views of that. To me, the history is preserved
perfectly well in Jira, it's not being phased out. Moving to github as the
issue tracking system is fine but different to me than code transitions
(cvs->svn->git). With code, you do have an existing state and history
you build from. With issue tickets - not so much. And even if you want to
create a ticket in the new system, you can easily link to the previous one.
It's the "web" of hyperlinks, right?
I'm a bit afraid that moving hundreds of jira issues to github will have
the reverse effect - duplicate the same information but with quality
degraded, for example automatic links that work in Jira will no longer work
or point at the ported github issues ("this is related to LUCENE-xyz or
SOLR-abc, blah, blah blah.")?
I don't want to stand in the way of progress but we've gone through a
similar transition at our company and I never had a problem using both
systems at the same time; jira just gradually atrophied into a read-only
state once issues in there got stale or resolved.
Dawid
