3 ms·
I'd want issue state to be tied to branch state. I want an issue to be able to capture that it's fixed in branch A but not branch B, and if I merge A into B, it
by apendleton 8y ago
I'd want issue state to be tied to branch state. I want an issue to be able to capture that it's fixed in branch A but not branch B, and if I merge A into B, it recognizes that it's now fixed in B as well.
Some systems have very rudimentary versions of this: an issue is globally open or globally closed, but gets auto-closed when a commit is merged into one specific branch (master or whatever), but I'd want this to be much more generalized: fixed in a feature branch but still broken in dev and master, then fixed in dev once the feature branch gets merged, then fixed in master once the dev branch gets merged, etc.
- vidanay 8y agoFogbugz/Kiln had a variation of this. You could easily see which branches a particular commit was in and it was tied back to the ticket as well. It didn't influence ticket state, but it was easily cross-referenceable.
- alangibson 8y agoHave you used Fogbugz? If so, what's your opinion of it?
- vidanay 8y agoI loved it! Unfortunately, I was overruled about three years ago and against (quite strong) protesting on my part, we left it for Easy Redmine (strong dislike). I have no idea what it is like anymore since it is no longer under to stewardship of Joel, and it's been quite a while since I used it.
- slantyyz 8y agoFogbugz, now known as Manuscript, is pretty good. It is somewhere between overly simple (Github Issues) and overly complicated (JIRA). I like it way better than JIRA (having said that, I haven't used JIRA in years). If you're a startup, you used to be able to get a two-user account for free -- not sure if they still do it, as Manuscript/Fogbugz got acquired by another company recently.