Live data from Hacker News

A Simplified Jira Clone Built with React/Babel and Node/TypeScript

github.com

21–30 of 101 posts

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#21
post #18

Earlier quoted context omitted.

I don’t think people like using JIRA in general, especially after companies bloat it with a number of useless plugins that only certain teams will use.

After being forced to switch from Jira to a much less capable system, I now wish nobody had complained about Jira. Grass is always greener.

I would much rather not deal with jira tbh. Some companies take it too far and use jira as a micromanagement tool.

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#22

maybe dont call it jira_clone. People dont like installing something called a "clone". Brand it differently and build something really cool here

But it is a (superficial) jira clone. As it stands, it's just a fun project with no commercial value

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#25
post #3

The real issue with jira is how unresponsive the backend feels.

First, this clone looks very nice and worth trying if your workflow fits it. If this tool is still needing some feature you want, Do you run JIRA cloud? Jira by no means is perfect. It's one of the few tools that can handle complexity. I noticed a huge leap in JIRA speed in switching from cloud hosted Jira to self-hosting. On Cloud, Atlassian is mischievous and aggressively optimizes and constrains the resources. If…

That's disappointing. I've always had self-hosted Jira and was hoping Jira Cloud would be more performant.

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#27
Creator of "Jira Clone" here.

First of all I want to make it clear that this is just a showcase/demo product. It's definitely not something I'm planning to sell.

Additionally, it's not even remotely production ready, and it's missing about a zillion features that would make it a full-fledged project management software.

The main reason I built this was to have a good showcase for potential future clients.

The second reason was to share with the community. More specifically to show how to organize non-trivial React projects and to provide folks with a bunch of React code to learn from.

The third reason was to improve my skills and get better at working with hooks, TypeScript, and a couple of other things.

Back when I was learning React (4 years ago) I was a bit frustrated by the lack of non-trivial example projects. It was either a bunch of to-do lists, or hugely complex codebases like https://github.com/Automattic/wp-calypso.

I like to think that this Jira Clone presents a nice middle ground.

Bonus: Here's a Trello clone I built while learning React four years ago: https://boxd.ivorreic.com/ :)

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#28
post #18

Earlier quoted context omitted.

I don’t think people like using JIRA in general, especially after companies bloat it with a number of useless plugins that only certain teams will use.

After being forced to switch from Jira to a much less capable system, I now wish nobody had complained about Jira. Grass is always greener.

relatively new DevOps user here - I miss Jira too...

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#29
post #5

What motivated you to develop your own query and mutation hooks? Was there something unsatisfying with things like swr and react-query, or were you motivated to demonstrate/learn how to do it yourself?

I wanted to get better at writing hooks and working with hooks. Learning was one of the reasons for creating this in the first place.

Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript

#30
post #21

Earlier quoted context omitted.

After being forced to switch from Jira to a much less capable system, I now wish nobody had complained about Jira. Grass is always greener.

I would much rather not deal with jira tbh. Some companies take it too far and use jira as a micromanagement tool.

I’ve found jira dysfunction often reflects the dysfunction of the underlying corporate structure.
Post reply on HN