Allow users to seamlessly create issues based on job logs
Opportunity
In talking to @rasheed we identified a use case where a job has succeeded but where there's a problem in the output of the job. If the job fails we show a "Create issue" button but this doesn't appear when the job succeeds; this action starts the new issue flow and prepopulates the description with a link to the job.
As an engineer using pipelines I need to identify defects in the pipeline so the relevant DevOps team member can track the work to be done.
As an engineer using pipelines I need to identify maintenance or defects in the codebase based on pipeline output and track the work to address the identified items.
Example scenario
Pipeline defects: Unexpected output
The job called an API to return results, but not all expected results were being returned. An issue would be created to pull full results, which might include the call and output from the job run.
Job-identified issues: Test outcomes
The job ran a test which did not fail but resulted in warnings or todos. One or more issues could be created to address the warnings, including the details of the test from the job output. (non-blocking negative test outcome)
The job ran a test which failed, failing the job and pipeline. An issue could be created today using the new issue button, but would not point directly to the test failure.
Solution
Provide mechanisms for users to create issues based on job output with minimal user input required.
Possibilities
- Allow users to select lines in the job output to create an issue for (similar to Changes tab in an MR)
- Automatically identify potential segments of interest, i.e. highlight a to do with a one-click issue creation