You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
As a developer or project owner
I want to be able to share a board with the client
To improve communication with them
And keep them in the loop with project progress
Some vague ideas:
Check permissions on GitHub and only show tickets from repos that user can access
Problems
Permission checking would slow down the app (especially with boards with lots of repos)
Reordering tickets becomes tricky - if I can't see all the tickets in a swimlane, where
should we place a ticket when I move it with regards to those hidden tickets?
Show all tickets, but ones from inaccessible repos appear as a generic "ticket from a repo you can't see"
Have 'nested' boards, which share the same swimlanes, but only include a subset of repos
Give clients access to the subset that concerns them, but retain the ability to see the 'big picture' for
the product owner when planning.
Have a filtering UI so that users can show/hide tickets from certain repos
A readonly mode for clients, or limit their ability to move tickets to certain swimlanes
The text was updated successfully, but these errors were encountered:
Access control/'client mode'
Some vague ideas:
Check permissions on GitHub and only show tickets from repos that user can access
Problems
should we place a ticket when I move it with regards to those hidden tickets?
Have 'nested' boards, which share the same swimlanes, but only include a subset of repos
Give clients access to the subset that concerns them, but retain the ability to see the 'big picture' for
the product owner when planning.
Have a filtering UI so that users can show/hide tickets from certain repos
A readonly mode for clients, or limit their ability to move tickets to certain swimlanes
The text was updated successfully, but these errors were encountered: