Hi,
Currently Risk and Issue are not mapped to Project status field - On track status. If the Risk and Issue are high (red), the Project status (On track status) should change to Red automatically. This is not happening.
Also, if the project is running behind schedule (Project completion % is very less), the Project status (On track status) should change to Red.
Can anyone suggest, if these two parameters can be linked to Project status (On track status).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very valid points. However, the RAG status (red-amber-green) is a very "policial" field in many organizations, and it's not at all clear what a "red risk area" means. Projects may have a separate "risk budget", so that a 30% risk value ($ risk / $ project) may be perfectly "green".
In order to define such rules you can use the relatively new "intranet-rule-engine" package. It's part of ]po[ V5.0.
Cheers,
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Currently Risk and Issue are not mapped to Project status field - On track status. If the Risk and Issue are high (red), the Project status (On track status) should change to Red automatically. This is not happening.
Also, if the project is running behind schedule (Project completion % is very less), the Project status (On track status) should change to Red.
Can anyone suggest, if these two parameters can be linked to Project status (On track status).
Hi Debarata,
Very valid points. However, the RAG status (red-amber-green) is a very "policial" field in many organizations, and it's not at all clear what a "red risk area" means. Projects may have a separate "risk budget", so that a 30% risk value ($ risk / $ project) may be perfectly "green".
In order to define such rules you can use the relatively new "intranet-rule-engine" package. It's part of ]po[ V5.0.
Cheers,
Frank