Hacker News new | past | comments | ask | show | jobs | submit login

We're planning a migration from Atlassian suite to the Gitlab ecosystem, but one item that I can't seem to replicate is the issue/ ticket workflow of a JIRA ticket. We have a semi-involved workflow that covers most of the software development lifecycle: initial requirements gathering, approvals, coding development, code reviews, UAT approvals, prod deployment approvals etc.

How do you handle this sort of thing with just Git(hub|lab) issues?




Scoped Labels (extended Kanban basically) and different boards for planning and development is our approach in gitlab




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: