G
G
German Zvonchuk2014-08-29 08:38:02
Work organization
German Zvonchuk, 2014-08-29 08:38:02

How to organize the work of several programmers? Version control, bug tracker, task management?

Good day.
I would be very grateful if you share your vision or experience on the topic of how to CORRECTLY organize the work of several programmers on one project?
How to manage incoming tasks? What are currently the best apps for this? Asana? I would like to be able to see active tasks, lists of tasks made by the project and made by each programmer.
Where to write bugs? if users report them, where is the first place to write information about it? To the bug tracker or to the task management system?
How to work effectively with the version control system?
How to call commits? Fixed, Feature, Bug?

Answer the question

In order to leave comments, you need to log in

6 answer(s)
V
Vit, 2014-08-29
@fornit1917

I like Redmine - there is a task tracker, a bug tracker, and integration with version control systems (including Git).
Regarding "how to work with git" I think there is no silver bullet, but you can familiarize yourself with some popular approaches and choose which one you like best. Google for example according to the words git workflow.

T
Tim, 2014-08-29
@darqsat

I use Git for versions.
For Trello tasks.
I use Jenkins to monitor code and builds.
Time is tracked in the dock in Google Drive.
I do not like big systems with other integration. One will fly and touch everything else.

S
Sergey, 2014-08-29
Protko @Fesor

Correctly, the concept is extensible. There are all sorts of Agile, Scrums, Kanbans, BDD. In a word, you yourself need to decide on the most effective workflow for your team. Depends on the project.
Task management - de facto standard - Jira. For small projects - Asana, Trello, etc. There are also products from JetBrains - YouTrack.
As for the names of the commits, they should clearly show what was actually done. Even if the commit changes one line, you still need to describe what exactly was fixed and why. There are also two approaches: feature-branches and feature-switches. The latter is more difficult to organize, but with this approach, each developer always has the code of each of his colleagues.
Also check out continuous integration, continuous delivery.

D
dmitriy, 2014-08-29
@dmitriylanets

I love products from Atlassian

F
fmbare, 2014-09-04
@fmbare

Has anyone tried axosoft.com?

I
iliyaisd, 2014-09-19
@iliyaisd

I am using Mantis. All tasks are solved. If users report a bug, then IMHO you need to process the incoming request from the user (depending on who is doing this for you - support? or auto-send?) and put it as a task in the same tracker.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question