![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Filters do not get updated properly Topic Summary: Created On: 14-Jan-2004 23:02 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: So. You have defined a view that has a filter that specifies a specific module. If you copy the project the view in the new project still mentions the module in the old project, rather than the module in the new project. It sounds like you are saying that references to modules should always be relative to the 'current' project. That may be the case but it isn't. You'll find similar behavior when you copy a module that has links to itself: the new module now has links back to the old module. This sort of behavior is because, generally, internal DOORS references tend to be to module identifiers rather than to module names. That's a good thing when you rename the module (the reference is still valid) but tough when you do copies. This really isn't a "bug" but it sure would be nice if they "fixed" it. The problem is coming up with all the scenarios and how to handle them. - Louie | |
![]() |
|
DOORS 5.2 and 7.0 SP1
I just wanted to point out yet another bug in DOORs. When I make a copy of a project (call it project A) and DOORs automatically names the new project "Copy of project A" But what DOORs does not do is to rename all of the filters that may be applied to views. For example: Project A has a filter that says "has no in-links through /Project A/Test Case Link Module" After I copy Project A to "Copy of Project A" Copy of Project A has a filter that says "has no in-links through /Project A/Test Case Link Module" when it should really say "has no in-links through /Copy of Project A/Test Case Link Module" Because we want to re-use a single project template for requirements management this bug/feature/nuance (whatever) is a real pain. Looks like more DXL Fixup code is going to have to be written. |
|
![]() |
|
![]() |
|
So. You have defined a view that has a filter that specifies a specific module. If you copy the project the view in the new project still mentions the module in the old project, rather than the module in the new project.
It sounds like you are saying that references to modules should always be relative to the 'current' project. That may be the case but it isn't. You'll find similar behavior when you copy a module that has links to itself: the new module now has links back to the old module. This sort of behavior is because, generally, internal DOORS references tend to be to module identifiers rather than to module names. That's a good thing when you rename the module (the reference is still valid) but tough when you do copies. This really isn't a "bug" but it sure would be nice if they "fixed" it. The problem is coming up with all the scenarios and how to handle them. - Louie |
|
![]() |
|
![]() |
|
Louie,
I agree with you completely on the fact that they should fix it. I also understand why this may not be considered a "bug". But, I contend that if they allow copying of items that potentially could be copied with incorrect data they should at least try to provide some indication as such. At the least, they could warn the user or even prompt the user if they want to: 1.Maintain original references 2.Change all references to the newly created item(s) 3.Display or print the references that may need to be changed due to copying. I just think that allowing a copy to occur without providing any indication of potentially incorrect data is too dangerous to ignore. |
|
![]() |
Telelogic DOORS
» General Discussion
»
Filters do not get updated properly
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.