Jira Clone
A simplified Jira clone built with React/Babel (Client), and Node/TypeScript (API). Auto formatted with Prettier, tested with Cypress.
It's only a showcase product. The last commit is from 3 years ago, with many features marked as “not implemented” in the linked website.
Features
- Jira
- Issue Tracking
Tags
Jira Clone News & Activities
Recent News
Recent activities
ouraboard added Jira Clone as alternative to Ouraboard
eluzja added Jira Clone as alternative to Kanba and Tasks.md
Extropista added Jira Clone as alternative to Operately
POX added Jira Clone as alternative to Deploy Path
POX added Jira Clone as alternative to Kan.bn
Jira Clone information
Developed by
Ivor ReicLicensing
Open Source (MIT) and Free product.Written in
Alternatives
245 alternatives listedSupported Languages
- English
AlternativeTo Categories
Development, Business & CommerceGitHub repository
- 11,063 Stars
- 2,147 Forks
- 10 Open Issues
- Updated
What is Jira Clone?
A simplified Jira clone built with React/Babel (Client), and Node/TypeScript (API). Auto formatted with Prettier, tested with Cypress.
What is this and who is it for?
I do React consulting and this is a showcase product I've built in my spare time. It's a very good example of modern, real-world React codebase.
There are many showcase/example React projects out there but most of them are way too simple. I like to think that this codebase contains enough complexity to offer valuable insights to React developers of all skill levels while still being relatively easy to understand.
Features
- Proven, scalable, and easy to understand project structure
- Written in modern React, only functional components with hooks
- A variety of custom light-weight UI components such as datepicker, modal, various form elements etc
- Simple local React state management, without redux, mobx, or similar
- Custom webpack setup, without create-react-app or similar
- Client written in Babel powered JavaScript
- API written in TypeScript and using TypeORM
Comments and Reviews
While it does look good per se, its only a showcase product and not a actual software being developed.
If cloning an epic is not just a flash in the pan for you, but you want to repeat it multiple times, your epic is a process because recurring projects are processes!
Flower - Process Automation clones your Jira epics as repeatable processes, including all issues, links, and structures.
Here is how to clone an epic as a process.
https://flower-bpm.com/docs/clone-jira-issues