Redmine

Rob D wrote:

Members that do not have permission to submit an issue still appear in the authors list. Members belonging to a role which cannot be assinged issues still appear on the Assignee list.

Which doesn't mean they didn't have said permissions in the past.

Felix Schäfer wrote:

Which doesn't mean they didn't have said permissions in the past.

Okay, agreed, then it may become a bit more complicated.

One option is: disregard past permissions, and show the list based on the permissions of the current roles.

Another option is: if a member's current role does not have the permissions to add an issue, and their total reported issues is 0 (ie. they did not add an issue in the past), then they should not appear in the Authors list. However, if they have reported an issue in the past, then it should be in the list. Likewise with the Assignee list.

Consider a private project with many members in a 'Stakeholder' type role, who's only permission is to view issues. They should not be listed in the summary, cluttering up the list. They do not want to see their name in the list, and panic when they think something may get assigned to them. They themselves as stakeholders only want to see the current summary of current developers.

Also, Developers/Contributors/Reporters etc. should still be listed even if they have not yet reported or been assigned an issue, provided their role allows them to add or assign issues.

In my opinion, it would be uncommon for members to change roles in a project. If it did occur, then there would be a good reason to do so, and that reason would probably apply to them being removed from the list of assignee's or authors.