Tag Archives: JIRA
A couple of weeks ago we announced that we were moving from a hosted instance of JIRA to our self hosted instance. The main reason was that we hit 2000 active users in the hosted instance of JIRA and that is the upper limit that it supports. We obviously wanted to allow more people to be active in reporting and commenting on bugs and features for MariaDB. That’s why we set up our own instance, which now is up and running at jira.mariadb.org.
Thank you Atlassian, the company behind JIRA, for providing the hosted instance of JIRA for the MariaDB project over the last three years! …
Continue reading “Eating our own dog food – Running JIRA on MariaDB”
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:
In June, I told about the consolidation of the MariaDB project tools. The final piece of this consolidation, to report bugs in the MariaDB project tracking tool called JIRA has now been finalized.
Bug reporting stays open! JIRA is open to anyone. The bug reports are publicly available, even without logging in and as a bonus it will be easier to follow what is going on in the project since you don’t have to jump between several tools to get the complete picture.
All bugs that existed in Launchpad have been migrated to JIRA. To find a bug that was originally reported on Launchpad use the following approaches:
- If you happen to have the original bug id you can search for the bug by typing lp:bugid into the search field in the upper right corner of JIRA.
Continue reading “Making it easier to follow and participate in MariaDB development”
It is not a secret that we’ve been kicking the tires and playing with JIRA for project management. After using it since the beginning of the year most of us like the feel of it and we’ve decided that it makes sense to start using it more.
As you know, the MariaDB project has many fragmented resources. We report bugs in Launchpad. We store our plans in worklog. We’ve never used the Launchpad Blueprint feature for this very reason. We don’t use Launchpad Answers because we have the Knowledgebase.
With this move to hosted JIRA (yes, this is an important link: https://mariadb.org/jira) we can report bugs, have future plans, and also give users a roadmap which is pretty cool. …