Multi Project Action & Testing Validation
Problem Statement
We think that customers who have multiple projects that make up a single customer facing app have problems validating integration tests and usability without working outside of GitLab. This reduces the time it takes to validate changes and deploy working features.
We also believe these same users are having challenges managing release artifacts when shared across many repos. We will use this opportunity to evaluate both release artifacts, environments, and testing across projects.
Reach
This is a problem primarily for Sasha who wants to validate that changes to an API don't break the front end that's in a different group level project.
This problem will also impact anyone responsible for a collection of interrelated code bases in different repos
We think the number of customers who are impacted by this is at least as large as the number utilizing multi-project pipelines.
3.0, significant amount of users are using multiple repos within their projects.
Impact
We believe the impact of solving this problem would be High in enabling Sasha to more quickly validate how a change has impacted the overall project.
2.0
Confidence
We have Low confidence that this is an issue today due to low/no participation in the implementation issues.
50%
Effort
We think that this solution is a 3.0 (PM and Designer .5 month each, engineer 2.0 months)