Is there some way to create task in a program that no get defined as key task? I try to put the "key task" attribute in the list but i can't edit it.
Any idea would be very nice.
Thanks for the help!
Checked in r8.1 and the same thing there. So apparently it is working as designed, but not saying whether or not as desired.
I don't think you can add a normal task to a Program. All the ones you create will be milestones in a Program.
Tried to create new tasks in programs in sandboxes 13.2 and 13.3. On both systems I could only create key milestones and could not remove the "key" attribute afterwards on properties page, list view or in properties opened from Gantt. More over by default they were open for time entry. Appears buggish to me.
One thing to try is XOGing.
Programs can only have milestones
Hi Mike, thanks for your help. I know programs can only have milestone, my problem is that Clarity is setting my program tasks as milestones and key tasks.
I need to set it as milestones but not all of then as key tasks.
Ok. I understand it better.
If you read the definition of Milestone and Key Tasks -
A milestone task indicates a critical point in a project, such as the completion of the first phase of the execution.
Specifies a major event or activity in a project and it indicates the phase completion or major deliverable or any significant achievement of your project during the execution of the project.
Specifies whether you want to identify a task as a key task. A key task is significant for other tasks.
Since a milestone depicts significant task on the WBS, you would see a milestone task marked as key tasks
"...Clarity is setting my program tasks as milestones and key tasks" - what you mention as program tasks are actually "milestones", and 'cause they are "significant task on the WBS", they are marked as "key tasks"
That make sense, although when you are creating milestones in a Project we can set it as key task or not why in program all milestones must be key tasks? That is what i don't get!
Do you guys think it could be a bug, or just "Working as designed"?
Thanks again for your help.
One way to look at it would be that at a project level not all milestones can be considered key and may just represent an event/activity completion.
At a program level (level above project) milestones would have to be considered key... just a guess
I would say, it is working as designed, but you can always put in an idea to check if others agree.
Thanks Urmas, you are the best. I'm resigned! I'm going to use some workaround to accomplish the customer request.
Retrieving data ...