Jira Software is an issue tracker and agile project management application. Portfolio for Jira Portfolio is a separate add-on that enables portoflio management in Jira Software. Jira Service Desk is a separate application to enable IT and customer service capablilities. Jira Core is a scaled down version of Jira Software that contains the general project managment capabilities without the software and agile-specific functionality of Jira Software.
Jira is available via 3 deploment models:
Probably some of these features could be worked around in GitLab (e.g. by using labels exclusively). In particular for our organization we have been using Jira for much longer than GitLab. Migrating to another issue tracking system for existing project would be less than trivial, i.e. if one wants to maintain the history.
Agreed that the problem isn't directly Jira, but (anecdotally maybe) there seems a clear correlation between Jira and unhappy developers who feel their tracker has way too much process. Jira doesn't cause the root problem, but Atlassian are profiting from it existing, and so maybe people are encouraged to use it in those ways. I'm not letting it off the hook so easily.
JIRA makes it dangerously easy to implement overly bureaucratic processes. A certain kind of organization is drawn to it for that reason. Even a healthy organization switching to JIRA can get carried away with the tools now at its disposal.
GitLab has Jira integration that allows Jira Software to be used as an issue tracker for the planning stage while using GitLab for the rest of the DevOps lifecycle: source code managment, CI/CD, and monitoring.
A few missing features in GitLab that JIRA has from this comment