Skip to content
This repository has been archived by the owner on May 9, 2019. It is now read-only.

Customizing notification subjects #8

Open
dubeaud opened this issue Dec 6, 2014 · 1 comment
Open

Customizing notification subjects #8

dubeaud opened this issue Dec 6, 2014 · 1 comment
Labels

Comments

@dubeaud
Copy link
Owner

dubeaud commented Dec 6, 2014

This issue was imported from CodePlex

dubeaud wrote 2013-08-26 at 10:59
It would be really amazing to be able to customise the subjects for the emails that are sent out from bugnet.

In project administration under notifications there could be a field called Notification Subject. This will be a text entry which will accepts data such as:

  • Issue [IssueNumber] : [OldStatus] -> [NewStatus]
  • [Date] [IssueNumber] for [CustomField1] has been updated by [EditedBy]: [NewStatus]

Etc etc.

This would allow any fields and custom fields to be defined by the clients per project. This would help in certain situations. For example if I am in a meeting and get an email for someone making a change on bugnet, the current email subject ("Issue x
has been updated by y") may not tell me enough information on a quick glance at my phone as to what actually happened.

@aliciam
Copy link
Contributor

aliciam commented Jan 8, 2015

I've just implemented something along these lines, although the bugnet administrator must set these up directly in the resource file at present.

Currently Notification Subjects are stored in Notifications.resx and there is only a single subject key for an updated issue notification (IssueUpdatedSubject). If you want to specify something like NewStatus you'd have to know that it was the Status that was changed and sent that value to

I've kept the single IssueUpdatedSubject (for now) and created a set of priority fieldnames to use to select the IssueHistory that is most salient to the user. Then a generic FieldName, OldValue and NewValue can be used in the subject.

e.g. IssueUpdatedSubject = Issue {IssueId} "{IssueTitle}" {FieldName} changed to "{NewValue}"
where several fields have been changed, including the status, would result in the subject line (given the appropriate data):

Issue BN-42 "Meaning of Life" Status changed to "Solved"

See my commit of those changes

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

No branches or pull requests

2 participants