Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RTC Build notifications - team getting emails

Questions
Tags
Users
Badges
Norman Dignard
(356●6●96●177) Aug 14 '19, 9:39 a.m.

 RTC 605 ifix14.  


it appears that all users in one of our RTC projects are getting email notifications on build events which they have no interest in getting.
The build definitions do not have any notifications rules defined/enabled yet all users keep getting notifications. 
There is no option to disable such notifications in the users profile, so why is everyone getting them?

Is this a bug or some reverse logic in that all users get the build notifications unless the notification is defined in the build definition?

0 votes

1 answer
1,684 views
0 votes

One answer

Permanent link
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (63.7k●3●36●48) edited
Aug 14 '19, 9:48 a.m.

 Did you look into the project areas Process Configuration>Configuration Data>Build>Email Notification and verified that there is nothing configured?

0 votes

Comments
Norman Dignard
Aug 14 '19, 10:37 a.m.

Yes i did and its "unconfigured" hence my "reverse logic" question  

Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Aug 15 '19, 2:19 a.m.

I would assume if no build notification is specified in the process and also not on the build definition, no build notifications are sent. 


Is the project areas sharing the process from another project area that defines build notification?

Consider opening an case with support.  

Norman Dignard
Aug 16 '19, 12:46 p.m.

 It looks like this was a one time glitch.

<o:p> </o:p>

The email issue occurred the same time we had a power bump that took down our proxy server where all our Jazz comms pass through.  During this event jazz could not get licenses from our license server. I suspect due to this the email was using some default behavior as opposed to any build notifications (which are not enabled). <o:p> </o:p>

<o:p>   </o:p>

We have not seen a similar occurrence since then. <o:p> </o:p>

<o:p>   </o:p>

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,488

Question asked: Aug 14 '19, 9:39 a.m.

Question was seen: 1,684 times

Last updated: Aug 16 '19, 12:46 p.m.

Confirmation Cancel Confirm