K
KimmoR
We have encountered a problem with Project Server 2003.
Project managers receive announcements of resources reporting hours to
already closed projects' tasks, even though they have not.
Project resource assignments have set to proposed, which should be enough to
disable time booking and notifications.
sql script:
select P.PROJ_NAME, A.TASK_NAME, A.ASSN_START_DATE, A.ASSN_FINISH_DATE
from MSP_WEB_ASSIGNMENTS A, MSP_WEB_PROJECTS P
where WASSN_ID in (select A.WASSN_ID from MSP_WEB_ASSIGNMENTS A
where A.WRES_ID = (select R.WRES_ID from MSP_WEB_RESOURCES R
where R.RES_NAME = '<resource name here>')
and A.WPROJ_ID=P.WPROJ_ID
and P.WPROJ_IS_NONWORKING=0
and A.ASSN_BOOKING_TYPE=0
and A.WASSN_REMOVED_BY_RESOURCE = 0)
order by ASSN_START_DATE
shows that the resource is still assigned to the project (as he should be,
what I know).
Project manager's notification subscription is also on:
select n.wntfy_is_enabled from msp_web_notifications n, msp_web_resources p
where p.wres_id = n.wntfy_owner_id
and n.wntfy_event_id = 1009
and p.res_name = '<project manager name here>'
Which naturally is ok, he must receive notifications of "current" projects.
Next I would like to inspect the procedure which triggers the notification
email for projects, to see if there is something which could explain this
behaviour.
Please tell me what procedure to look into?
Or could there be something else to look for?
--Kimmo
Project managers receive announcements of resources reporting hours to
already closed projects' tasks, even though they have not.
Project resource assignments have set to proposed, which should be enough to
disable time booking and notifications.
sql script:
select P.PROJ_NAME, A.TASK_NAME, A.ASSN_START_DATE, A.ASSN_FINISH_DATE
from MSP_WEB_ASSIGNMENTS A, MSP_WEB_PROJECTS P
where WASSN_ID in (select A.WASSN_ID from MSP_WEB_ASSIGNMENTS A
where A.WRES_ID = (select R.WRES_ID from MSP_WEB_RESOURCES R
where R.RES_NAME = '<resource name here>')
and A.WPROJ_ID=P.WPROJ_ID
and P.WPROJ_IS_NONWORKING=0
and A.ASSN_BOOKING_TYPE=0
and A.WASSN_REMOVED_BY_RESOURCE = 0)
order by ASSN_START_DATE
shows that the resource is still assigned to the project (as he should be,
what I know).
Project manager's notification subscription is also on:
select n.wntfy_is_enabled from msp_web_notifications n, msp_web_resources p
where p.wres_id = n.wntfy_owner_id
and n.wntfy_event_id = 1009
and p.res_name = '<project manager name here>'
Which naturally is ok, he must receive notifications of "current" projects.
Next I would like to inspect the procedure which triggers the notification
email for projects, to see if there is something which could explain this
behaviour.
Please tell me what procedure to look into?
Or could there be something else to look for?
--Kimmo