1, there are tools that can help us to keep the submitted issues, like https://github.com/bongohrtech/jira-issues-importer/tree/lucenenet.
2, of course, GitHub Issue has a lot of features that are very convenient for version management, Milestones, labels, and assignees are great features to filter and categorize issues. On 2021/07/23 07:40:06, Goson zhang <[email protected]> wrote: > I have two questions: > > How to deal with the issues submitted before? > Is the issue version management of Github convenient? Jira is good at > version management > > guo jiwei <[email protected]> 于2021年7月23日周五 下午3:22写道： > > > +1. > > At the beginning of the project, I had posted an email for discussing this, > > but kept using JIRA then. > > Now we discuss this again , I think it's a good idea to use github issues. > > > > > > > > Regards > > Jiwei Guo (Tboy) > > > > > > On Fri, Jul 23, 2021 at 3:14 PM Charles Zhang <[email protected]> > > wrote: > > > > > Hi guys, Can we use GitHub Issue to replace JIRA？ > > > If we migrate issues from JIRA to GitHub, it could make InLong record > > > and show issues easily, and it could help beginners to a quick start. > > > JIRA is a little troublesome for beginners to report issues, they have > > > to register an account and be authorized. And according to > > > https://issues.apache.org/jira/browse/INFRA-20118, there are some tools > > > that could help us importing our JIRA issues into GitHub. > > > I found lots of apache projects are using GitHub to record issues, like > > > Pulsar, superset, SkyWalking, etc. GitHub’s issue has great features like > > > Milestones, labels, and Assignees, it could help InLong to track tasks, > > > enhancements, and bugs. > > > What is your opinion? > > > > > >
