Wanna see something cool? Check out Angular Spotify 🎧

I built a Jira clone application with Angular 9, Akita and ng-zorro

There have been a handful of cool Jira-cloned apps written in React/VueJS, which makes me wonder Why not Angular? And here you go.

This is not only a simplified Jira clone built with Angular 9, but also an example of a modern, real-world Angular codebase.

Source code


Working application

Check out the live demo -> https://jira.trungk18.com

Jira clone built with Angular 9 and Akita

If you like my work, feel free to:

  • Tweet about Angular Jira clone
  • ⭐ this repository. And we will be happy together :)
  • Buy Me A Coffee

Thanks a bunch for stopping by and supporting me!

Who is it for 🤷‍♀️

I have been working with Angular for about four years. I built cool stuff at Zyllem but almost all of them are internal apps which is difficult to show.

This is a showcase application I’ve built in my spare time to experiment the new library that I wanted to try before: Akita, TailwindCSS, ng-zorro.

There are many Angular examples on the web but most of them are way too simple. I like to think that this codebase contains enough complexity to offer valuable insights to Angular developers of all skill levels while still being relatively easy to understand.

This piece of work is also part of our technical series angular-vietnam/100-days-of-angular which aims at enabling everyone, after 100 days of learning Angular with us, to self-build their application with the similar scale. Our desire is to advocate and grow the Angular developer community in Vietnam.

Tech stack

Tech logos

Features and Roadmap

I set the tentative deadline for motivating myself to finish the work on time. Otherwise, It will take forever to complete :)

Phase 1 - Angular application and simple Nest API

June 13 - 27, 2020

  • Proven, scalable, and easy to understand project structure
  • Simple drag and drop kanban board
  • Add/update issue
  • Search/filtering issues
  • Add comments

Noted: All of your interactions with data such as leave a comment or change the issue detail will not be saved to the persistent database. Currently, the application will serve a fixed structure of data every time you open the app. It means if you reload the browser, all of your changes will be gone.

Phase 2 will bring you a proper API where you can log in and save your work.

While working with this application, I have the opportunity to revisit some of the interesting topics:

  • TailwindCSS configuration - that’s awesome
  • Scrollable layout with Flexbox
  • Deploy Angular application to Netlify

I will take two weeks break to:

Phase 2

July 10 - 25, 2020

  • Refactor the mono repo to use Nx Workspace
  • GraphQL API and store data on the actual database
  • Authentication
  • Websocket realtime update
  • Interactive report


When I look at the application, it is huge. When the task is huge, you usually don’t know where and how to start working with them. I started to break the big task into a [simple to-do list on notion][todo-list]. Once I know what needs to be done, what I need is to follow the plan. That’s my approach.

I learned a lot of stuff. I know you might also have a curiosity about the process of building the same scale app as well. That’s why I am writing a tutorial series on how I built Angular Jira clone from scratch. I hope you guys will learn something from that too :)

I will try to be as detailed as possible. Hopefully through the tutorial, you will get the idea and will start working on your own application soon. Please bear with me.

Its series will also be published in Vietnamese as part of our angular-vietnam/100-days-of-angular.

Part Description Status
-1 Behind the 900 stars repository - Slide Done
00 Prerequisites Done
01 Create a new repository and set up a new Angular application with CLI Done
02 Build the application layout with flex and TailwindCSS Done
03 Setup Akita state management Done
04 Build an editable textbox Done

Time spending

It is a side project that I only spent time outside of the office hours to work on. One day, my team and I were fire fighting on PROD until 11 PM. After taking a shower, I continue with Angular Jira clone for another two hours…

According to waka time report, I have spent about 45 hours working on this project. Which is equivalent to watch the whole Stranger Things series twice.

I really enjoyed working on this project. The interactive kanban board took me sometimes, it is challenging but exciting at the same time.

Jira clone built with Angular 9 and Akita - Time spending

What’s currently missing?

There are missing features from the live demo which should exist in a real product. All of them will be finished on Phase 2:

Proper backend API

I built a very simple NestJS API to send a fixed data structure to the client. All of your interactivity with data will only be saved on the memory. If you refresh the page, it will be gone. Phase 2 will bring the application to live by saving the data into a database.

Proper authentication system 🔐

I am currently sending the same email and a random password to the server without any check to get the current user back. Phase 2 will also bring a proper authentication system.

Accessibility ♿

Not all components have properly defined aria attributes, visual focus indicators, etc.

Setting up development environment 🛠

  • git clone https://github.com/trungvose/jira-clone-angular.git
  • cd jira-clone-angular
  • npm run start:back for the API
  • The API server should run on http://localhost:3000
  • npm run start:front for angular web application
  • The app should run on http://localhost:4200/

Unit/Integration tests 🧪

I skipped writing test for this project. I might do it for the proper backend GraphQL API.


It was being tested on IE 11, Chrome and Firefox. For Safari, there are some minor alignment issues.

Author: Trung Vo ✍️

  • A young and passionate front-end engineer. Working with Angular and TypeScript. Like photography, running, cooking, and reading books.
  • Personal blog: https://trungk18.com/
  • Say hello: trungk18 [et] gmail [dot] com


If you have any ideas, just open an issue and tell me what you think.

If you’d like to contribute, please fork the repository and make changes as you’d like. Pull requests are warmly welcome.


Inspired by oldboyxx/jira_clone and Datlyfe/jira_clone.

I reused part of the HTML and CSS code from these projects.


Feel free to use my code on your project. It would be great if you put a reference to this repository.


Published 27 Jun 2020

Read more

 — A painful Gatsby v1 to v2 migration
 — How to configure TailwindCSS with Angular and why you should use it
 — NPM vs Bower vs Browserify vs Gulp vs Grunt vs Webpack
 — Migrating my blog from Github to Gitlab, and deploy to Netlify
 — What is JavaScript Closure?

Follow @trungvose on Twitter for more!