Thank you, that's very clear (and I can see it now that I understand it). :)
On Fri, Apr 15, 2016 at 11:04 AM, Mukunda Modell <[email protected]> wrote: > > > On Fri, Apr 15, 2016 at 12:41 PM, Max Binder <[email protected]> > wrote: > >> You can require certain projects for all task creations going through >>> your creation form, but then the user can't add any extra projects >>> themselves (AFAIK). >> >> >> Do you happen to know if Alex is correct about this? >> >> > Almost correct but not exactly, it's nuanced. You can't absolutely force > certain project tags while also allowing users to add their own but you can > suggest some default projects and let the user make adjustments as needed. > > More specifically, you can do either of the following: > > 1. Pre-fill and lock the projects field, in which case the user cannot > add or remove any project tags. You could also hide the projects field, in > which case the behavior is the same but the user won't even see the > projects that are being selected for them. > 2. Pre-fill the projects with a default (can be one project or > several) but leave it unlocked. In this case the user can add projects to > the list but they are also free to remove the default choices and replace > them with whatever projects the user wants. > > > > > _______________________________________________ > teampractices mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/teampractices > >
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
