SSWConsulting / SSWConsulting/SSW.People

📧 CRM and SSW.People - Improve automated email when an update is done

Open
#652 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13
Forks
9
PR merge metrics
No merged PRs in 30d

Description

cc @jaydenalchin @adamcogan

Hi team,

Everytime we update CRM and consequently our SSW profiles, we get an automated email, which is cool!

  1. Less is more 🙌 - Can we improve the email from

Hi Tiago,

Thanks for your updates to SSW People | Tiago. These changes will be live after about 30 mins.

This happened because you made a change to CRM | User | Tiago. More information about this rolling build can be found here
https://raw.githubusercontent.com/SSWConsulting/SSW.People.Profiles/main/.github/instructions/images/rolling_build.png

-- Powered By CRM.SSWPeople
https://github.com/SSWConsulting/SSW.People (an open source project by www.ssw.com.au )

to

Hi Tiago,

Thanks for the update to SSW People | Tiago by editing CRM | User | Tiago.

Your changes will be live in about 30 minutes.
See more information about the automated build.

-- Powered by CRM / SSW.People - An open source project by ssw.com.au

Contributor guide

No contributing guide indexed for this repository

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

No source file, test, or entry point is named. Start by locating the automated email template or sender in the SSW.People project, then compare it with the proposed wording and linked rolling-build information. Done means the email uses the shorter text, preserves the SSW People and CRM links, and clearly points to the automated-build details.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
content
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.