Comments on: EndUserSharePoint.com: Extending Issues and Tasks: Part 3 http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/ Immediate Solutions for Everyday Business Problems Tue, 24 Nov 2009 17:20:26 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: EndUserSharePoint.com: Extending Issues and Tasks: Part 4 | End User SharePoint http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/comment-page-1/#comment-10554 EndUserSharePoint.com: Extending Issues and Tasks: Part 4 | End User SharePoint Wed, 18 Feb 2009 14:59:07 +0000 http://www.endusersharepoint.com/?p=843#comment-10554 [...] parts 1, 2, and 3,  you built a slick-looking extension of SharePoint’s Tasks and Issues.  If you let the [...] [...] parts 1, 2, and 3,  you built a slick-looking extension of SharePoint’s Tasks and Issues.  If you let the [...]

]]>
By: Amita http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/comment-page-1/#comment-8069 Amita Fri, 24 Oct 2008 17:15:58 +0000 http://www.endusersharepoint.com/?p=843#comment-8069 I'm trying to figure out what I did wrong here. I closed out an issue that still had an open task related to and didn't get the error message. Did I miss something? -aps I’m trying to figure out what I did wrong here. I closed out an issue that still had an open task related to and didn’t get the error message. Did I miss something?

-aps

]]>
By: Links (10/8/2008) « Steve Pietrek - Everything SharePoint http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/comment-page-1/#comment-7814 Links (10/8/2008) « Steve Pietrek - Everything SharePoint Thu, 09 Oct 2008 00:27:06 +0000 http://www.endusersharepoint.com/?p=843#comment-7814 [...] EndUserSharePoint.com: Extending Issues and Tasks - Part 3 [...] [...] EndUserSharePoint.com: Extending Issues and Tasks – Part 3 [...]

]]>
By: SharePoint Daily http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/comment-page-1/#comment-7800 SharePoint Daily Wed, 08 Oct 2008 12:11:26 +0000 http://www.endusersharepoint.com/?p=843#comment-7800 <strong>SharePoint Daily for October 7, 2008...</strong> Top News Stories Microsoft Will Bow In-Memory Analysis, Appliance-Ready Database in 2010 (intelligent... SharePoint Daily for October 7, 2008…

Top News Stories Microsoft Will Bow In-Memory Analysis, Appliance-Ready Database in 2010 (intelligent…

]]>
By: AutoSponge http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/comment-page-1/#comment-7790 AutoSponge Tue, 07 Oct 2008 16:05:11 +0000 http://www.endusersharepoint.com/?p=843#comment-7790 Mark, Thanks, that's already on the agenda for the closing article, "I want to add a link to the DispForm.aspx page that starts a new Task related to the Issue being displayed." Mark,

Thanks, that’s already on the agenda for the closing article, “I want to add a link to the DispForm.aspx page that starts a new Task related to the Issue being displayed.”

]]>
By: Mark http://www.endusersharepoint.com/2008/10/07/endusersharepointcom-extending-issues-and-tasks-part-3/comment-page-1/#comment-7788 Mark Tue, 07 Oct 2008 15:28:59 +0000 http://www.endusersharepoint.com/?p=843#comment-7788 The whole thing is very impressive and clever, and also very complex! This is Microsoft's fault, not yours. In response to the first part of this, someone referenced Bamboo's List Integrity web part. I think there is a use case that Bamboo picked up on that your example does not: when am I going to add a task for an issue? When I am looking at an issue. What you really need is a way, when a user is looking at an issue in a list/view or in the display form for an issue, to quickly add a task for that issue, with the issue lookup field prepopulated in the task. If I have, say, 1,000 issues in my list (and half are closed), under your approach each time I create a task I have to cull through the list of issues to find the one I want, even though half are closed. Better for me to be looking at a list of open, relevant issues and then decide to add a task for one of those, with the issue prepopulated. Can you do that in part 4? :) The whole thing is very impressive and clever, and also very complex! This is Microsoft’s fault, not yours.

In response to the first part of this, someone referenced Bamboo’s List Integrity web part. I think there is a use case that Bamboo picked up on that your example does not: when am I going to add a task for an issue? When I am looking at an issue.

What you really need is a way, when a user is looking at an issue in a list/view or in the display form for an issue, to quickly add a task for that issue, with the issue lookup field prepopulated in the task. If I have, say, 1,000 issues in my list (and half are closed), under your approach each time I create a task I have to cull through the list of issues to find the one I want, even though half are closed. Better for me to be looking at a list of open, relevant issues and then decide to add a task for one of those, with the issue prepopulated.

Can you do that in part 4? :)

]]>