1. A customer request portal was created
A portal was prepared where the customer could submit bugs, improvements, or feature requests in their own words. This moved requests away from scattered communication channels into a traceable entry point.
Reference Study
Software / Product Development Automation
An automated development flow from customer request to production release
An automation flow developed for collecting bug reports and feature requests via a customer portal, converting them into technical tasks using LLM, passing them to AI-assisted development automation, running code review checks, validating in a test environment, and deploying after customer approval.
2. Requests were converted into technical development items
Descriptions submitted through the portal were analyzed by an LLM. Customer-written requests were converted into technical work items that could be executed by a developer or automation tool.
3. AI-assisted development flow was executed
The generated technical items were passed into an AI-assisted development automation flow. The system was structured to prepare the required code changes based on the request.
4. LLM-assisted code review was added
Prepared changes were passed through a separate code review step. The LLM evaluated the changes with an accept/reject logic and reported the decision together with its reasoning.
5. Automatic transfer to the test environment was enabled
Completed changes were routed to the test environment. In the used infrastructure, deployment was automated; a similar structure could be adapted to Jira, Jenkins, or comparable CI/CD processes in other projects.
6. Runtime and error checks were performed
The test environment was checked to confirm whether the application was running correctly. If compile or runtime errors occurred, the error output was sent back into the development automation to trigger a revision loop.
7. Customer approval workflow was executed
Once the application was running correctly, the relevant development item was presented to the customer for review. This ensured that technical changes were validated by the customer before publishing.
8. Approval or revision loop was established
If the customer approved, the publishing process was started. If not, the revision request was fed back into the automation flow and the process continued in a controlled way.
Key Gains
- Bug and development requests became traceable through a single portal.
- Customer-written requests were converted into technical development items.
- Manual interpretation and handover effort in the development process was reduced.
- Code review was integrated into the automation flow, strengthening quality control.
- Test environment validation, error checks, and revision loops became more systematic.
- Compile/runtime errors could be routed back into the development flow automatically.
- Customer approval became mandatory before publishing.
- The process became adaptable to different CI/CD structures and project management tools.
- A more traceable and repeatable workflow was established instead of a single-developer-dependent process.