For project creation using REST API, we pass "projectTemplateKey" which is setup scrum, kanban or basic.
Similary, if the project is already created using JIRA UI, what is the REST API I should use to get the ProjectTemplateKey.
In the project json there is only projectTypeKey whcih says "software".
You don't - the scrum/kanban is only really part of the creation process. It determines what board to create by default and the fields, workflows etc, but once created, the project is, well, a project. You can create more boards that refer to it, of either scrum or kanban, and change the workflows, fields etc to make it work totally differently.
Nope. That tells you about the board, not the project. Boards do not belong to projects, and you can point many points to a project. If I create a Scrum project, I get a scrum board at the same time, but I can point a Kanban board at it if I want as well.
I am a bit confused then, this endpoint shows each board's location (in a project) and it is not an array - it is a single value. So I assumed that each board belongs to a single project.
Then you can get all boards belonging to a project here. And if all are of the same type you can safely assume this is the type of the project. If not, treat it as a mixed type project. Am I wrong?
A board can include issues from many projects. You need to stop thinking of a board as being "in a project", as that's not true. It can look like it, and the UI misleads us into thinking it in places, but a board can pull in many projects, and a project can be included in many boards.
>And if all are of the same type you can safely assume this is the type of the project
No. I could create a Scrum project, create a couple of Kanban boards that include it, and delete the original scrum board. The project would still be a scrum project, just one that has no scrum boards and several kanban boards looking at it.
This forum platform is still lacking many of the functions Confluence Questions has, and moving/removing stuff is one of the these.
The way you are using your system now means that what you're doing is a perfectly good approach, and it will work fine for you. My discussion was not to try to tell you to change (I'd rarely encourage change if the current thing is working!), just for the benefit of readers to understand how it works, so they can make it work for them.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG