DEV Community

A simplified Jira clone built with Angular 9, ng-zorro and Akita

Trung Vo on September 25, 2020

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 onl...

Read full post

Greg Dostatni • Feb 14 '21

Thanks for creating this, very helpful. I have a suggestion for readers who want to learn from this repository.
Fork it, configure compodoc and document everything. You'll learn and understand everything and you will have a reference to use in the future. The best way I've found yet to learn from code.

For Trung: Thank you for creating this. Going through this exercise has slotted some pieces of knowledge I got from various tutorials into a cohesive whole. At least it makes sense now, we will see if the knowledge survives attempts at implementation.

Cheers,

Trung Vo • Feb 16 '21

Thanks Greg for your kind words. It means a lot to me :) Let me add compodoc into the repository so that others can use it directly after forking the repo.

Let me know if you have any other suggestions/questions. I am happy to help 🙂

Trung Vo • Feb 16 '21

Hey Greg, I added a command to run compodoc on the master branch 😁

You can sync with the upstream and run

npm run docs:html

github.com/trungk18/jira-clone-ang...

Peter Kiss • Sep 26 '20

Hey, I like the look very much!
Especially that this is the topic of one of my side projects as well 😂.
Except I've focused more on basic functionality and what can be achieved with the API. Beside some prototyping and learning on various topics.
For example css grid as a board display, parsing JQL expressions.
I used angular and ngPrime.

Trung Vo • Sep 26 '20

Sounds great. Did you have publish it anywhere? I would like to see it. For a project like Jira clone, we can actually try and test a lot of technology and see how all of them are working nicely at the end. Looking for more projects from you! 😊

Peter Kiss • Sep 28 '20

Hey, thanks. It is on bitbucket, but far from complete or mature enough for a real publication :)

bitbucket.org/kisp/jira-light/

Exploring the jira API lead to some dead-ends. I found that boards are provided on the agile endpoint, only after I have implemented a board view through a JQL query execution.

Before you do anything involving "agile" - you need to be sure about some basics about the api.

The cloud-api and the agile-api are two different endpoints working over the same data with some extra entities
There are customFields defined on the ticket, which can be accessed via ids - ('Story points' is one of them) Some custom fields has a default name, 'Story points' is one of them. The id can be found by name. SP exists on scrum boards only obviously. Boards and epics can be accessed through the agile api with project key. end-so-on.

In overall I was a little-bit struggling to find the entry-point for having a good grasp to get my tickets displayed.

Trung Vo • Sep 28 '20

Seems like you did the extensive research on how the actual Jira work. I only focus on the front end of thing 😁But anyway I am preparing an API with GraphQL with some basic functionality. If you would like to take a look, this is a branch name: github.com/trungk18/jira-clone-ang...

Basically it is the flow:

User login, you get some basic user information.
There should be an list of projects associate with an user, so probably you will need to fetch the list of project. Then open the last opened project (My API is not working exactly like that)
Fetch the project detail and show the board. A project will have a list of
Lanes: mapped to the status: Backlog, Selected, Inprogress, Done
Each lane will have a list of issues
Have several API to update issue.

I hope that I can deployed the 2.0 version with API very soon. I didn't think about the custom fields that you are mentioning but I am aware of that on the actual use of Jira.

Anyway, good luck with that jira-light!