> It's a project management app. It does nothing else.
I would say it doesn't do that very well. You can't manage projects without mapping out dependencies, visually and with integrated relationship tracking. JIRA is miserable at this.
Notion databases easily allow dependencies, integrated relationship tracking and multiple ways to visualize a project roadmap. Can't speak to JIRA but Notion is continuously releasing new updates that respond to user needs. There is a major downside to this of course. As a solopreneur I find it frustrating that Notion's updates tend to serve corporate needs, but it's a good business strategy and allows Notion to continue to serve others with its free version.
people also use jira as a support ticket system.
Sprint planning system.
Kanban system.
I’ve seen it set up so that it can track work across kanban teams and scrum teams.
Jira has deep integration with bitbucket, confluence, and GitHub.
It can manage your CI pipelines as well.
Jira is an anything app with a bend towards project management.
Setting up jira workflows is a whole career.
Source: I worked at Atlassian for 5 years and they use jira as the backbone for _everything_. It all flows into jira.
people also use email as a support ticket system. Sprint planning system. Kanban system. I’ve seen it set up so that it can track work across kanban teams and scrum teams.
Email has deep integration with bitbucket, confluence, and GitHub.
Email can manage your CI pipelines as well.
Email is an anything app with a bend towards project management. Setting up email workflows is a whole career.
Source: I worked at Google for years and they use email as the backbone for _everything_. It all flows into email
a) Support tickets, sprint planning, kanban etc are all part of project management.
b) It can't manage your pipelines. It can visualise deployments and link them to work but you still need some sort of CI/CD tool like Bitbucket, Github etc.
c) It is not an anything app. I can't use it as a wiki, CRM, database, calendar etc.
B) it can manage pipelines through those services. Each card change would kick off pipelines whose status updates would cause jira to further change cards potentially kicking off more ci/cd steps.
C) you absolutely can use it as a database, calendar, and a wiki.
It has an api and can store data. You can query cards by label, search by content, and extract structured information from them.
Nested and linked cards provide the tools needed to build wikis.
I’m not 100% sure what the difference between CRMs and support ticketing system are, but Jira instances have been used as support ticketing systems in order to give devs view into what customers want.
It’s not the best at any of those things, but those are all doable (and are being done) with jira.
Yeah… that’s Atlassian for you. Why sell just Jira when you can sell jira, confluence, bitbucket, opsgenie, and atlas as part of the Atlassian cloud platform.
This is the company that (already having owned jira) bought trello and did nothing with it for 5 years.
The 4th, a Wiki, is of course more-so just Confluence, but I have seen echoes of a wiki make their way into Jira; e.g. in one place I worked, every release was a ticket that was duplicated from a previous ticket, and that ticket had step-by-step instructions on how to run different parts of the release.
You're just wrong on this, bro. Notion tries to be everything to everyone. Jira is everything to everyone, it doesn't matter what it tries to be.
It's amazing how people think Project Management = Issues (and only issues).
Release Management is a fundamental part of IT Project Management. So of course companies use Jira to track releases. And of course you can tie milestones and OKRs to releases. And of course tickets can have small amounts of text content associated with them. How else would you describe the ticket without them ?
But the idea of Jira being remotely like a Confluence style wiki is just ridiculous.
And your comment is out of some parallel universe where Jira is Confluence.
You must of missed the multiple points where I said "three out of four" and "echoes" of a wiki; but reading comprehension is hard, don't worry you'll get 'em next time.
I would say it doesn't do that very well. You can't manage projects without mapping out dependencies, visually and with integrated relationship tracking. JIRA is miserable at this.