# Issues: Jira ot Github

**URL:** <https://forum.liquibase.org/t/issues-jira-ot-github/4763>\
**Category:** Liquibase Development\
**Created:** [October 28, 2020, 4:06pm UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763 "2020-10-28T16:06:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mturra](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@mturra](https://forum.liquibase.org/u/mturra)\
**Post date:** [October 28, 2020, 4:06pm UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763/1 "2020-10-28T16:06:39Z")

</div>

Is [Jira](https://liquibase.jira.com/) the place to fill the issue?

Or is [Github](https://github.com/liquibase/liquibase/issues) the right one?

Why use two issue tracking?

---

<div class="post-metadata">

**Author:** ![MattBertolini](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/mattbertolini/32/210_2.png) [@MattBertolini](https://forum.liquibase.org/u/MattBertolini)\
**Post date:** [November 14, 2020, 2:35pm UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763/2 "2020-11-14T14:35:49Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ronak](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ronak/32/221_2.png) [@ronak](https://forum.liquibase.org/u/ronak)\
**Post date:** [November 17, 2020, 2:55pm UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763/3 "2020-11-17T14:55:33Z")

</div>

@MattBertolini is right. Liquibase use Github for issue tracking in the community. JIRA use by community has been deprecated and only there for historical.

---

<div class="post-metadata">

**Author:** ![Dahleander](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@Dahleander](https://forum.liquibase.org/u/Dahleander)\
**Post date:** [September 27, 2024, 8:40am UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763/4 "2024-09-27T08:40:25Z")

</div>

What kind of projects are you working on?

---

<div class="post-metadata">

**Author:** ![Juravelyk](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@Juravelyk](https://forum.liquibase.org/u/Juravelyk)\
**Post date:** [September 27, 2024, 8:59am UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763/5 "2024-09-27T08:59:44Z")

</div>

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](https://appliger.com/jira-issue-types-and-use-cases/) 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.

---

<div class="post-metadata">

**Author:** ![admah](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/admah/32/1238_2.png) [@admah](https://forum.liquibase.org/u/admah)\
**Post date:** [September 27, 2024, 4:21pm UTC](https://forum.liquibase.org/t/issues-jira-ot-github/4763/6 "2024-09-27T16:21:22Z")

</div>

@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](https://github.com/liquibase/liquibase).

Jira has been deprecated and is only for historical reference.