A
anovak
Looks like they created a Issues Log (w/ different name) from an
Issues template. The error message in the queue says something to the
effect that you cannot have more than 1 SP list of the same template
type. I checked their project workspace and sure enough, there was
another Issues Log FOR POST-PROJECT SUPPORT.
We all know that projects start and end. But this is a very good
question though. Once you are live, how do you best track post-
implementation issues?
Use something other than the project workspace entirely, allowing the
project to "end" - perhaps a team-based SharePoint site with that
contains various issue logs for different things like different
systems?
Modify the Category field in the baseline Issue Log to contain a Post-
Implementation type (other than Technical, Functional, Management,
etc.)?
Add a new column to the existing baseline Issue Log that is a checkbox
for post-implementation?
Any and all suggestions would be greatly appreciated.
Thanks,
Andy Novak
UNT
Issues template. The error message in the queue says something to the
effect that you cannot have more than 1 SP list of the same template
type. I checked their project workspace and sure enough, there was
another Issues Log FOR POST-PROJECT SUPPORT.
We all know that projects start and end. But this is a very good
question though. Once you are live, how do you best track post-
implementation issues?
Use something other than the project workspace entirely, allowing the
project to "end" - perhaps a team-based SharePoint site with that
contains various issue logs for different things like different
systems?
Modify the Category field in the baseline Issue Log to contain a Post-
Implementation type (other than Technical, Functional, Management,
etc.)?
Add a new column to the existing baseline Issue Log that is a checkbox
for post-implementation?
Any and all suggestions would be greatly appreciated.
Thanks,
Andy Novak
UNT