Allow an alias to be associated with Baseline, Baseline 1, Baseline 2 etc
Being able to associate and alias (or renaming) Baseline fields would provide highly effective ways to present and view current project data and baseline data in a more meaningful way. If set at the server level (using Project Online or Project Server) it provides organisational consistency in how baselines can be used. The aliases should be visible in usage views and in PWA views. Typical scenarios are when the baseline should be set at the end of each key stage gate milestone or at the end of specific process stages.
planner 1 commented
+1 for this, also to note the date the baseline was taken. Even better if we could have custom fields attached to the baseline, that way we could define what we want (e.g. baseline name, baseline type, baseline date..)
Also, more locked baselines please. I would like to store baselines taken at each stage gate (x6) and also at any approved change request
Erik van Hurck commented
I wrote a blogpost about this UserVoice item. This would be a great addition to the product. You can read about it here:
Caitlin Young commented
Agreed this is a frequent request from our business users to clearly declare that certain baselines are aligned to specific milestone events.
I'd like to add an alias to each baseline to differentiate budget years (2017, 2018, etc).
Gord Schmidt commented
And make this information and the date/time the baseline was taken to be accessible via reporting!