Difference between Tasks, Project Tasks, or Issue Tracking lists?

[snsd]

Hi:

Complete newbie here. Is there any detailed documentation out there as to
the fundamental differences between "Tasks", "Project Tasks", and "Issue
Tracking" lists? They all seem pretty similar - but I want to make sure I
understand the differences before deciding which to use in varying scenarios.

Thanks,

Dave

[Vaibhav Desai]

Check the following.

http://office.microsoft.com/en-us/sharepointtechnology/HA011611831033.aspx
(tasks)
http://office.microsoft.com/en-us/sharepointtechnology/HA100852271033.aspx
(project tasks)
http://office.microsoft.com/en-us/sharepointserver/HA101744921033.aspx
(issue tracking list)

Regards,

Vaibhav Desai

[snsd]

Thanks for the response. After reading the info found in the links, it's
still not really clear what the pros of using one over the other are. It
seems to me that if you are going to customize your lists that it really
doesn't matter which of the 3 one uses. I'm just trying to make sure I don't
back my self into a corner and discover "if I had only known" and used the
other list type... In other words, are there any features that ONLY exist in
one of the 3 types - and not in the others.

Dave

[spconsultant]

I have found that the pre defined lists are BEST when not customized,
and when used for their designed purpose. They have special coding
that has it built in constraints that sometimes down the road will
paint you into a corner. An example is trying to modify the task list
to allow for multiple "assigned-to" people. You can very easily make
the mod so you can enter more than one assigned-to person, but it
might break some of the notification logic later. I had a client that
wanted to create an "archive" issues list, where they could move old
issues via workflow, but refer to them later. The problem came in
trying to keep the link for the appened comments field working.You can
usually add fields as needed, be careful when deleting fields (beter
to "non-display" them).

On Oct 6, 9:14 am, snsd <s...@discussions.microsoft.com> wrote:
> Thanks for the response. After reading the info found in the links, it's
> still not really clear what the pros of using one over the other are. It
> seems to me that if you are going to customize your lists that it really
> doesn't matter which of the 3 one uses. I'm just trying to make sure I don't
> back my self into a corner and discover "if I had only known" and used the
> other list type... In other words, are there any features that ONLY exist in
> one of the 3 types - and not in the others.
>
> Dave
>
>
>
> "Vaibhav Desai" wrote:
> > Check the following.
>

> >http://office.microsoft.com/en-us/sharepointtechnology/HA011611831033...
> > (tasks)
> >http://office.microsoft.com/en-us/sharepointtechnology/HA100852271033...

> > (project tasks)
> >http://office.microsoft.com/en-us/sharepointserver/HA101744921033.aspx
> > (issue tracking list)
>
> > Regards,
>

> > Vaibhav Desai- Hide quoted text -
>
> - Show quoted text -

[snsd]

Good advice. Thank-you. I still have the question about whether there is any
fundamental difference between the 3 types. It seems to be that there is
simply some different display capabilities - but there must be more than
that. Any clarification would be appreciated.

[Greg Abbott]

From what i have found the different is Issue Tracker comes out tof the box with a Text Box that will keep all entries threaded meaning you will not overwrite the text, it will simply be appended. Of course you can always use versioning to track this in any list.

The other difference is a Task list is integrated into Outlook. In the cations tab you can connect to outlook, i dont see this feature with the issue tracking list.

There may be more but those are the difference that I can see.

Greg

>> On Monday, October 06, 2008 9:14 AM sns wrote:

>> Thanks for the response. After reading the info found in the links, it's
>> still not really clear what the pros of using one over the other are. It
>> seems to me that if you are going to customize your lists that it really
>> doesn't matter which of the 3 one uses. I'm just trying to make sure I don't
>> back my self into a corner and discover "if I had only known" and used the
>> other list type... In other words, are there any features that ONLY exist in
>> one of the 3 types - and not in the others.
>>
>> Dave
>>
>> "Vaibhav Desai" wrote:

>>> On Monday, October 06, 2008 12:09 PM sns wrote:

>>> Good advice. Thank-you. I still have the question about whether there is any
>>> fundamental difference between the 3 types. It seems to be that there is
>>> simply some different display capabilities - but there must be more than
>>> that. Any clarification would be appreciated.
>>>
>>> "spconsultant" wrote:

>>>> On Tuesday, October 07, 2008 9:50 PM Vaibhav Desai wrote:

>>>> Check the following.
>>>>
>>>> http://office.microsoft.com/en-us/sharepointtechnology/HA011611831033.aspx
>>>> (tasks)
>>>> http://office.microsoft.com/en-us/sharepointtechnology/HA100852271033.aspx

>>>> (project tasks)
>>>> http://office.microsoft.com/en-us/sharepointserver/HA101744921033.aspx
>>>> (issue tracking list)
>>>>
>>>> Regards,
>>>>
>>>> Vaibhav Desai

>>>>> On Tuesday, October 07, 2008 9:51 PM spconsultant wrote:

>>>>> I have found that the pre defined lists are BEST when not customized,
>>>>> and when used for their designed purpose. They have special coding
>>>>> that has it built in constraints that sometimes down the road will
>>>>> paint you into a corner. An example is trying to modify the task list
>>>>> to allow for multiple "assigned-to" people. You can very easily make
>>>>> the mod so you can enter more than one assigned-to person, but it
>>>>> might break some of the notification logic later. I had a client that
>>>>> wanted to create an "archive" issues list, where they could move old
>>>>> issues via workflow, but refer to them later. The problem came in
>>>>> trying to keep the link for the appened comments field working.You can
>>>>> usually add fields as needed, be careful when deleting fields (beter
>>>>> to "non-display" them).
>>>>>
>>>>>
>>>>>

>>>>> On Oct 6, 9:14=A0am, snsd <s...@discussions.microsoft.com> wrote:
>>>>> n't
>>>>> e
>>>>> in