dependency-track icon indicating copy to clipboard operation
dependency-track copied to clipboard

Limit notifications to portfolio(s) instead of/alongside projects

Open malice00 opened this issue 1 year ago • 2 comments

Current Behavior

Currently notifications can only be limited to projects. This means that any new project has to be added in the notification manually (unless no limits are set of course). Since this can only be done by a user with administrative permissions, this is a rather involved process and takes more time than it really should.

Proposed Behavior

It would be good to be able to limit notifications to a portfolio, so that any new projects in the portfolio are automatically picked up. Seeing that (at least for the mail notification) it is already possible to send it to a specific team, maybe there it could even be the default -- seeing how a team should only see their own portfolio.

Checklist

malice00 avatar Jul 12 '24 16:07 malice00

@malice00 , PR #3506 (scheduled for inclusion in v4.12.0 release) adds functionality whereby notifications can be filtered by tag.

I believe that this will address your need. Do you agree?

msymons avatar Jul 15 '24 18:07 msymons

@msymons, it might be usable as a workaround, but it does mean that we have to go through all our current projects to set tags on them... Also, what happens when 2 teams use the same tag on their projects? I feel portfolios are the more 'secure' way to make sure our teams only get notifications on their own projects...

malice00 avatar Jul 15 '24 19:07 malice00