When comparing JIRA vs Gitea, the Slant community recommends Gitea for most people. In the question“What are the best bug/issue tracking tools for small development teams?” Gitea is ranked 5th while JIRA is ranked 16th. The most important reason people chose Gitea is:
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Lots of integrations and plugins
It integrates well with a lot of other tools, including other products from the Atlassian suite. Plus there are a ton of plugins, including charting tools, screen capture, etc.
Pro Backed by a trustable company
Jira is developed and maintained by Atlassian, which is not an unknown venture, especially for developers. Atlassian has a great number of other products used by million of users worldwide, including BitBucket, HipChat, Confluence and Stash.
Each of these products have hundreds of thousands of users who use them daily and this has allowed Atlassian to garner a lot of goodwill from the dev community.
Pro Very cheap for small teams
Pro Supports version-focused work-flows
JIRA is not a plain long list of tickets, but can be configured to be version-focused, so planning and understanding the progress in a software project becomes clear.
Pro Great reporting tools
Jira offers amazingly powerful reporting tools like activity stream, different graphs of opened and closed issues over time etc...
Pro Light-weight
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Pro Open source and maintained by community
Unlike Gogs, which is maintained primarily by its creator.
Pro Intuitive interface
Easy to navigate around and feels very natural in general.
Pro Non-memory consuming
Just like Gogs, but with new features and fixed bugs. Unlike GitLab which is enormous.
Pro Wiki and issues
Like GitHub, a wiki and issues (bugtracking) can be added to a repository.
Pro Fast pace of development
New features, constantly updated.
Pro Like Gogs but with faster bug fixes
If you love Gogs but were frustrated with the long wait for bugs to be fixed, this is for you.
Pro Most common platforms
Versions available for Linux, Mac and Windows. This is possible because Gitea is developed in the Go language which makes it compact and fast too. Only one executable is needed.
Pro Easy install with MariaDB back-end
No problems getting to work with MariaDB.
Pro Simple to install/written in GO
Pro Package Registry
Supports NuGet, npm, Cargo, Composer, Maven, RubyGems etc.
To work with the NuGet package registry, you can use command-line interface tools as well as NuGet features in various IDEs like Visual Studio.
Pro Runs perfect on a Raspberry Pi 3
Thanks to its light-weight and simple integration.
Pro Customizable Templates
All templates can be overridden.
Pro Focus only on key features
And if you want extra features, you can use web hooks.
Cons
Con New releases often change the GUI largely
Sometimes the usage becomes worse, e.g. when creating a new ticket, you need to click the notification to keep it on the display.
Con Locks you inside its own ecosystem
If you use Jira you are pretty much locked inside their ecosystem. For example, if you want to add a tool to your project management stack (like a wiki) more often than not you will have to buy one of Atlassian's tools.
Con Client application support
No free client applications; IDE connector development was discontinued. Users are effectively locked into using web interface which requires context-switching.