Feature ideas

It's nice to have some log stream formatting options. I like the approach Azure Devops uses. Could you implement something like this: https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash Not sure if GitHub actions or Jenkins have something similar, to cover several CI/CD systems in a one shot, and highlight log lines automatically. Additionally, to this, it's nice to have some console auto colouring support, like on the TF plan screenshot:

Is it possible to differentiate between the existing "Text" (which translates to a simple input field) and a more expansive "Text area" (which would translate to a text area input field)? We have a few use cases where we were trying to avoid the overhead of formatted text/adding an extra click to interact with the markdown editor, and really just focused on a bit more visual space for both the input and display of plain, unformatted text. Consider the example of the description for a portal feedback item in the demo site - something like this , where I was imagining that the description might render on multiple lines and/or two columns, instead of needing to hover to see the full text.

Using the online demo as an example, there is currently a self-service action named "Add/Remove Service from Favorites". In my head, the ability to make an action conditionally available (based on one of more properties of the selected entity) would allow "Add Favorite" as an action for services that were not yet a favorite for me - while "Remove Favorite" would only be available for services that were already my favorite (this same thought process could be applied to the existing actions "Unlock Service" and "Lock Service"). Similarly (and maybe more compelling), an action like "Deploy Service" might only be available once certain criteria are met (an extension of sorts to the concept of scorecarding). Again referencing the demo service catalog, I could also see additional actions based on a distinguishing property like "Language" - maybe in our environment Python is managed distinctly different from React, and as such only certain actions would make sense in each context. (There is also this feature request which also feels related...but not entirely overlapping.)

We have a use case where context is everything - and having the page that the user was on when they triggered the self-service action is an important part of that context. Potentially, this could be a part of the trigger object (potentially as a new from key, alongside the existing "origin": "UI" ?). We have tried thinking about potential workarounds, and all we have come up with so far is to either ask the user to pick which page they came from (forcing us to maintain an enum of existing pages - both unwieldy, and requires additional maintenance) or create one action per page (where the only difference between the actions is that hidden page attribute - again, quite unwieldy and adds a lot of additional maintenance).

Currently, search conditions cannot be applied to calculated properties in self-service actions. Adding support for this is required

When creating an action with approval you can't see who is the action approvers in the run page. That can be helpful to know who can I reach to ask them to approve my run.

For certain actions it would be helpful to have a bigger text area (like the description when creating a Jira issue ) with the ability to add links, images, and videos

We have a few places today where we are attempting to link to a specific self-service action, and have had success using a relative URL like /self-serve?action=[action.identifier] . As an example, we have the following action today: action identifier : create_dbt_repo action inputs : team_name ( enum ), app_name ( string ) It would be nice to be able to default one or more values in the self-service action user input form (on a per instance basis) with a URL like: /self-serve?action=create_dbt_repo&app_name=test . (Note: This is different than defaulting the field at the form level - if someone comes in and manually triggers this action, I don't want to default anything for app_name - but in cases where we are linking to the action from specific pages elsewhere, it would be nice to use the information known at that point to drive some context-specific defaults when they arrive on the self-service action form.)

We'd like to be able to adjust the content of the Approval Message sent to slack for Approval protected actions

Now that a deep link to a specific self-service action is available, we have taken advantage to link directly to a self-service action. Specifically, we have made a similar portal feedback mechanism to the one offered in the demo site, and then added a hyperlink within the description of a given page like "Have feedback about this page?" which is hyperlinked to the "Leave feedback about the portal" Day 2 action. Unfortunately, this link takes the user to the Self-service page (albeit with the correct action modal opened to the form). Completing the form then leaves then on the Self-service page. Similar to how related self service actions are handled within an entity table or from an action card, it would be nice to have a way to trigger the display of the appropriate self-service action form as a modal over the page that the user is currently (perhaps with some opinionated/specially handled markdown syntax to designate creating a link to trigger the display of a specific self-service action?).