> A tool that tries to be everything to everyone
Jira doesn't try to be everything. It's a project management app. It does nothing else.
Notion is wiki, CRM, project management, calendar etc.
Jira doesn't try to be everything. It's a project management app. It does nothing else.
Notion is wiki, CRM, project management, calendar etc.
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.
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.
This is the company that (already having owned jira) bought trello and did nothing with it for 5 years.
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
I mean email isn’t an app, it’s a handful of protocols, but… sure
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.
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.
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.