It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Agile: Anyone can create a Scrum board -- why????

I newly installed Jira Agile plugin 6.3.4 on top of my 5.2.11 standalone Jira server.

My current Jira setup is tightly controlled using a custom workflow with scriptrunner groovy scripts for transition conditions and validators. Only a limited group of users (managers and scrum masters) have full editting access to issues (i.e. permission scheme customized to limit direct editing and scheduling of issues in general). There are two main Jira projects: Features and Bugs which I want to include in the overall agile backlog. Then I find out that anyone can select the "Getting Started" menu under the Agile tab and select the "create scrum board". Why??

I need to limit this access.

3 answers

1 accepted

0 votes
Answer accepted

A Scrumboard only provides a view on a list of Issues (using an Issue Filter). The idea is that everyone should be able to create his/her own view on the progress.

If I want to add my own Quick Filters or I'd rather have a different view while working in a sprint (other swimlanes, different details) or even when I'm working in more than 1 scrum team.

At my work we for example have a scrumboard we use for our daily standups (with all projects we're currently working on) but we also have a scrumboard per project so the Product Owners and Project Leaders of those projects can follow up without having to worry about the other projects.

The fact that every user is allowed to create a scrumboard isn't necessarly an issue in my opinion.


Just to add to Maarten's answer:

Why not? As long as your JIRA permissions and Workflow permissions are correctly set, having a board to view the issues does not impact anything. No users will be able to make any changes to the issues and all the rules that you have set using conditions/validators are respected.


At a minimum, it's confusing for users that do not need Agile let alone know what it is. We have a variety of projects on our system and not all of them are development or operations related. Users of these projects will be confused with the Agile views, and they are going to cost me a lot of time explaining to them that they should ignore it. You took a big step backwards in usability by removing the per-project control of this plugin.

I found a solution to this problem.  It's posted at

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Early Access: If you use Jenkins and Jira Software Cloud, you need to read this!

The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...

2,347 views 3 19
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you