We've done something like this too. It worked well to keep track of related issues, particularly during regular reviews. It turned out insufficient when we had to plan ahead for ~6-12 months of work on polishing "version 1.0" (~300 existing tickets that needed to be pruned, reprioritized and otherwise rearranged) and building "version 2.0" (proper work-breakdown task of a complex project).
Our PM tried to handle this challenge for a while, by writing scripts against GitLab API. This eventually turned out insufficient, so the PM, myself and another coworker set out to find a project management tool that actually does project management. It's after extensive discussions and search that we figured out none of the well-known work tracking products in software development fit the bill.
Best easily-accessible options we've found were: MS Project (if you're on Windows, which we weren't), Jira (if you hire a person full-time just to manage it) and YouTrack from JetBrains (if you hire a person full-time just to script it). There are other options in the corporate PM space, but we didn't get to explore those as a startup (and eventually we've all left the company).
Our PM tried to handle this challenge for a while, by writing scripts against GitLab API. This eventually turned out insufficient, so the PM, myself and another coworker set out to find a project management tool that actually does project management. It's after extensive discussions and search that we figured out none of the well-known work tracking products in software development fit the bill.
Best easily-accessible options we've found were: MS Project (if you're on Windows, which we weren't), Jira (if you hire a person full-time just to manage it) and YouTrack from JetBrains (if you hire a person full-time just to script it). There are other options in the corporate PM space, but we didn't get to explore those as a startup (and eventually we've all left the company).