Project

General

Profile

Forums » Open discussion »

Trackers and activities

Added by Ivan Cenov over 13 years ago

Hello,

I have to define trackers and activities in our Redmine. I am a bit confused when trying to distinguish trackers from enumerations activities. What kind of information (values) are appropriate for trackers and what for activities?
Well, we have software, electronics and mechanics development in our company. I suppose, par example, the following trackers are suitable:
  • design
  • service requests
  • feature requests
  • feedback
I think these would be appropriate for the software developments, and for mechanics and electronics as well. Am I right?
What about activities though? These should be specific to particular work. par example:
software:
  • design
  • coding
  • code review
  • QA tests
  • deployment
electronics:
  • design (as for software)
  • PCB design
  • tests without software
  • tests with software

So I am seeking for opinions about these things .... it seems they are not related just to Redmine but for project management at whole...

Ivan


Replies (1)

RE: Trackers and activities - Added by Felix Schäfer over 13 years ago

Tracker is a type of "workflow" you can define, and with which different "roles" (people with certain permissions) can interact.

Example: An "Article" is a good tracker: a new article can be "assigned" to a reporter, who writes the article, which then has to get "edited" by the editor and "corrected" by a linguist, after that it can also get "laid out", "sent to press", and "closed" once it's made it to the final journal. You can define all those steps for the "Article" tracker, and share them with other trackers if you want, define a workflow about those steps and who can advance that workflow.

The activity is a description of what has been done to advance the ticket.

Example: For said article, suppose the reporter does 2 hours internet research, goes to the library for 1 hour, talks to people on the street for 3 hours and does a 30 minutes interview, you could define the activities "internet research", "library research", "field research" and "interview". That might be to specific though, so you could also just define only "research" and "interview", and tell everyone to write in the comment of the activity field what type of research they have done.

Regarding your case: well, it's something that depends on the management requirements and work culture and so on, so in the end your or your enterprise guidelines will better know what you need where :-)

    (1-1/1)