IQSS / IQSS/dataverse

Feature Request: Confirmation e-mail for contact/support requests

Open
#11,088 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Overview of the Feature Request
Send additionally some confirmation mail to the users who contacted dataverse owners ("contact" button on the dataverse level) or repository admins ("support" button on top) to inform them, that their message was successfully sent and reply will come soon.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
All GUI users.

What inspired the request?
When users do not get any confirmation email and admins/owners do not answer in 1-2 days, users can start to think, that their message was not sent properly and they start to write additional mails to admins/owners directly, not via Dataverse.

What existing behavior do you want changed?
Currently (in my case v6.2) users can see only a graphical message, that their message was sent. It is good, but not fully enough.
grafik

Any brand new behavior do you want to add to Dataverse?
Additional confirmation mail to the user including the text of the message itself. It will help for the further communication, the user will have the original message then. The basic confirmation text can be similar to this one.

Any open or closed issues related to this feature request?

Are you thinking about creating a pull request for this feature?
no

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 by tracing the contact and support request flows described in the issue, then review related issues 9701 and 8719 for existing expectations. Define confirmation behavior for both flows, including the original message, and verify that users receive the email after a successful submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.