devynspencer / powershell-sdp-cloud Goto Github PK

Update resolution and mark as resolved/closed in one action.

For example, lookup available values for change stage, instead of having to manually determine them from an existing change.

Each additional criteria needs a logical operator shoehorned into it, and grouping them into parent/child relationships is also cumbersome.

Save change to file for use as a template or example. Alternatively use Export verb?

For example, if we only need a handful of properties from a large number of resources, only include those fields in the response objects.

Perform basic category operations

Verify tickets have a category that makes sense based on subject?

There doesn't appear to be a built-in way to send messages via the API. That said, an email with the correct subject could be generated, and the ticket email determined and included as well.

Get-ServiceDeskRequest -Id 12345 | Send-ServiceDeskMessage -Text "Here is an email update to a specific user. It will be added to the ticket conversation." -To devyn.spencer@example.com -Cc worker.bee@example.com

Not a direct consumer of an API resource - more of a convenience function.

# Rename a ticket
Get-ServiceDeskRequest -Id 12345 | Rename-ServiceDeskRequest -Subject "New subject here"

# Add a prefix to an existing ticket
Get-ServiceDeskRequest -Id 12345 | Rename-ServiceDeskRequest -Prefix "FIX: "

# Add a suffix to an existing ticket
Get-ServiceDeskRequest -Id 12345 | Rename-ServiceDeskRequest -Suffix "- DUPLICATE"

• Create new standalone task (i.e. using /api/v3/tasks endpoint)
• Create new child task on request
• Create new child task on problem
• Create new child task on change
• Create new child task on project
• Create new child task on project milestone
• Create new child task on release

Update README with a Getting Started section.

Allow for a number of source formats, but ideally we could focus on markdown.

It would be huge to be able to sync solutions against a directory of markdown files (potentially with header data for indicating the solution id, tags etc).

Provide metrics on one or more requests. Include individual parameters to customize the output.

Update README with a table of environment variables and/or Microsoft.PowerShell.SecretStore secrets used by the module.

Submit for approval, triggering approval workflow.

• Convert/format property names in PascalCase instead of snakeCamel_shitshow case.
• Include response codes and other useful information about the request
• Remove pagination information
• Add tests to verify consistency across all resource types
• Document expected output format

• Handle the error
• Suggest the user runs Request-ZohoAccessToken (or run automatically)

Assuming we can't remove the requests.

Add Pester tests for basic module structure, features, manifest metadata and similar. It should be easy to identify modules that have drifted from the set standard.

Add and configure PSDocs or similar.

Support searches using multiple categories, technicians etc.

Group other resources to the change. Ideally could link all resource types with change.

Duplicate an existing request, while allowing for customizations:

Copy-ServiceDeskRequest -Id 12345 -Subject "Slightly different subject"

• Get large number of changes (but limit returned fields to those that will be exported), storing all unique values for properties like template.name, change_type.name etc.

Update README with a standardized set of deployment steps.

Update README with a table of features.