Enable Support form to Communicate with RT APIs, investigate external tool for Support Form
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
The support form at dataverse.harvard.edu currently relays messages in a way that is running afoul of spam filters by using the user’s email as the return address and with mismatched domain headers. We can expect that other installations may run into this as well. We should investigate a configuration that allows the support form to communicate with support ticketing systems via API or some other method instead of generating an email with mismatched headers. For this first iteration I’m interested in setting up something with RT:
https://bestpractical.com/request-tracker
https://rt-wiki.bestpractical.com/wiki/REST#Java
https://docs.opennms.org/opennms/releases/27.1.0/javadoc/org/opennms/netmgt/rt/RequestTracker.html
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the support form behavior described in the issue and review the linked Request Tracker REST and Java references. Define an API-based configuration that avoids mismatched email headers and verify how it would work across installations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100