nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using REST API, how do I know if the project is Scrum or Kanban or Basic

Ravi21

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

Accepted answers

All comments

Nic Brough -Adaptavist-

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.

Gerardo Saborio

Hello Nic

To know, My project is SCRUM or Agile, Have you created any new API?
Answer of your post is of 2016. After that, if you have created any new API then please provide me its URL.

Nic Brough -Adaptavist-

It's the same answer - projects are not "scrum" or "kanban", those words are just to select a board type to create alongside a Software project. It's not stored, so there can't be a REST API for it.

Gerardo Saborio

Hi Nic,

Thanks for quick reply.

But if I want to know whether this project is in Agile or Scrum, then how will it?

Raimundas Juska

Thank you for explanation. Anyway, in my case board type was what I really need, so this endpoint fits me perfectly.

Raimundas Juska

Mistakenly posted this here as a reply to Nic's reply below my comment. Seems no way to remove it now.

Nic Brough -Adaptavist-

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud