Pipeline authoring 13.10 planning issue
Pipeline Authoring Issue Boards
Goals for the milestone:
- Increase adoption for pipeline editor - since the release of the pipeline editor we are seen high adoption, and would like to increase that adoption notably we would like to deliver:
- Branch selector - to support users that are working from a non-default branch
- Empty page - to improve the getting started experience
- Allow users to navigate to the pipeline editor from the yaml file viewer
- Rollout the new pipeline view
- Improve the pipeline editor user experience
- implement popular customer requirements
Additional comments
Deliverable issues
Scope of Work for EngineeringFiller issues (which typically should be picked up if all Deliverable are done or blocked)
Priority | Issue | Category | Notes | Frontend | Backend | Weight |
---|---|---|---|---|---|---|
1 | Downstream pipeline UI is caching and not updating correctly | ~bug | 3 | |||
2 | Show an alert with a link to the feedback issue to existing CI users when Pipeline Editor is released | 2 | ||||
3 | Spike - auto Generate JSON schema | |||||
4 | Support parallel keyword for child pipelines | 3 | ||||
5 | gitlab-org/gitlab#296532 (closed) | |||||
8 | Trigger pipeline if draft is removed |
Scope of Work for Testing
Issue | Investigates/Tests | Due on |
---|---|---|
Scope of Work for UX
Issue | Category | comments |
---|---|---|
Collaborating with Dov on Problem validation: Validating your pipeline | ||
|
||
Create design proposals for UX debt and UI polish issues where necessary | ||
|
||
|
Edited by Nadia Sotnikova