Pri     Meaning
---     -------
100     Critical to operations
120     Critical to a minor release
125     Critical to the next Cycle's major release
150     Action Item - Critical

200     Important to operations
220     Important to a minor release
222     Integrated Schedule work
225     Important to the next Cycle's major release
250     Action Item - Important

300     Other problems affecting operations
320     Other problems affecting a minor release
325     Other problems that should be done for a Cycle's major release
350     Action Items - Other
399     Issues that have no operational/RPS2/APT impact


OPR Priority Explanation: 

 - 100-150  Critical OPRs.      Must Have.  Won't release unless they are done.
 - 200-250  Important OPRs.     Users would really like these,
                                but won't stop a release.
 - 222      Integrated Schedule OPRs, tracked separately.
 - 300-350  Would Be Nice OPRs. Done if time permits
 - The OPR priorities are a plan (not an absolute) to guide upcoming development. 
   Things can be re-prioritized as needed.  So we don't need to spend too much time
   trying to fit an OPR into a particular category, because we are allowed to change
   our minds later.

Link to PR System.