5 Best Practices for Software Development with Mattermost Mattermost also has an integration with Jira , which works similarly. Try running `/jira help` in a conversation with yourself on Mattermost. Without leaving the team conversation in a channel, you can quickly spin up a new issue stub to track a request or bug. Any message can also be used to create or add to a GitHub issue or Jira ticket by clicking the message actions menu, then `create` or `attach to`. Team members can shut off notifications from ev- erything but Mattermost and stay focused while still receiving those critical review requests that keep work moving forward. With project tracking, the important thing is that work and the team’s time is counted, credited, and visible to everyone. It’s another way we can eliminate silos and keep the entire organization on the same page. Get the bird’s-eye view of what you can do with various integrations and open source magic for Mattermost . Use documented, repeatable, and shared processes Mattermost CEO Ian Tien recently wrote about how DevOps lost its way -- and how to bring it back , talking about the need for visibility and centralized, simplified interfaces. For ex - ample, DevOps best practices often rely on checklists. A team starting from scratch might run through a process, write down what they did, run it again, update the docu - mentation, then continue to use that same process and iterate. That team will need to provide updates and visibility into the process when it’s underway and afterwards in reports, and the checklist needs to be accessible and easy to update as the team learns and improves over time. Unfortu - nately, teams often rely on text documents, spreadsheets, wikis, and other tools that are both siloed and difficult to maintain.