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

Fixes to notification email about joining organization #140

Closed
wants to merge 1 commit into from

Conversation

rdn32
Copy link
Collaborator

@rdn32 rdn32 commented Jun 25, 2013

There was a suggestion in the card, which I haven't implemented, to have a special help email address for an econsensus installation. (I'm not quite sure what status the suggestion had.)

username (rather than their first and last name, which may not
be set) in notification email. Also remove sentence that didn't
make any sense in that context. (Fix for
http://aptivate.kanbantool.com/boards/5986-econsensus#tasks-1257223)
@samastur
Copy link
Contributor

samastur commented Sep 2, 2013

There are few things missing. It is missing sender's email address so it is not possible to contact that person.

It would also be better to fallback to username when first name and last name are not available since username alone on service I am not yet using likely doesn't tell me much.

Not sure about help email address. We certainly shouldn't add it before it exists and it should be configurable.

@samastur samastur closed this Sep 2, 2013
@rdn32
Copy link
Collaborator Author

rdn32 commented Sep 6, 2013

This isn't a message for a service that the user is not yet using. It's the message someone gets if they already are using econsensus, and have merely been added to another org. I'm not sure about giving the sender's email address, since (as far as I'm aware) email addresses are normally only visible to org administrators.

@samastur
Copy link
Contributor

samastur commented Sep 8, 2013

It doesn't really change the problem since it's not anonymity of eConsensus that would be the problem.

I understand the reservation about email, but don't really have a strong view one way or the other (could argue for both). However if we drop this requirement, then that should be reflected on story card.

@rdn32
Copy link
Collaborator Author

rdn32 commented Sep 9, 2013

I've hit a weird thing. I implemented falling back on username, and for consistency I wanted to do this in invitation and reminder emails. However, in testing this locally I've found that invitations aren't being sent out (although reminders are). I need to dig into this, to find out what's going on.

Update: this problem exists in the develop branch, so rather than try to address it here I've created a new card (https://aptivate.kanbantool.com/boards/5986-econsensus#tasks-2155377)

@rdn32
Copy link
Collaborator Author

rdn32 commented Sep 9, 2013

I've moved the suggestion about having a "help" email address to its own card (https://aptivate.kanbantool.com/boards/5986-econsensus#tasks-2155433)

@rdn32
Copy link
Collaborator Author

rdn32 commented Sep 9, 2013

I've opened pull request #176 as I couldn't figure out how to add further commits to this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants