Project

General

Profile

Actions

Feature #7730

closed

Allow to override Maintainers' emails by alias

Added by Pavel Kácha 2 months ago. Updated 7 days ago.

Status:
Closed
Priority:
Normal
Category:
Development - Core
Target version:
Start date:
04/11/2024
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

We are increasing the role of the Maintainers (in an attempt to decouple some tasks from Mentat Admin role). However, there can be quite a number of Maintainers, and all of them are now getting the emails about some events happening in Mentat (report filtering rules, for example). It would make sense for those bigger groups to allow (or reuse) mail alias (which might be managed for example by one Maintainer which is on duty in the moment).

Actions #1

Updated by Rajmund Hruška about 1 month ago

  • Status changed from New to In Progress
  • To be discussed changed from No to Yes

Pavel Kácha, currently, if a user is both a manager of a group and a maintainer, and someone changes a filter of that group, the user will only receive one email (the one addressed to maintainers, as it's sent first).

What should happen if the maintainer emails are overridden by the alias and the user's email is the same as the alias? Should they still receive only one email?

In my current implementation of this feature, they would receive 2 emails - one because of the override and the other one because they are the manager of the group. I think it's actually OK not to solve this possible issue, because this situation is unlikely to happen.

Actions #2

Updated by Pavel Kácha about 1 month ago

Rajmund Hruška wrote in #note-1:

In my current implementation of this feature, they would receive 2 emails - one because of the override and the other one because they are the manager of the group. I think it's actually OK not to solve this possible issue, because this situation is unlikely to happen.

Agreed.

Actions #3

Updated by Rajmund Hruška about 1 month ago

  • Status changed from In Progress to Resolved
  • To be discussed changed from Yes to No
Actions #4

Updated by Rajmund Hruška 25 days ago

  • Status changed from Resolved to In Review
Actions #5

Updated by Rajmund Hruška 7 days ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF