Tightly Integrate Git into Your Project Management Workflow

robiulroky

You need to be able to reproduce the bug, because it’s really hard to fix a bug you can’t see in action. Second, you have to make sure the bug is, in fact, a bug or whether the user expected something your software doesn’t provide.

Here’s another way of putting it:


And you can’t fob off the person reporting the bug with the classic line: “It’s not a bug. It’s a feature!” if you don’t know what the person expected instead.

Using an issue tracker such as Redmine means Country Email List you have a standardized way of receiving this information.

There’s one way you can make sure a task never gets done: vaguely suggested that the team should do something about it. Unless it’s assigned to one “owner”, it just won’t get done.

Issue trackers force you to assign an issue to, well, one person at any given time, so you always know who currently owns a bug or task. At the same time, issues go through a workflow of different statuses such as “In Progress”, “QA/Testing” or “Ready for Deployment”.



Most trackers will give you reports based on the current status of an issue, so you can see the current volume of work in progress and how much remains to be done. You can even create burndown charts, which are popularized in agile methodologies.

As we mentioned above, using git in your WordPress development process will make your life a whole lot easier when things go wrong. Git gives you a rewind button on your code, and you can create multiple, parallel versions of your site.