vlsi commented on issue #124: URL: https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207193708
> Jira issues to GitHub while preserving the original contents as far as possible In the new world, you would have GitHub issues only, and new issues would reference other issues and PRs. The habit would be: there's a link, you can click to see the details. However, if you use "JIRA first, GitHub last" style for the migrated issues, then the pattern breaks. Consider: "new issue 123 references a migrated one 42 which references yet another migrated one 21" User opens "issue 123", and sees there's a link to 42, they click and open issue 42. So far so good. However, then they see "link to 21" which breaks the flow. They suddenly have to parse the message, and deliberately click on the second link (the first link for 21 would be JIRA). That is why I suggest following the pattern: prefer in-GitHub links first, and keep JIRA links as the last resort, so cross-navigation between issues and PRs is consistent for both migrated and the new issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
