Feature ideas

Allow to trigger and approve actions from the MCP server to enhance the integration for both developers and agents

It would be great if Port Self Service Actions allowed to have an input field in table format for users. We need users to input multiple times 4 related inputs which would be better visualized as a table (this is how we manage it in another tool currently). Without a table view, the UX is not good. Use case: Developers need to input network information This information is in a table naturally (DNS | IP | Port | Something else) The information may need to be inputted multiple times in a form They need to make sure the data matches the other data (DNS with IP and such)

Currently you can configure inputs so that a step has no visible inputs based on previous steps. Port should automatically hide or skip steps that have no visible inputs.

Currently any approval for a self-service action requires the approver to log into Port to approve the action. It would be great if a user could approve directly from either an email or slack/teams notifications. This helps improve the UX and simplify the approval process.

It would be great to have an option to do bulk actions(day2 and DELETE) on entities

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

In case of very dynamic action forms (where the form changes as result of certain inputs) it would be ideal to be able to make certain inputs required dynamically, as result of a certain field change. An input can be hidden until a certain point, and then when it is visible it might be required. You cannot set it as required, since it if remains invisible it will cause triggering issues.

In some cases an operation failed and a retry will solve it. Adding a retry action for a run can be nice addition :)

Hi, We have an on_call_duty blueprint where we define the triager for each week. We would like to fill the assignee based on the current week's triager on a user form. I managed to do this with the following configuration ```json "week_number": { "type": "string", "title": "Week number", "blueprint": "on_call_duty", "format": "entity", "default": { "jqQuery": "now | strftime(\"%V\") | \"week_\"+." } }, "assignee": { "type": "string", "title": "Assignee", "format": "user", "dependsOn": [ "week_number" ], "default": { "jqQuery": ".form.week_number | .properties.triager" } } ``` On the first load of the form, the week number gets filled but not the assignee . If I close the form and reopen, the assignee gets filled properly. Could you make the dependsOn configuration to be aware of dynamically set default values? Thanks in advance!

Currently, the depends_on functionality in self-service actions only works when the referenced field is part of the userInputs section. Enabling the depends_on for blueprints as a part of Day 2 actions would be beneficial.