Our Blog: updates and reflections from the Matterhorn team

Get notified of the things that Matter

Notifications are a really helpful way of keeping up with what you need to know in a project. It’s also a great way of making sure others know what you need them to know!

We’ve implemented two types of notifications - @mention notifications and ticket assignment notifications.

While Matterhorn is designed to let you do your own thing when you want to focus on the tickets on your dashboard, it is equally important for you to know when you’re needed on something new. This is why we’ve decided to start with only these two notifications.

Using @mention Notifications

@mention Notifications can be used to make sure a certain person sees what you need them to see. If you’ve used Twitter, Slack or Flowdock, you probably already know how these work:

To send a @mention notification, simply type @ in any comment field.

This will bring up a list of your team members. Select the team member you want to notify by either using the arrow keys and pressing enter, or clicking and selecting the person you want.

You can @mention in any part of your comment - it doesn’t have to be done at the beginning.

You can send @mentions notifications to multiple people in one comment

@mention notifications use @mention nicknames

By default, your @mention nickname is a lowercase combinations of your First Name and Last Name.

You can also @mention by typing or pasting in the users full @mention nickname

You can personalise your nickname by going to My Profile from under the Settings Tab.

If your registered as John Adams your default @mention nickname would be @johnadams.

Your @mention nickname only needs to be unique within your team. Having unique nicknames ensures you don’t notify two people at once if they share the same name.

Assigned to Notifications

Matterhorn will also notify you when tickets are assigned to you. This means you can always keep track of when you have new tickets, and makes it easier to catch tickets that have been assigned to the wrong person.

Matterhorn will notify you when:

  1. A new ticket is created that is assigned to you
  2. An existing ticket is assigned to you
  3. When a ticket is assigned to you through the planner

Receiving notifications

Notifications are received in real time, as soon a comment with a mention is sent or a ticket is assigned to you. Notifications will appear in the sidebar (as a number).

Matterhorn will play a sound to let you know that you’ve received a new notification

Hover over me to get a notification sound!
Credits to Soundbible for the great soundbyte

Notifications live on your dashboard as cards above the Activity Feed. Clicking the orange header of the notification will take you to the context of the notification.


Dismissing Notifications

Clicking on a notification header will automatically mark it as read. To dismiss notifications one by one, press the trashcan icon in the bottom right corner. You can also dismiss all of your notifications by pressing the “Mark all as read button”

Email Notifications

By Default, Matterhorn will email you when you receive a notification. You can turn this off by going to My Profile from under the Settings Tab.

A new way of getting around Matterhorn

For a while, we’ve been debating what to do about the navigation in Matterhorn.

While we liked the simplicity of the navigation we originally designed, there were a lot of avenues we’re we thought it could improve.

These were the issues we wanted to solve:

We wanted a more easily understandable UI especially for new users. We were using icons with hover-over tooltips which meant you had to hover over a link to see what it was for. This wasn’t very effective for telling new users where to find what they needed, nor was it very useful to users who already knew what each icon meant.

We needed a home for quick access to projects. We began to realise that having to click twice to navigate between projects eventually was a major frustration. We needed a way to allow users to quick access all their projects straight from the navbar.

We wanted to introduce notifications. The old Matterhorn design used the logo to take the user to “home”, which was really their dashboard. This wasn’t clear enough and we expected that adding notifications to this mix would confuse users.

We needed to add more links without making the nav confusing We’d added integrations & account settings, but putting both of these as icons in the main nav didn’t make much sense. We knew there should be a subnav for links that weren’t likely to be used all the time, but this clashed with the tooltips.

We took all of these considerations into account, and set about redesigning the main navigation.

The Result?

Why another sidebar style nav?

We were considering going with a more conventional top bar nav, however there were a number of advantages to a sidebar nav that eventually won us over:

Screen Height is important to Matterhorn - as tickets are stacked vertically, more height means you can see more tickets at once!

Laptops and desktop screens generally have more width than height.

A top nav design uses up some of that precious screen height - especially if you want it to be fixed, and also if you have other levels such as project level navigation.

