# Update of Slicer issue tracker

**URL:** <https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437>\
**Category:** Development\
**Tags:** web-infrastructure\
**Created:** [June 2, 2017, 9:17pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437 "2017-06-02T21:17:49Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [October 29, 2018, 7:26pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/8 "2018-10-29T19:26:50Z")

</div>

Bumping this thread since there’s already been some good conversation on this topic.

I have found it pretty difficult to use the search within the Mantis Tracker to find relevant results. It’s hard to quickly find if there is already an issue for a bug that I observe.

ITK recently moved from their issue tracker (JIRA) to GitHub issues. See this [post](https://discourse.itk.org/t/issues-in-github/1218/15) on their forum. Here is another [post](https://discourse.itk.org/t/github-issue-labels/1256) they had about using GitHub labels. For the most part I think Github Issues, Labels, and Milestones could replace a lot of primary functionality in the issue tracker. There isn’t default assigning of issues, but maybe some github apps could supplement any missing features.

---

_[View the full topic](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437)._