Is Jira the place to fill the issue?
Or is Github the right one?
Why use two issue tracking?
Jira was the old way of filing issues. I believe they have migrated to GitHub for issue tracking. The Jira is there for historical purposes as this point.
@MattBertolini is right. Liquibase use Github for issue tracking in the community. JIRA use by community has been deprecated and only there for historical.
What kind of projects are you working on?
Using both Jira and GitHub can actually make a lot of sense depending on your team’s workflow. For example, when my team worked on a project, we used Jira to track tasks and bugs, utilizing the jira issue types to categorize everything—like stories, tasks, and bugs—making it super easy to prioritize. Meanwhile, GitHub was great for code reviews and managing pull requests. It felt natural to keep the coding and issue tracking separate, but linked them together when needed.
@Juravelyk as stated before, we use GitHub to track community issues. New PRs and issues should be filed at GitHub - liquibase/liquibase: Main Liquibase Source.
Jira has been deprecated and is only for historical reference.