Feature Requests

Details: After upgrading from IDP v1 to v2, all our catalog templates were converted to Inline templates. We’re now migrating them to a remote repository using the "Move to Git" feature. Our organization enforces a Git commit policy that requires including a JIRA story number in every commit message. Currently, when using the "Move to Git" option in IDP, there is no way to specify a JIRA story number or customize the commit message. Request: Please enhance the "Move to Git" workflow to allow users to: Enter a JIRA story number. Customize the commit message before committing.

When running an API call to a non-existent entity, we see a return of all values, rather than a message that we are accessing an entity that doesn't exist. We need better indicators because. this is incredibly misleading.

Hi Team, Currently, We did not correctly show the status of long running steps in IDP. Steps will show as running even though it has finished execution. We would like IDP to report the correct status.

Currently the Git Clone step suppprts using a connector with GitHub using GitHub App authentication. The Direct push only supports using username and password and not GitHub App auth.

Currently, user has to click the dropdown and select the desired value from the list. What needs to be done, to have the first value as default value, as this will avoid clicking and opening of the dropdown list.