Skip to content

Tools and support

In this article we will look closer at tools used in Easy8 and where you can get support.

There is a wide variety of tools used in Easy8. Some are used on a daily basis and you need to have access to them, some are used less often or could be never used by you.

Here goes the list of the tools used and what department takes care of it:

  • Common tools - back-office can help you get access
  • Microsoft Teams - instant messaging tool
  • Outlook email - email service
  • Easy8 - our own instance of our own product
  • Bitwarden - password management tool
  • Quality assurance - ask QA team
  • Playwright - tool for e2e automated testing
  • DevOps tools - ask operations' team
  • Easy Git - Easy8 git
  • Gitmakers - package manager
  • Bugsnag - error monitoring and stability management tool
  • Hookdeck - webhook management tool
  • New relic - performance monitoring tool
  • VPN - VPN for internal network
  • Internal development
  • EasyCLI - internal tool for developers
  • Nodes - package management tool
  • Gems - gems management tool

For Microsoft services (Teams and Outlook email) you will need to have a Microsoft account - if you do not have one yet, reach out to the backoffice team.

General rule of thumb is to reach out to respective team and ask for access.

MS Teams channel for help from developers

The channel to look for in MS Teams is Developers help. Head here if you need deeper technical insight.

Advanced technical support

This service alternates between Ruby developers.

People who are on duty have to:

  • Check and respond to chat, especially on channel Developers help. This is one of biggest responsibility.

  • Follows Support help channel and tries to help.

  • Solves tasks which are assigned to Easy Developers ( Technical Support) group (solve on your own, process them or delegate them...)

  • Monitors and solves bugs from Bugsnag:

  • Close rare case (and these, which are connected with application restart)
  • Reassigns non-critical bugs to QA (so the team can go through them during bug meeting on every Tuesday)
  • Critical bugs - make sure they are fixed (solve on your own, process them, delegate them,...)

Free time left? Solve bugs, do some refactoring and other stuff