Feature ideas

Allow categorizing self service actions for ease of finding appropriate actions for your needs.

Stronger integration with Jenkins in Self service actions, to provide automatic status reflection, and summary log based on pipeline results

Currently as it stands, an action can only be associated with one blueprint. It would be great to have an action be associated with multiple blueprints, for example if we want to restart a service, all catalogs will have service overview and likely this action will be associated with service overview entity. In all scenarios there will also be services from respective container orchestration (ECS/EKS) - right now as it stands an action if associated with service overview entity cant be associated with the service blueprint entity - which means a new actions should be created which can be associated with the service (orchestration layer service). The goal here is to be able to use the lightning button and trigger actions instead of going to the action section and triggering it.

Lack of library of templates for common self-service actions and blueprints (e.g. restart Azure VM, rotate storage keys. It would add great value to Port to have more comprehensive and published library of common self-service actions with their pipelines such that every customer is not trying to reinvent the wheel on common types of actions

Currently, there is no way to offer input selection based on API. Implementing this could allow forms for specific services based on their API responses. For example, create a dropdown selection of Github organizations based on an API call.

Currently, validation does block invalid operators in conditions for day-2 and delete actions, but it doesn’t block invalid property names. This means you can successfully save your action, but when you go to execute, there will be no entities listed in the drop down. If you open the browser dev tools, you will see a "not_found" validation error for the property. This error should be surfaced when you try and save the invalid conditions block. You should not be able to save the action with an invalid property in the conditions block.

Today if a user enters text to a string based input field for a Self Service Action that happens to be invalid determined by a Regex match pattern. The user is presented with a red font colour error message in the format "must match pattern {regex-pattern-here}". Even though we have a human readable validation hint message on the field description. We've had numerous users not find that and instead become blocked and distracted by the red error which they don't understand. To avoid them reaching out to a admin/action owner for support. I would like to be able to set a custom match pattern error message text. If set the user see's my error message and not the default one. So in my guess here I would say something like "Name use lower case characters a-z or numbers 0-9 but can't start with a number. Name must be at least 3 characters long".

Currently, using the dynamic permissions feature, self-service actions will still appear in the UI. In case the user is not permitted, the run will be rejected only after sending the self-service action form. As part of this item, we would like to support hiding/displaying self-service actions using the dynamic permissions policies.

Ability to customize the email that sent to users.

Ability to cancel the execution of an action after triggering it