How to edit the baseline description in DOORS 8.3?

On the DOORS 8.3 client, there is not a mechanism to edit the description of a previous baseline. However, we often need to update the description text of the previous baselines when their information is missing or incorrect.

Is there any way to edit the description of a formal module baseline?
cemp - Mon Feb 28 06:36:20 EST 2011

Re: How to edit the baseline description in DOORS 8.3?
SystemAdmin - Tue Mar 01 18:58:38 EST 2011

This question has been asked many times before - unfortunately the answer is "No" - once you have created a baseline, all of the data in that baseline is locked to read-only. There are no explicit documented DXL functions that allow you to change the data of a baseline and as far as I know there are no undocumented under the hood DXL perms that can work around this read-only restriction. Modification at the DB server level is possible but as all DB server files are encrypted this would require the assistance of IBM.

Note for IBM - it would be nice if the DOORS Administrator user could at least change the baseline annotation data as many people have been caught out creating a baseline with incorrect or insufficient info in the annotation.
Paul Miller
Melbourne, Australia

Re: How to edit the baseline description in DOORS 8.3?
llandale - Wed Mar 02 09:29:20 EST 2011

SystemAdmin - Tue Mar 01 18:58:38 EST 2011
This question has been asked many times before - unfortunately the answer is "No" - once you have created a baseline, all of the data in that baseline is locked to read-only. There are no explicit documented DXL functions that allow you to change the data of a baseline and as far as I know there are no undocumented under the hood DXL perms that can work around this read-only restriction. Modification at the DB server level is possible but as all DB server files are encrypted this would require the assistance of IBM.

Note for IBM - it would be nice if the DOORS Administrator user could at least change the baseline annotation data as many people have been caught out creating a baseline with incorrect or insufficient info in the annotation.


Paul Miller
Melbourne, Australia

They should also support some sort of "merge" baseline, where the History of a baseline in moved up to the next baseline, and then that baseline deleted. So when I baseline for delivery version 3.0, need to tweak and re-baseline 3.0a, then tweak and baseline again 3.0b, it would be nice to just get rid of 3.0 and 3.0a and merge into 3.0b.

Baselining should require full RMCDA access to the module.

  • Louie

Re: How to edit the baseline description in DOORS 8.3?
SystemAdmin - Wed Mar 02 16:07:06 EST 2011

llandale - Wed Mar 02 09:29:20 EST 2011
They should also support some sort of "merge" baseline, where the History of a baseline in moved up to the next baseline, and then that baseline deleted. So when I baseline for delivery version 3.0, need to tweak and re-baseline 3.0a, then tweak and baseline again 3.0b, it would be nice to just get rid of 3.0 and 3.0a and merge into 3.0b.

Baselining should require full RMCDA access to the module.

  • Louie

Agreed Louie.

Full configuration management (CM) capability in DOORS would be great - dare I say such features would move DOORS closer towards complying with fundamental Requirements Management principles - full support for the CM concepts of version trees, branching, merging, re-basing and roll back would be a hoot. Is IBM listening?


Paul Miller
Melbourne, Australia

Re: How to edit the baseline description in DOORS 8.3?
cemp - Thu Mar 03 10:40:13 EST 2011

It was worth to try :)