Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add reminder about Jira notification email address #3204

Open
daniel-beck opened this issue Oct 25, 2022 · 2 comments
Open

Add reminder about Jira notification email address #3204

daniel-beck opened this issue Oct 25, 2022 · 2 comments
Labels

Comments

@daniel-beck
Copy link

Service(s)

Accounts

Summary

It's not uncommon for maintainers to use a different (usually outdated/obsolete) email address on Jira compared to the account app. This creates friction when trying to inform maintainers about vulnerabilities.

I don't remember whether it was a deliberate choice to not override the Jira notification email address with the one from the account app, but it might be. I know I deliberately did that for a while.

Unless we want to (and can) change this behavior, an easy first step would be to add a reminder to the account app that the Jira notification email address needs to be changed separately.

Reproduction steps

No response

@daniel-beck daniel-beck added the triage Incoming issues that need review label Oct 25, 2022
@timja
Copy link
Member

timja commented Oct 25, 2022

I think it would be better to just update from ldap on login?

Would need to modify this:
image

@daniel-beck
Copy link
Author

I think it would be better to just update from ldap on login?

Right, I explicitly mention that as a possibility. The problem with that is that it could override good Jira values with bad account app values. We should make sure that's not the case first. For example, around 70 LDAP accounts have @java.net email addresses. If they have a better email address in Jira, we'd break that.

@dduportal dduportal removed the triage Incoming issues that need review label Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants