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.
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!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
In overall I was a little-bit struggling to find the entry-point for having a good grasp to get my tickets displayed.
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:
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!