IQSS / IQSS/dataverse

Account creation confirmation email should include support email, not system email

Open Beginner friendly
#11,626 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Notifications Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

The template is given the output from getSystemAddress instead of getSupportAddress on the two lines starting at the link below:

https://github.com/IQSS/dataverse/blob/7e16ed3523c7cbad76a0d162d7da865f3076d3f1/src/main/java/edu/harvard/iq/dataverse/MailServiceBean.java#L597

            case CREATEACC:
                String accountCreatedMessage = BundleUtil.getStringFromBundle("notification.email.welcome", Arrays.asList(
                        BrandingUtil.getInstallationBrandName(),
                        systemConfig.getGuidesBaseUrl(),
                        systemConfig.getGuidesVersion(),
                        BrandingUtil.getSupportTeamName(getSystemAddress().orElse(null)),
                        BrandingUtil.getSupportTeamEmailAddress(getSystemAddress().orElse(null))

It seems like functions called getSupportTeam* should take the output of getSupportAddress() not getSystemAddress().

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/main/java/edu/harvard/iq/dataverse/MailServiceBean.java at the CREATEACC case and the two lines around L597. Review how the welcome email arguments are assembled, then verify that the support-team fields use the support address and that the account-creation confirmation shows the support email.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.