Skip to content
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

Levels of Responsibilities within Block #5511

Open
riesentoaster opened this issue Jul 10, 2024 · 0 comments
Open

Levels of Responsibilities within Block #5511

riesentoaster opened this issue Jul 10, 2024 · 0 comments
Labels
External feedback This Issue is Based on Feedback from the Community

Comments

@riesentoaster
Copy link

When we plan our blocks, we assign one person to be responsible for the block ("boss") and others who contribute/support. There is no way to distinguish between the two at the moment, we're just adding everyone who works on the block as responsible, so they show up in the lists/filters.

However, in more complex blocks, only the "boss" knows about every part, and you'd want to ask this person as an outsider. And when you add everyone as responsible, there is no way to find out who the "boss" is, and thus who to ask. I'd love a way to distinguish between levels of involvement ("boss", "supporter", "has minor role", whatever else) for each person involved in a block. This would then allow each user to generate a list of each block they are involved in, but retain the information about who to ask about each block.

UI-wise this could either be implemented by separate fields that allow adding people similar to the current "responsible" list for different levels, or by assigning levels within the existing fields. This could either come from a predefined or custom list, or maybe even something numeric?

@manuelmeister manuelmeister added the External feedback This Issue is Based on Feedback from the Community label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
External feedback This Issue is Based on Feedback from the Community
Projects
None yet
Development

No branches or pull requests

2 participants