Transposit Activities provide a single source of truth across incidents, tasks, and all operational events — all with automatic documentation
Ticketing is a great way to keep track of the progress of work, but manually updating tickets every time you’ve taken action in another tool or system can be tedious and time consuming. We’re going from GitHub to Jira, to AWS and back to Jira, to Slack and back yet again to Jira — all to document the work that’s been done.
But what if all that documentation could be done automatically? That’s what Transposit Activities provide — a single source of truth across incidents, tasks, and all operational events — all with automatic documentation. Activities are the container for all automation and processes, providing context, visibility, and actionability across the organization.
Activities can be auto-updated by taking the output from an action in a runbook and piping it into the activity field, ensuring context is always up to date, with less manual toil. This level of documentation and transparency streamlines efforts and provides confidence that tickets are being addressed quickly and correctly.
In order to reap all the benefits of activities, it is important to understand how to set them up. One of the hallmarks of Transposit is the fact that its functionality is able to be customized without coding, meaning that any member of your team, technical or non-technical, has the ability to put activities setups in place and even customize their features and functions.
Start by clicking the New button in the Transposit toolbar, and then select the category of the activity within the dialogue box. By default, you will be provided with default types of activities within the dropdown which include Incident and Task.
However, as with most fields and inputs throughout Transposit, you can customize the types of activities to make them tailored and intuitive for your team and the nature of the work. Some common activity types users create are service requests, user provisioning, and change requests, but they can literally be anything you want. If you wish to add custom activity types, click the gear button in the top right corner of the dashboard and click Activity Types.
Within this window, you can add new activity types with customizable activity fields.
The New Activity dialogue box has a lot of other options and fields that must be configured as well in order to optimize the activity’s utility. Some of these fields are required, if so indicated, and others are optional.
The corresponding fields are different for the default types of activities: an Incident and a Task. The default configuration for an incident is designed to help triage and resolve a problem. The standard fields for an activity categorized as an incident include:
The default configuration of an activity categorized as a task is designed for scheduling and prioritizing to-do items for the team. The standard fields for an activity categorized as a task are mostly the same as an Incident, but there are some unique fields as well, which include:
On any of your activities, you are not limited to the default configuration of these fields. You are able to add new types of fields depending on the specific needs of your team or the type of project you are undertaking. And if you are constructing a new type of activity rather than using one of the default options, this will be necessary. To add custom fields to your activity, click the gear button in the top right corner of the dashboard, and select Activity Fields at the bottom of the dropdown. From this All Activity Fields page, you can see all of the fields that are currently in use in your various Activities.
To create a new field, click the button in the top left corner of the page that says New activity field. Within this new field page, you have three dialogue boxes that you must complete.
First choose the activity Name and ID, which must end in an alphanumeric character and can only contain lowercase letters, numbers, and the underscore character. The third field, Type, contains a dropdown with every different type of pre-made entry configuration possible in Transposit. These entry types include:
Although activities can easily be created from scratch as described above, Transposit also integrates with Slack, the third-party business communication platform. Once Transposit is synced with your organization’s Slack, within a Slack channel, you simply need to type /transposit new and hit Enter and you will be prompted with the same dialogue box workflow described above.
Note that unlike within the Transposit dashboard, you will be restricted to the activity options already created in your Transposit backend, so if you wish to create a new type of event, you must do this in your dashboard before creating an activity of this type within Slack.
You can also edit an activity within Slack using /transposit edit.
The synchronization and automation of Transposit makes it effortless to create activities as dictated by the events taking place in your workflow. Inside the Transposit dashboard, each incoming event appears in the activity feed. These events have an embedded Create Activity button right inside of them, which opens the same dialogue box as described above.
Similarly, if you configure it to do so in Slack, events may also appear in your Slack channels as well. As in the Transposit feed, the event in Slack will appear with a Create Activity button that opens the same Activity dialogue box.
Once you have created an activity and filled out each of the corresponding fields, it will appear in the Activity Overview and the Timeline of your team’s Transposit dashboard.