Code Repository

SSH clone feature missing from the UI, only HTTPs url available. Many engineering teams use SSH clone approach and not having this basic feature will be a no-go for them to adopt.

Repo import feature for BitBucket server does not work. It throws an error saying 'no such host found. Inability to import from BitBucket will impact the ability to migrate the repos to Harness Code.

Harness repo default branch to be set to master as a standard. Currently the only default option is "Main". In CDK, Master is default and making the switch for all developers in the migrated repos to Main will be an adoption challenge.

The webhook system for a Harness repo seems to be not setup properly. I did not find the below basic functionalities: The ability to send out repo event notifications to a MS Teams channel. We need MS Teams connector as an option available within the webhooks settings of a repo or an app available inside MS Teams. With that a user could interact/acknowledge those events captured in the Teams channel. There is no troubleshooting system for webhooks. Currently a configured webhook just displays a warning sign on failure and there is no way of finding out the actual error or the status code after a webhook call is made. There is no options to select the content type for webhooks. What is the default option? (options could be /json and /urlencoded)

Repo import feature loading glitch, solves by refreshing the screen. Operational Inconvenience for migration team.

After selecting an option from the dropdown, the selected option goes back to being 'Squash and merge' after 3 seconds. There are a couple places where refreshing the browser becomes necessary. After clicking on 'Merge pull request' we don't see the result immediately. This is also the case for approving a PR request. Any glitch in PR merge issue will be an issue for developers and will impact day to day dev operations.

Total no. of PR, commits, branches, tags, contributors etc. display numbers are missing from the banner in the repo list page and the first page of a selected repo.

Pipeline/builds associated with a Harness repo should be visible in the Harness repo module. Lack of this data linkage is going to increase context switching between pages/modules in Harness.

Unable to archive Harness repos. Will cause unused repos to not be able to be archived.

When reviewing PR changes, I use chrome's search feature and it does not find what I am searching for, unless the content is loaded on the screen (possibly whatever has been loaded into cache)