One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified. The folder structure is another aspect that could be enhanced, as all jobs are displayed on a single page without the clear organization seen in Jenkins. Implementing a more structured approach to organizing jobs would improve user experience.

AI could simplify job creation. For example, instead of manually editing pipelines as code, an AI tool could allow users to input variables and automatically generate the required jobs. It would help reduce human errors, such as issues that arise from incorrect edits in large code files.

Jenkins is overtaking the product. The product must enhance user experience. Jenkins has everything in a simple XML format. However, GoCD is complex. Upgrading it to a simpler language would be helpful. The tool must be more user-friendly.

GoCD could cover the authentication aspect. Currently, we are handling an in-house development that needs this. Comprehensive features must be established before transitioning into an enterprise product.

The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us.

I would prefer to streamline the user management process, which would be more convenient for me. It would involve importing users from GitLab and granting them the necessary permissions they require.

1. If the workflows were updated for any reason, such as when environments are created, deleted, or changed, the previous delivery pipelines will be broken. You can't redeploy the old version or propagate new versions to the following environments.
   
2. It would be great to have more flexibility in configuring the initial job. We are using GoCD for the CD process only, so any jobs are triggered by external CI tools, not the GoCD itself. We don't need to configure code repositories or other inputs that GoCD is expecting, so we are forced to create the dummy repository, and the commit history is not relevant to the CD process.
3. It would be great to have more available plug-ins to cover more functionality inside GoCD.
4. The documentation really should be improved by including real examples and more setup cases.

GO statistic and report options.

User management, Documentation, Advanced GUI functionality.