On Fri, Jun 17, 2022 at 12:08 PM Michael McCandless <luc...@mikemccandless.com> wrote: > > I agree the embedded links are tricky. Not sure whether we could do a big > rewrite of those links or not ... seems a chicken/egg situation. We could 1) > append a forwarding link comment on the Jira issue to its GitHub version, and > 2) make Jira read-only so the risk of a user adding a Jira comment on an old > issue that then goes into /dev/null, is gone. >
Couldn't we solve this with 2 passes? First pass: create GH issue corresponding to each JIRA issue: LUCENE-1000 -> issue #564 Second pass: "correct" references in the texts: LUCENE-1000 -> #564 You could also handle special "links" in JIRA issues with the same stuff, e.g. at the beginning of the GH issue, it could just have some markdown like: Links: * Relates to #476 Could also be a way to transfer over subtasks with some sanity, e.g. add "Subtask of #200" to the text somewhere. Then these would be "linked" in GH. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
