To address your points specifically
Quote
↩ characterslimits Taiga is open source
Taiga is open source while Jira is proprietary software. Taiga allows you to do more things with it's code and it allows anyone to view the source code
From my perspective this is not a feature that adds value, we wouldn't look to modify the source code anyway. We don't have time to do that or the need / will to do this so offers no advantage over the current cloud hosted and ATLAS Supported tool.
Quote
↩ characterslimits Taiga allows guest access for free
About a month and a half ago, I pointed out that there is a lack of transparency between the developers on TotalFreedom. Taiga allows you to create public projects for free which allows us to see what developers are doing and it fixes the transparency problem we have. Jira forces you to pay a fee to allow guest access to see your projects.
Yes, I agree this is a benefit over Atlassian Cloud, though not over Jira as a product. We could have considered looking for an Atlassian open source license, but most of our projects don't fit into that.
Quote
↩ characterslimits Taiga is more secure
Taiga is more secure than Jira because it's open-source. Anyone can audit the code of Taiga and check to see if there's a security issue and report it if there is one. For Jira, you cannot see it's source code. The only way to know if there is one is that we're the first to be attacked, or if we're notified by Jira themselves.
This as I said is absolute nonsense, open source does not mean more secure. Atlassian has been around for a lot longer, and with it being an enterprise product with an enterprise price tag, means they are paying for security specialists to regularly audit and pen test. It's also US FEDRAMP Moderate accredited which allows it to be used for sensitive us DoD projects, so I'll trust Jira over Taiga.
Quote
↩ characterslimits Taiga is highly customizable
The On Premise version of Taiga gives users 100% control over the software, which means you can basically do anything you want with Taiga. Jira is a cloud based solution, which means they have control and they can suspend your project at any time.
Again, gives us no benefit because we wouldn't want to customise it, and Jira let's us customise it as much as we need it to... We use Jira Cloud but could use the on-prem version if we wanted to pay for it, and likewise Taiga cloud could suspend our projects at any time... This entire point is moot.
Quote
↩ characterslimits Taiga has a built-in importer
Taiga has a built-in importer, so you can transfer everything from Jira to Taiga.
Not really a feature when you don't want to use it in the first place, offers no advantages over Jira.
Quote
Compared to Jira the UI is dated and lacks clarity and functionality from what I can see, not really something that gives me confidence to want to move to it.
Now, some reasons we do use Jira
- It's already ATLAS's tool of choice for Project Management like this.
- It's got an excellent reputation as being a provider of enterprise security and functionality, and being a leader in the agile software development space.
- It does everything we need it to do.
- It links very nicely into Confluence (Which we use for Wiki tooling) and also Github
- It's free and cloud managed in an enterprise environment
- It doesn't require me to host additional servers / infrastructure.
Now, if TF actually grows to the point where we have enough developers that we breach the Jira Cloud Free Tier of usage, we would look to re-visit the tooling choice and decide if paying for Jira cloud is a good idea, or if alternatives are going to provide us with better value, but right now given the free tier works well and we have plenty of space on it, and the fact that every time we've tried to get the community involved in the development we've had 0 contributions, the con's to me outweigh the benefits.
If someone can give me a reason we should put the effort into moving away from an enterprise ready solution we already have and that I'm personally very experienced in managing, I'd love to hear valid arguments for why we should leave Jira.