Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
1–10 of 110 posts
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#2While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis.
It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-featured tracker designed for everyone to use.
But, I am curious to hear from someone who has actually used this thing.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#3While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis. It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-…
P.S. The GitHub readme for this project desperately needs a "Why?" (... would anyone use it, ie. what benefits does it offer vs. say Jira?)
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#4While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis. It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-…
I think that is more useful for communities whose members don't have reliable, always-on networks, rather than workflows within companies.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#5While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis. It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-…
All those users are why bug trackers are annoying. I don't care about those fields "those other people" are demanding, why do I need to fill them out. Mean while they don't care about the fields that are critical for me and don't want to fill them out.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#6This is incredibly cool. I love seeing local first software starting to make a comeback. Github is becoming painful to use, even on a fast connection.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#7While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis. It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-…
This is a bug tracker. What you are describing is much closer to a project management tool, just to make the difference clear.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#8While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis. It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-…
This is a bug tracker. What you are describing is much closer to a project management tool, just to make the difference clear.
To some people, engineers without project management doesn't make any sense.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#9While I like the idea of tool consolidation, bug trackers aren't just a tool for the engineers. At most companies I've worked at, the support team, designers, QA team, managers, etc. all use the bug tracker on a daily basis. It sounds like you can "bridge" to somehow show the tracker outside Engineering, but then you're having to do work around the consolidation, and I'd imagine the result won't be as nice as a full-…
This is a bug tracker. What you are describing is much closer to a project management tool, just to make the difference clear.
Those should be tightly integrated, if not the same tool.
Re: Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
#10Might be interesting as a personal cross project todo tracker?