| Key: |
CIB-1098
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
3
|
| Assignee: |
jason
|
| Reporter: |
Scott Marshall
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
I love the email committer feature that was added recently. Unfortunately, not all of my P4 userids match valid email addresses for each user. It would be great if there was a way I can map a perforce userid to a valid email address so that when a developer submits a change to P4, pulse wakes up and runs the build, and then sends email to each committer. This is in lieu of each user having a Pulse userid. I believe this was talked about on the support forum and I just wanted to throw it out there again as something I would love to see in the product.
-Scott
|
|
Description
|
I love the email committer feature that was added recently. Unfortunately, not all of my P4 userids match valid email addresses for each user. It would be great if there was a way I can map a perforce userid to a valid email address so that when a developer submits a change to P4, pulse wakes up and runs the build, and then sends email to each committer. This is in lieu of each user having a Pulse userid. I believe this was talked about on the support forum and I just wanted to throw it out there again as something I would love to see in the product.
-Scott |
Show » |
|
provide mechanism to map Perforce Userid so that email notification can be sent
Thanks for raising this as a proper issue for us. I have a feeling this will be solved more elegantly after we have the new configuration/templating system we are building into Pulse 2.0.