Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Excluding tasks with associated objects
Topic Summary: Excluding tasks with associated objects causing parallels
Created On: 3-Jul-2006 19:48
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
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.
 3-Jul-2006 19:48
User is offline View Users Profile Print this message


Alicia Campbell

Posts: 9
Joined: 29-Sep-2005

I'm new to Build mgmt and Synergy so maybe someone can tell me what I'm doing wrong.  I have excluded some tasks that have objects associated to it.  We did not make fix task and do not intend to complete this task for a baseline, so we also do not want the objects. I had assumed when a task was excluded then the objects where excluded as well, but some users have been checking out the objects and building off of them, which is causing some parallel conflicts.  Should I have excluded the tasks and deleted the objects as well?  Some of the users do not want these objects deleted right away in case they can provide a fix.  How do I keep these objects from being checked out by other users?  Any suggestions would be greatly appreciated.
Thanks,
Alicia
Report this to a Moderator Report this to a Moderator
 6-Jul-2006 09:00
User is offline View Users Profile Print this message


Gilad Benjamini

Posts: 6
Joined: 9-Mar-2006

I ran into similar problems. I don't have a real good answer, but if users stick to standard work flows, then this should not happen. I.e. if users simply update-members, and by that use recommended versions of objects, then the objects from the excluded tasks would not be used. When users do something beyond that, they have a good chance of making mistakes, and sadly enough the system doesn't prevent them from doing so.
Report this to a Moderator Report this to a Moderator
 12-Jul-2006 15:33
User is offline View Users Profile Print this message


michael Barnes

Posts: 85
Joined: 12-Nov-2003

It seems likely to me that the following occured:
1. the users had reconfigured with the tasks and got the objects.
2. You excluded the tasks.
3. Users modified the objects.

To prevent this, users should reconfigure before starting new work (so that new stuff from others is brought in and excluded stuff is removed).

Alternatively, as you mention parallels, it is possible that (say) version 5 of an object was OK; excluded task created version 6; user-reconfigure reset version in project to 5; user checked out to version 5.1.1, giving paralells.
If this is the scenario, then there is (probably) nothing to worry about.


There are probably lots of other possibilities in general, and it is difficult to determine the cause and correct course of action without looking at the specific situation.


As you ask "how to fix the situation", the following would work, but great care is needed:
A) stop people working.
B) create a prep project with the current state.
C) use the "use" option to get the correct version of each object in the project.
D) check in the project to a static state.
e) update reconfigure templates so that developers use this project as the baseline.
F) Get everyone to reconfigure and to verify that they have the correct versions in their projects.

Mike.



Edited: 12-Jul-2006 at 15:37 by michael Barnes
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
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.