Hi Guilherme, > Another thing I've just noticed we'll have to keep in mind is that in > these per-project lists, users won't be able to do mass-state-changes > unless they're the maintainers of the project in question. We could > change generic_list() to behave differently and always include the > state-changing form, but this seems to me like yet another indication > that generic_list() may not be the appropriate thing to use here.
That would indicate to me that we should update generic_list to handle these cases properly. What we could do: if there are editable patches in the list, then include the checkbox-per-patch column (with checkboxed disabled for non-editable patches), and include the state-changing form. Otherwise, just leave it as a read-only view. Cheers, Jeremy _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
