I have a tricky question about how to set up Rapid Boards.
Our context is that we're a software development company working with a number of clients. Each of our Scrum teams has several clients that they work with. The Scrum team's backlog therefore includes tickets from a number of projects, each of which relates to a single client.
Setting up a Rapid Board to represent this is fairly straightforward. However, we also want to have a single-client view where that client can log on and only see their tickets. How do we do this?
* Do we give them a separate Rapid Board? If that's the case, how to we keep the cards selected for the Sprint in-sync?
* Or is it possible to give the client access to the Scrum team's multi-project Rapid Board, and somehow hide the cards from other clients? If so, how do we configure this?
Historically, we have used the Classic Greenhopper planning view, filling out common values for Fix Version across projects, and then configuring the Rapid Board to use Fix Versions for swimlanes. It was a bit clumsy, but it was workable. However, I can see that you're deprecating the Classic views, and so I want to migrate away from them if we can.
For the benefit of the wider community I thought I would share the links regarding the managing of projects in JIRA OnDemand for external users : https://confluence.atlassian.com/display/AOD/Managing+project+visibility
Through applying the external and internal user permissions to a project this will flow through to any board that is created that incorporates those projects.
Hey there, Sam.
The new Rapid Board has the functionality of Quick Filter that allows you to only show selected issues based on the JQL:
Does it cater to your requirement or are you looking at something which is much more specific?
Hrm, it seems as though you *can* set up a Rapid Board and grant access to it to people who don't have access to all the tickets on it. In that case, the client only sees a sub-set of the tickets, as expected.
So it seems I can answer my own question. Will this work?
* Create projects Client1, Client2, Client3
* Create a rapid board, ScrumTeam, including all the tickets from Client1, Client2, Client3
* Give my scrum team access to all three projects
* Give each of my clients access to only their project
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Happy Friday, Funmakers! We had a Community Team offsite in Austin this week, and my mind feels primed for thinkin' from all the brainstorming we did! So, this week's Friday Fun thread w...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs