Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Louie Landale, on Friday, January 23, 2004 1:19 PM

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
 14-Jan-2004 23:02
User is offline View Users Profile Print this message


Douglas Zawacki

Posts: 97
Joined: 14-Aug-2003

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.
Report this to a Moderator Report this to a Moderator
 19-Jan-2004 20:30
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Answer 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
Report this to a Moderator Report this to a Moderator
 20-Jan-2004 01:12
User is offline View Users Profile Print this message


Douglas Zawacki

Posts: 97
Joined: 14-Aug-2003

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.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.