Orphaned Activities?
Our Cireson Portal implementation is in about year six now. We are using more and more 'activities' with Service Requests as we get our Request Offerings designed that automatically builds them so monitoring the status of these Activities is becoming more formal. One thing that I've noticed is we have a number (around 500) Activities that seem to be orphaned from active requests. They are accessible in our SSRS 'archive' environment but no longer accessible via the Cireson portal.
I would like to clear these Activities out somehow, so that our reports/metrics are accurate.
How can I do this? Powershell?
Answers
PowerShell?
Yes. 😁
But in all seriousness, when you say orphaned Activities what specifically do you mean? Are they Activities...
Yes, they are MAs, probably some RAs as well. They have no associated/parent work item in the system.
Some are pending, some are 'in progress'. I don't think any are cancelled/failed.
My guess is early in our deployment there was some database issue where some database surgery was done and I think the parent work items were deleted. Just a guess. I'm not the admin of our system, just trying to help resolve an issue.
EDIT: These MAs/RAs are in our data warehouse.
Thanks Adam!
If they are in the:
Appreciate the info Adam.
The PowerShell for making these edits, I can certainly construct on the fly. But your report queries sound like you need some INNER JOINS to ensure you're only capturing Activities + Parent Work Items. I'd have to see it to really help on this front.
Manual Activities with a Status of In Progress and Title of "Order Laptop"
You can get a list of Activity Status enums with the following PowerShell so you could substitute the GUID above:
Just make sure before you mass update a bunch of Manual Activities that the $mas variable contains the Manual Activities that actually need to be updated though!
Had a chance to look at this some more. Rather than 'clear' them out, is there a powershell process to mark these Activities 'skipped' or 'completed'? This would also resolve our issue I believe.
Yes - the above PowerShell you can use/adapt to shift manual activities to a different status.