The sidebar meant that the list of projects could always be visible, whereas the top nav would have to have it under a dropdown - therefore it wouldn’t significantly speed up project navigation

Give me the tour already!

Settings Tab

The top part of your navigation will display the Company Name you registered with. Clicking in this section will open up the Settings Tab

Company Settings is where you access your company’s subscription plan, and also where you can manage and invite team members.

Configure Integrations is where you can set up integrations with other services.

My Profile is where you can change your account details, including your email, @mention nickname and whether or not you want to receive email notifications.

Sign Out for when you need to switch accounts or be secretive!

Dashboard & Planner

This section links to your Dashboard. This is where you can access your “to do today” list, notification and activity feed.

The red bubble to the right shows the number of notifications you have.

You can access the planner as usual by pressing the blue planner button

Project quick access

This is the list of all your Matterhorn projects, in alphabetical order. You can navigate to a project by clicking on it, or add a new project by pressing the "new project" button.

For the All Projects overview page, you can press the "view all" link.

We are working on implementing a search function here so that you can get to the project you want even easier.

Love it? Hate it? Need more help?

We’re always interested to hear your views on Matterhorn. If theres anything you’d like to congratulate us on, that you’d like to change, or that you’d prefer to have clarified, don’t hesitate to Get in Touch

Introducing a new & improved GitHub Integration

Last month, we introduced GitHub integration to Matterhorn projects. However, we know this is a really important feature, and want to make it the best that it can possibly be. That’s why we’ve been hard at work to bring you an even better GitHub integration.

We’ve overhauled the way Matterhorn integrates with GitHub in order to allow you to:

  • Manage all your project integrations in one place instead of on a project only level.
  • Link multiple GitHub repos to one Matterhorn project
  • Create and Close tickets through GitHub Issues
  • Track comments from

Setting up your GitHub Integration

Matterhorn’s new GitHub integration uses oAuth tokens rather than webhooks.

The GitHub integration works on a company level. This means as soon as anyone authorises with their GitHub account, everyone in the team will be able to link Matterhorn projects to any repo accessible by that account. We recommend that the main account holder links their account.

To set up your GitHub Services, go to Configure Integrations under the Settings Tab.


Click on the Connect with GitHub button. This will bring up a popup asking you to confirm that you want to give Matterhorn permission to access your GitHub account.

Matterhorn requires full access in order for the issues integration to function. If you have any questions or concerns about this you can contact us.

Linking up your repositories

After giving Matterhorn access to your GitHub account, you can start linking your GitHub Repos with your Matterhorn Projects. If no projects are linked, you will be taken to the “quick link” screen. Here you will see a list of all your Matterhorn projects on the left, and dropdowns with your GitHub repositories on the right.

You can then select the repo you want to link to each project, as well as what events you want to listen to.

Matterhorn can listen to these events:

  • Commits pushed to the repository
  • New comment on commit
  • Pull request opened or closed
  • Issue opened, closed, assigned, or labeled
  • New comment on issue or pull request

Unfortunately, event listeners cannot be configured after the service has been created. If you need to change these settings later on you will have to remove and recreate the service.

If there are Matterhorn projects you don’t need to link up, you can remove them from the quick link list by pressing the red cross. When you’re happy with your settings, press Create services.

Managing & Adding services

After setting up some initial services, you can always return to Configure Integrations to edit and add services.


From this screen, you can remove existing services or add a new service. To add a new service, select the Matterhorn Project and GitHub repo that you want to link up and press Create Service

Using the GitHub Integration

Setting up your account

When we connect to GitHub in this way, we only know who is creating or commenting on tickets by their GitHub username. Make sure to enter your GitHub username in My Profile (under the Settings Tab)

GitHub Commits and Matterhorn

