# Why do you use Jira, not Gitlab?

**URL:** <https://forum.mattermost.com/t/why-do-you-use-jira-not-gitlab/244>\
**Category:** Troubleshooting\
**Created:** [September 25, 2015, 12:19am UTC](https://forum.mattermost.com/t/why-do-you-use-jira-not-gitlab/244 "2015-09-25T00:19:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![it33](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/it33/32/3_2.png) [@it33](https://forum.mattermost.com/u/it33)\
**Post date:** [September 25, 2015, 1:10pm UTC](https://forum.mattermost.com/t/why-do-you-use-jira-not-gitlab/244/6 "2015-09-25T13:10:47Z")

</div>

Thanks everyone for the feedback.

Mattermost uses [GitLab](https://gitlab.com/gitlab-org/gitlab-mattermost/issues?assignee_id=&author_id=&label_name=&milestone_id=&scope=all&sort=created_desc&state=all) to communicate with the GitLab Mattermost community and we have [a product page there](https://gitlab.com/gitlab-org/gitlab-mattermost).

Yes, we have a lot of communication channels. Our current thinking is that:

####a) We want to make it easy for people to communicate.

Some users prefer forums, some issues, some mailing lists, some tweets, given the 1% rule (i.e. 99% of internet readers don’t speak), we want to make it as easy as possible to hear from the community.

Regarding Jira specifically, this comes from our previous life as a video game company, where Jira is largely the standard. Our processes work well in Jira Agile and we’d rather spend our energy building for the community than changing something internal that is working.

####b) Using a broad range of communications helps us build infrastructure to support a diverse set of future integrations.

It’s definitely a lot of work for us to monitor everything–and we’re far from perfect. However this pushes us to build internal integrations with Mattermost that we can later bring to the community.

---

_[View the full topic](https://forum.mattermost.com/t/why-do-you-use-jira-not-gitlab/244)._