Two issues with SCRUM boards

Well, accidently we spotted following two issues:

1) Boards collecting issues from various Projects - to manage sprints they require from user (Project SCRUM Master/PO/admin) to have admin in all projects, from which issues are listed in sprint - for most case it might be fine, but what if:

- there is board combining various cases and addressing it to one team
- board is managed e.g. by PO which is not project admin due to project itself is run by tech team?

I would say that Sprint managing function should be rather independant from Project Mgmt, or at least configurable.

2) copying board will copy also existing sprints which are from now on shared between boards. Shouldn't it be in the way that sprints are also duplicated, as well as boards?

2 answers

Who reported this as offensive ?

I couldn't agree with you more on the first issue, it is so obvious I can't comment. I think you should open an improvement on GH

Got reminder from Answers to "be a good citizen" and close it... Sorry Atlassian, can't do without any reply from ur side...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


266 views 0 7
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you