Supporting continuity and open collaboration

MariaDB JIRA is moving

The MariaDB JIRA instance that currently is in use for project and issue tracking will change. The current instance is hosted in Atlassian’s cloud and it has worked well, but we have hit the maximum user limit of 2000 users. It’s fantastic to see how many of you actually report bugs and other issues in the MariaDB project!

To hit that limit also means that we have to migrate over to a self-hosted instance of JIRA. Below are important details about that change.

When will the switch happen: 
Sat 27th of Feb

What is the impact for me as a user of MariaDB’s JIRA:
1. URL change – The current instance is hosted in Atalassian’s cloud and has the URL The new one will be found at starting from 28th of Feb.
2. RSS feeds – If you have been using JIRA’s RSS feeds, you’ll need to set up them again since the URL is changing

What will happen to old JIRA:
The JIRA instance will be put into read-only mode and a banner will be visible on each page telling the URL of the new MariaDB JIRA instance. It will remain this way for some time since it has been referenced quite heavily from other sites.


  1. Craig Craig

    Atlassian hasn’t publicly supported their products running on MariaDB yet, does this mean they’ll now give it their blessing?

No Pings Yet

  1. Questions about MariaDB’s bug system | Todd's MySQL Blog on 2016-02-25 at 01:12
  2. Eating our own dog food - Running JIRA on MariaDB - on 2016-03-03 at 13:50
  3. Questions about MariaDB’s bug system | Database Administrator on 2017-02-20 at 05:31

Leave a Reply

Your email address will not be published. Required fields are marked *

Platinum Sponsors

MariaDB Foundation Platinum sponsors

Gold Sponsors

MariaDB Foundation Gold sponsors

Code statistics