The Complete Starter Guide

We're super excited that you decided to start using Anaxi--but where to begin? Here's a comprehensive guide on everything you'll need to get set up, in just 3 minutes!

Before you start, there are 2 things you need to know:

Your data stays 100% secure!

Let me tell you how. We don't store any of your issue-related or code-related data in our servers, that also applies to your credentials and tokens, which stay in your browser or device. Any data is computed directly from GitHub and Jira, we never handle them directly. So you can safely connect your account. Here is an article on the data we store if you want to learn more.

No need to switch tools for you or your team

Anaxi is built on top of Jira and GitHub. Any action you do on Anaxi is written back on the original tool. So you can start using Anaxi alone, and have your team continue using Jira for instance without realizing you have become way more productive using Anaxi ;).

Ok so what do you do after you sign up:

1) Connect your accounts 

You can safely connect your corporate accounts and personal ones. We don't integrate them together. We give you an interface to easily manage them. And as mentioned, we never access or store your data.

Anaxi is built on top of Jira (Cloud and Server) and GitHub (Cloud only, Enterprise is coming soon). 
Note to authorize access to your organization, you need to see with your admin so she accepts the request. 

2) Add your projects 

You can add any number of projects. We encourage to add them all as keeping track has become easy with Anaxi. 
Some default filters will be added for each project you add. Those filters' goal is to show you what you can do with Anaxi. So the next step is to build your filters and folders.

3) What can you do with filters?

Filters give you all the information you need for the tickets/PRs within the filter in several ways. Let's say you have a filter for your current sprint:

  • The feed gives you all the latest activities in the sprint, threaded by ticket for better understanding. 
  • The list gives you a fast interface to manage all the tickets concerned

Your filters will have state indicators. Red triangle signals an alarming state. You can edit the indicator settings by clicking on them in the filter page. You can set up a due date so the threshold will take the due date in consideration. 

You can organize your filters into folders, the folders will show the color of their most alarming reports. 

4) Examples of filters you may want to create

  • One filter for your current sprint or milestone
  • One filter for the component or epic that you are responsible for, if you ever are
  • One filter for the pull requests assigned to you 
  • One filter for the pull requests that you created
  • If you use issue states, issue filters filtered by the "resolved - to test" for your next milestone (if any) - that can help you have a sense of your team+QA workflow, or if there is any bottleneck
  • Weekly activity report for you and all your team member at once, for each of your projects.

And many more, that you can add according to your team's process.

Don't hesitate to organize them by folders. For instance, a folder for each team, and a subfolder for each project of the said team.


That's it! You should understand how it works :). Don't forget to download the iPhone app too!

Did this help answer your question?

thumbs up
thumbs down

Thanks for the feedback! 🙏🏽

Help by drift