This is a cross-post from stackoverflow, upon the suggestion of a user there.
My organization is experimenting with new processes to coordinate developers as they integrate their code into our main branch. Right now it's just a basic task list in Sharepoint, but it seems to be doing the trick pretty well. However, there's a lot of tedious manual labor in the creation of those task tickets, and we're looking to improve this. To that end, I have two questions.
1) I've looked through the list of Powershell cmdlets for Sharepoint, but without being a Sharepoint wiz I don't see anything immediately obvious in terms of automated task creation. Can this be done, or are the cmdlets more for administrative (configuration) purposes rather than for usage?
2) Is this a horrible abuse of sharepoint? Ultimately we're just trying to create a centralized location for tasks to be registered with some basic information concerning task details, task owner, and completion status. If there's some obviously better way to do this I'm all ears since no matter what we do we're probably reinventing some wheel or another.