Assign topics to non-staff users

(Daniel Hollas) #1

Is it possible to add the possibility of assigning topics to users of other groups than staff?

I would be very much interested in this as well.

In a recent Discourse blog post, there is an allusion to such functionality

We use a category on our internal instance of Discourse to manage tasks. New tasks are written up in the todo category. In some cases they are immediately assigned and in others, we tag a group to give visibility of the task so that a team member can claim it using Discourse Assign.

It does not make sense to me that everybody in their internal Discourse instance is a Staff member…

Discourse Assign
(Sam Saffron) #2

All our staff on our internal instance are staff barring a few part time people, we may expand the functionality cause we already have assign-public so adding this is not a huge change #pr-welcome for the time being just let me know what you want to call the site setting.

(Boubacar Sidy Diallo) #3

I have installed the assign plugin 0.1, but it is only accessibles for administrators or moderators. How can I make all users assign their question to anyone ? and see the topic assigned to them

Discourse Assign
(Jeff Atwood) #4

Not possible at this time.

(Sam Saffron) #5

@danekhollas I am actually very mixed on this:

Take for example the following implementation:

  • New site setting assign_allowed_on_all_users (will have to be a client setting) default off

  • Client and server site tests that confirm the behavior.

  • Staff still is the only type of user that can either assign or unassign.

This restriction that only staff can assign is very likely to break workflows, and then we end up needing even more settings for the wormcan:

assign_groups_allowed_to_assign , assign_assigned_user_can_always_unassign and so on.

Plus non staff don’t get whispers so then even more goes into this can.

I am tempted to just reject this as something that would just increase the scope of the plugin too much.

(Daniel Hollas) #6

Got it. What if instead of assign_allow_on_all_users you’d have something like assign_allowed_on_groups where you would explicitly list the user groups? I think in that case you could leave the can of worms closed and just let everybody assign/unassign by default?

To better explain my use case: I run a small non-profit and we use Discourse mainly for internal communication. We have a small stable core team and then lots of volunteers coming in and helping us, possibly for a limited time. It doesn’t make sense for us to make them all staff users, but it would still be nice if we could use this plugin (I am not exactly eager to introduce yet another tool like Trello into our workflow). :slight_smile:

That being said, I completely get your concerns here. :slight_smile:

(Sam Saffron) #7

I am kind of OK with a setting for assign_allowed_on_groups that defaults to staff and provides full access to all assign features for the groups selected. I guess from a security perspective this would be nice but I think it is a reasonably big change.