-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Feature Request: Option for seeing all public boards on All Boards page #252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Up this feature. or else what makes public public other than access rights? |
Please prioritize this. It would be very difficult to use wekan in an organizational setting without such feature. |
Thats what I'm thinking. Actually, it may even be better to implement some sort of GROUP functionality. E.g.: This would eliminate the need to manually add each individual user that should have access to the board. |
Would also like to see this implemented. We are testing Wekan as an organizational program at work and it'd be nice to not have to specify users every time I make a board. |
bump |
A simple mid-level publicity options would be enough for our use case: every registered user should be able to see every public board, but the boards should not be visible to outside users like the current |
I think the way "public" boards are not seen by any existing user (they need to be invited to see the board), is more a bug than a feature, it doesn't "feel" public... We don't need groups at the moment, only "public" (seen/editable by any user) boards and "private" boards, as it is meant to work at the moment :) |
We have a "master" board and just linking to all other boards from that master board - it is super dirty. A page with list of public boards would be so much better. |
UP +1 to this feature. I agree I think the way public boards work at the moment doesn't feel "public" like we are used to. |
Up ? |
Would this be a separate view like "My Boards' or an addition to that view? The js query would be simple enough:
|
On the user's homepage of wekan, I suggest he sees all public boards (with a limit and the usual "expand arrow" .. ), |
There could be buttons at top bar for:
|
Good idea to separate boards into category ! But how do you categorize a board as a subtask board ? As sometimes users define their "master board" as the subtask board aswell. |
Well, maybe it could be like:
There is also related Top Level Boards issue for other way to categorize. Admin Panel could also have options like:
What do you all think? |
I presume you have a lot of boards. What kind of categorization would work best for you? |
What kind of categorization would work best for you? Having Subtask Master / Child boards on separate views would help already I think. |
Currently we have 10895 boards of which 331 are public so it could present us with a bit of a monster but some configuration in the admin panel would be useful for our kind of edge case. I like the idea of showing my boards and starred boards by default and then the user has to pick to see public boards. |
That many boards makes me think of pagination, maybe with selectable amount of boards per page. |
Yea that could work nicely. Either push the starred boards to the top or default to show starred boards only |
I don't think subtask boards should even be displayed on the boards page. There should be a new point "subtasks" (such as templates), and then the subtask boards should also be properly named and not all just called ^originalboardname^. This looked so terribly wrong that I thought it was a database corruption and thereby I just deleted all subtasks of the user by getting rid of these boards. |
Feature added at #3008. |
For someone that is hosting an instance of Wekan as an internal Kanban board, it would be nice for all users to be able to see all public boards.
The way it works now, is that if you want to see the boards of other users, you will need to either send them the public link, or to add each user to the board.
It would be nice to be able to see all public boards directly in the All Boards page when you log in.
The text was updated successfully, but these errors were encountered: