What Are Automations?

In project management, "Automations" refer to the feature that allows users to set up automatic actions or workflows based on specific triggers or conditions. These automations are designed to reduce repetitive tasks and increase efficiency within a project.

Automation Key Functions in DevStride

Search Bar

The search bar in DevStride plays a crucial role in enhancing automation and efficiency within the system. By providing a powerful and intuitive search functionality, it allows users to quickly locate and access specific project-related information, tasks, documents, or resources. With the ability to search through vast amounts of data, the search bar simplifies the process of retrieving relevant information, saving users valuable time and effort.

Moreover, the search bar in DevStride also facilitates automation
by enabling users to create customized searches and save them as templates.
This feature enhances productivity by allowing users to quickly access frequently searched items or perform routine searches with just a few clicks. By defining search criteria once and saving them as templates, project managers can automate the process of retrieving specific information or generating reports on a regular basis.

For example, a project manager can create a search template to view all overdue tasks assigned to a particular team member, saving time and ensuring timely follow-ups. The search bar's ability to support automation in this manner empowers project managers to focus on higher-level decision-making and strategic planning, while routine search tasks are handled seamlessly in the background, resulting in improved productivity and streamlined project management processes.

Toolbar

The toolbar serves as a convenient and accessible hub that empowers users to use essential features such as the Search bar and Automation Filters.

With the Search bar integrated into the toolbar, users can swiftly enter keywords,
project names, or specific criteria to quickly locate relevant information.

The search functionality can be further enhanced by the inclusion of Automation Filters.

These filters enable users to define specific triggers, condition fields, actions, statuses, and creators to narrow down search results and automate certain tasks. By leveraging the Automation Filters, project managers can effortlessly sift through vast amounts of data, identify patterns, and streamline workflows based on pre-defined rules.

This seamless integration of the Search bar and Automation Filters within the toolbar ensures that users have quick and easy
access to the tools they need for efficient project management.

To optimize screen real estate and provide users with a clutter-free workspace, the toolbar view in the Project Management software is designed to be collapsible. This collapsible feature allows users to hide or expand the toolbar based on their preference or the context of their work.

When collapsed, the toolbar occupies minimal space, providing users with a larger viewing area for project details, timelines, or task lists. This collapsible view not only maximizes the available workspace but also offers a customizable and adaptable interface for users to tailor their project management experience.

Name

In the Automations page of DevStride, the Name function serves as a crucial element for organizing and identifying automation rules. It allows users to assign a descriptive and meaningful name to each automation, making it easier to locate and manage specific rules within a growing list of automations.

By providing a clear and concise name, users can quickly discern the purpose and intent of an automation without the need to delve into its details. The Name function acts as a labeling mechanism, ensuring that users can efficiently navigate and modify automations as needed, leading to improved organization, clarity, and overall ease of use within the project management software.

Description

The "Description" function within the Automations page of DevStride serves as an
essential tool for providing additional context and information about an automation rule. It allows users to include detailed explanations, instructions, or notes that further clarify the purpose, behavior, or intended outcomes of the automation.

With the Description field, users can document the rationale behind specific automation decisions, outline the expected results, or provide guidance to other
team members involved in the project. This function enhances collaboration, ensures consistency, and minimizes confusion by enabling users to communicate important details and considerations within the project management software itself.

By leveraging the Description function, project managers and team members
can foster better understanding and facilitate effective communication
within the context of automation rules.

Enable

The "Enable" function on the Automations page in DevStride allows users to activate or deactivate automation rules as needed. By toggling the Enable button, users can control whether an automation is actively running and executing its defined actions or if it is temporarily paused. This function provides users with the flexibility to enable or disable automations based on project requirements, changing circumstances, or specific workflow considerations. Enabling an automation enables it to monitor relevant triggers, evaluate conditions, and trigger the defined actions, contributing to the automation and streamlining of project management processes.

On the other hand, disabling an automation temporarily suspends its execution, allowing users to fine-tune its settings, review its behavior, or accommodate any changes in project dynamics. The Enable function grants users granular control over their automations, empowering them to adapt and optimize their workflow while maintaining a seamless balance between automation and manual intervention.

Run History

The "Run History" function provides users with valuable insights and a comprehensive record of past automation executions. By accessing Run History, users can review the details of each automation run, including the date and time of execution, the specific triggers and conditions that led to the automation being triggered, and the resulting actions taken. In DevStride, the above are classified as Run Date, Status, and Actions Executed.

With the ability to analyze past runs, users can identify patterns, troubleshoot any issues or errors that may have occurred, and fine-tune their automations for optimal results. The Run History function serves as a valuable tool for monitoring and evaluating the impact of automations, ensuring that they align with project goals and
contribute to increased efficiency and productivity in project management workflows.

Duplicate

The "Duplicate" function on the Automations page in DevStride allows users to create identical copies of existing automation rules with a simple click. This function streamlines the process of creating new automations by eliminating the need to manually recreate complex rule configurations from scratch.

By duplicating an automation, users can leverage pre-defined settings, triggers, conditions, and actions as a starting point for new automation rules. This not only saves time but also ensures consistency and accuracy in setting up similar automations.

Users can then customize the duplicated automation by modifying specific details, such as triggers, conditions, or actions, to suit the unique requirements of the new rule. The Duplicate function provides a convenient way to replicate and adapt automation rules, enabling users to rapidly expand their automation capabilities while maintaining consistency and efficiency in project management processes.

Edit an Automation

The "Edit" function allows users to modify existing automation rules to better align with evolving project needs. By clicking the pencil icon and enabling editing, users can access and adjust various components of an automation, including triggers, conditions, actions, and settings. This function empowers users to make necessary updates, optimize automation rules, and incorporate feedback or lessons learned from previous executions. By providing the ability to edit automations, the software ensures that users can adapt to changing project requirements, refine their workflows, and enhance the efficiency and effectiveness of their automation strategies.

Delete an Automation

By selecting the "Delete" option users are able to permanently remove automation rules that are no longer needed or relevant. Users can effectively eliminate automation rules from the system, freeing up space and decluttering the list of active automations. This function offers a way to manage and maintain automation rules, ensuring that only necessary and up-to-date rules remain in the system.

Deleting obsolete or unused automations helps maintain the overall organization and efficiency of the project management software, preventing confusion and reducing the risk of outdated or conflicting automation rules causing unintended actions.

Created By

"Created By" provides the origin of each automation rule. It displays the name or identifier of the user who initially created the automation. This information helps track ownership and accountability within the project management software, allowing users to identify the individuals responsible for designing and implementing specific automation rules. The "Created By" information serves as a reference point for collaboration and communication, enabling team members to reach out to the original creator for clarification, updates, or modifications to automation rules. Additionally, this feature promotes transparency and visibility within the software, as users can easily identify the authors of automation rules and acknowledge their contributions to the project. "Created By" enhances collaboration, accountability, and effective management of automations within DevStride.

Edit Automations

When This Happens... Then Do This

The connection between the "when this happens" prompt and the "then do this" action in Automations is at the core of creating effective and dynamic automated workflows. "When this happens" serves as a trigger or condition that initiates the automation rule. It defines the specific event, action, or situation that must occur for the automation to be activated.

This trigger can be a wide range of events, such as the creation of a new task, the change in a project status, or the receipt of a specific email. It sets the starting point for the automation process, signaling that certain conditions have been met and an action needs to be taken.

On the other hand, "then do this" represents the set of predefined actions that should be executed once the specified trigger or condition is met. It defines the sequence of steps, tasks, or changes that the automation rule will perform.
These actions can include sending notifications, updating project information, assigning tasks to team members, or generating reports. The "then do this" action enables users to define the desired outcome or behavior of the automation,
determining how the system should respond to the identified trigger.

By combining the "when this happens" prompt with the "then do this" action, users can create powerful and customized automation rules that reduce manual effort and drive efficiency within the project management software. The trigger and action work together to form a cause-and-effect relationship, automating tasks and driving the desired behaviors based on specific events or conditions.

What is a Trigger?

In Automations, a trigger is a specific event, condition, or action that serves as the catalyst for initiating an automated workflow. It acts as a starting point for the automation process, defining the moment or circumstance that prompts the system to execute a series of predefined actions.

Triggers can encompass a wide range of events, such as the creation or
modification of a task, the addition of a new team member, the change in project status, or the receipt of a specific type of email. By defining triggers, users can set precise conditions that need to be met for the automation to activate, ensuring that the right actions are triggered at the right time. Triggers play a vital role in streamlining project management workflows, reducing manual effort, and enabling the system to proactively respond to specific events or conditions, thereby enhancing efficiency and productivity.

What is a Condition?

In Automations, a condition refers to a specific criterion or rule that must be met for an automation to proceed and execute its predefined actions. Conditions act as decision points within an automated workflow, allowing users to define logical rules that determine the flow and behavior of the automation. These conditions can be based on various factors such as specific data values, dates, project statuses, or assigned team members. For example, a condition could be set to trigger an action only if a task is overdue or if a project's budget exceeds a certain threshold.

By incorporating conditions, users can introduce flexibility and customization into their automations, ensuring that actions are taken only when specific requirements are fulfilled. Conditions enable intelligent decision-making within the automation process, allowing for more targeted and contextually relevant actions to be executed, ultimately enhancing the effectiveness and efficiency of project management workflows.

Chaining Conditions

In Automations, chaining conditions refer to the practice of combining multiple conditions within an automation rule to create more complex and sophisticated logic. Rather than relying on a single condition to trigger an action, chaining conditions allow users to specify a series of conditions that must all be met for the automation to proceed. This chaining of conditions enables users to create advanced decision-making processes within their automated workflows.

For example, an automation could be designed to trigger an action only if a task is overdue AND ONLY IF it is assigned to a specific team member AND ONLY IF the project status is marked as "In Progress". By chaining conditions together,
users can create more precise and targeted automation rules that consider multiple factors before executing actions. Chaining conditions provides a higher degree of customization and control over when and how automations are triggered, allowing for greater flexibility and adaptability in project management workflows.

What is an Action?

In Automations, an action refers to a specific task, operation, or change that is executed as a result of an automation being triggered. Actions are the predefined steps or operations that the system performs automatically when certain conditions or events occur within the project management software. These actions can include a wide range of activities, such as sending notifications or emails, updating project statuses, assigning tasks to team members, generating reports, or making changes to project data. Each action represents a specific outcome or behavior that is desired within the automated workflow. By defining actions, users can expedite routine tasks, reduce manual effort, and ensure consistency in project management processes. Actions are the tangible results of automation, allowing users to orchestrate and automate various operations, ultimately improving productivity and efficiency within the project management software.

Chaining Actions

In DevStride, "AND THEN" chaining actions refer to the capability of combining multiple sequential actions within an automated workflow. By using the "and then" concept, users can create a series of consecutive actions that are executed one after another based on the trigger and conditions of the automation. For instance, an automation rule could be set up to send a notification to a project manager when a task is marked as complete, and then update the project status to reflect the task's completion. This chaining of actions allows for a seamless flow of
operations within the automation, enabling users to define a logical sequence of steps that should be followed.

Chaining actions in Automations empowers users to automate complex and interconnected tasks, facilitating efficient project management workflows. It ensures that a series of actions are executed in a specific order, improving consistency and promoting a more efficient use of time and resources.

Item Attributes and Operation

In Automations, an "Item Attribute" refers to a specific characteristic or property of an item within the project management software. It represents the various data fields or attributes associated with an item, such as the name, status, due date, priority, or assigned team member. Item attributes provide contextual information about the item and serve as the basis for defining conditions and triggers in automation rules. By leveraging item attributes, users can create automation rules that are tailored to specific criteria or changes within the project management software.

For example, an automation rule could be triggered when the status of a task changes to "Completed" or when the due date of a project is approaching. Item attributes enable users to customize and define automation rules based on the specific characteristics and data fields associated with items in their projects.

On the other hand, an "Operation" in Automations refers to a specific action or task that is performed on an item within an automation rule. Operations are the actionable steps that the system executes as a result of the automation being triggered and the specified conditions being met. These operations can include a wide range of actions, such as updating an item's status, assigning a team member, sending notifications, creating subtasks, or modifying other item attributes.

Each operation represents a distinct action that is performed automatically to optimize project management workflows. By defining operations within automation rules, users can eliminate manual effort, ensure consistent actions are taken,
and create efficient processes that align with their project requirements.

Operations are the building blocks of automation, allowing users to define the specific tasks and changes that should occur when triggered by specified conditions.