Sprint branches are an excellent way to manage API changes during development. After using them in my team for several months, I’ve identified a few areas for improvement:
-
Search in sprint branch selection dropdown - In my project there are 30+ sprint branches (as we are using sprint branches for each feature) and find required branch without search is not convenient
-
Branch statuses - Currently there are only two statuses: “Active” and “Archived” branch, but lifecycle of branches can include additional statuses: “merged”, “verified”, “conflicted”, etc (this can be implemented via tags for branches)
-
Shared documentation is not available after archiving of sprint branch - We create separate documentation for every sprint branch and link to it in development tickets, so we can’t archive a branch until the feature is fully implemented and tested.
-
Endpoint references in other branches - When the same endpoint is changed in multiple branches, it’s hard to know which version is latest until one is merged into main, causing merge conflicts. Allowing a branch to pull changes from another branch—not just main—would reduce conflicts.
-
Export/Import in sprint branch - There’s no way to export a sprint branch (e.g., to HTML docs) or import one (e.g., as a Swagger or Postman collection). Adding this capability would greatly help collaboration.