As in the previous integration, you can reference tickets in your commits via their ticket id (by writing the full number including the hash eg #162).

  • If you just leave a reference, this will be added as a comment to the ticket
  • If you’re starting work on a ticket, you can move it to in progress by having the ticket id and any of these words in your commit message. breaks, unfixes, reopen, reopens, re-open, re-opens, open, opens
  • If you’re starting work on a ticket, you can move it to complete by having any of these words in your commit message. close, closes, closed, fix, fixed, fixes

GitHub Issues and Matterhorn

Any issues you create in GitHub will now be added as a ticket in the linked Matterhorn project. These tickets are automatically grouped under the Feature GitHub Issues, to help you keep track of them. You can change the feature of a GitHub Issue ticket after creating it.

Commenting on a GitHub Issue will add a comment to its corresponding Matterhorn ticket.

Closing a GitHub Issue in GitHub will Close the issue in Matterhorn.

Box and Dropbox come to Matterhorn

Today we’re excited to launch two great integrations in one: Box & Dropbox

Sharing files is such an important part of working together, and we know how restrictive it can be to have to keep files on your computer. Most of us use some kind of online file hosting service, not only so we can access it from everywhere, but also to allow us to share files easily within a team. That’s why we decided to make sharing files from these services to Matterhorn as easy as possible.

There are now three ways of attaching a file to a feature discussion: from your dropbox account, your box account or your computer.

Attaching Files with Dropbox

To attach a dropbox file to your discussion, click on the green “click or drop a file here to upload” section, and select dropbox from the list. This will bring up the dropbox chooser and you will be able to select files and photos from your dropbox account.

Attaching Files with box

To attach a box file to your discussion, click on the green “click or drop a file here to upload” section, and select box instead. Then simply browse to the file you want and press select.

How it works:

Files will be attached as links at the end of your feature discussion. The coolest thing about this? Attaching files in this way means that any file in your discussions will always be up to date with the latest version that was saved in your box or dropbox account!

We will be looking at allowing you to include these links inline in your discussion so that you can reference your files even more efficiently.

File sharing updates in the pipeline

We believe that sharing files within the right context is one of the most efficient ways to communicate with your team, and that is why we’re working hard on bringing you even more improvements to the Matterhorn file sharing experience.

Here are a couple of improvements that we hope to roll out within the next few weeks:

  • Allowing you to insert Box & Dropbox files inline in your discussions so you can reference them even more efficiently
  • Thumbnail previews of files you’ve attached so it’s easier to make sure you’ve got the right one.
  • Allowing you to attach files to tickets
  • Allowing you to attach files to ticket comments

Let us know your thoughts: what other file sharing functionalities would you like to see?

GitHub, Meet Matterhorn

Over the last couple of weeks, we’ve been hard at work building out first integration…and it’s a good one!

GitHub is our (and probably everyone else’s) favourite place to store our code - so it was an obvious match for Matterhorn.

From today you can integrate Matterhorn with GitHub. By using certain strings in your commit messages, it will automatically move the ticket in Matterhorn.

How do I integrate GitHub with my Matterhorn project?

  1. Go to your Matterhorn project page and click on the cog in the top right to get to your project settings.
  2. Paste the Git URL* from your project’s GitHub Repository into the box on the integrations panel.
  3. Visit the settings page in the GitHub Repository and select Webhooks & Services**. Now click “Add Webhook”.
  4. Copy the provided Payload URL from the integrations panel into the webhooks “Payload URL” field. (this URL is private and unique to your project)
  5. Save and start moving around tickets with Git!

*If you need help finding your git URL, you find it in this box in your repository

**This is what the webhooks page looks like

How do I use the git integration?

Referencing tickets

Each ticket has a ticket id. You reference the ticket in github by using a # followed by the ticket id for example #162

If you just leave a reference we will add a comment to the ticket like so:

Moving tickets

Referencing is only the start of the integration. You can also move ticket around the board via the message

Opening Tickets

If you’re starting work on a ticket, you can move it to in progress by having any of these words in your commit message. breaks, unfixes, reopen, reopens, re-open, re-opens, open, opens

Completing tickets

If you’re starting work on a ticket, you can move it to complete by having any of these words in your commit message. close, closes, closed, fix, fixed, fixes

Here’s an example:

bash git commit -m "Implement GitHub Integration fixes #1540"

This will move the ticket to the complete column in Matterhorn :D