How can I easily tell what kind of Software project is a project in Jira, Kanban vs Scrum vs Basic?

[Abe_Roba]

How can I easily tell what kind of Software project is a project in Jira, Kanban vs Scrum vs Basic? I can tell whether it is a Software or Business or Service Desk, but I can't tell what type of Software project it is.

[Kian Stack Mumo Systems]

Hello Abe,

The "Type" that you are in only affects the original workflows, issue types, ect. It doesn't limit you in any way going forward. It's just a project template.

That being said, if you want to check if you had a "Scrum project" initially vs. a Kanban, you can look at the "Issue Type Scheme" that was given to the project. 

Kanban ones will be marked with "Project Key: Kanban Issue Type Scheme", Scrum ones will be "Project Key: Scrum Issue Type Scheme". "Basic" ones will be marked as "Software Development Issue Type Scheme". 

See my screenshots. 

[subham patra]

Hi @Kian Stack Mumo Systems - Is there any other way to find out the types of project i.e. scrum or kanban? 

The scheme names have been changed for the projects i have been looking for to identify the types.

[Benjamin Kirkbride]

> The "Type" that you are in only affects the original workflows, issue types, ect. It doesn't limit you in any way going forward. It's just a project template.

This may have been true at one time (oh what a time that must have been) but it could not be further from the truth now.

[Ratom]

In Dec 2025 I was taught  who to find types:

Scrum =  always has  Active Sprint section on the left pane

else

Kanban.

However next day instructor told us that you can also bring Agile Dashboard into Kanban project, and after this you also get Active Spring on the pane. So looks like nothing works.

[Hoffman, Chris]

@Kian Stack Mumo Systems   This solution does not work as of May 2023.  It also looks like there are limitations on what can be changed in a project based on how it was originally created

[Dick]

This is especially true when using Plans. For some reason storypoints can only be visualised in a Plan when the issues displayed originate from scrum projects. Any Kanban project issues screw this up (as in: the option to use storypoints in the Plan configuration is greyed out). 

Hence, it is important to know the original type of project: scrum or Kanban. 

[jeroen_wilmes]

You can see whether it is a scrum or a kanban by the fact that only "scrum" projects have a backlog. So if you have a backlog option in your left bar it is scrum, if you don't it is kanban