Redmine for IT Management: Practical Experience Extensive Implementation OpenSource Systems

Small prehistory. As you know, automation always starts with something "cheerful". Automate yourself or your management we start not from a good life. This usually happens because the organization grow up, it becomes difficult to navigate in a large amount of incoming and available information. So our organization at a certain point began to grow rapidly, so we needed very quickly from chaos to do something structured, useful and convenient.

What does chaos mean in our systems? This means that non-ordered requests that are not subject to analytics and structuring requests come from users, and there is no project management as such. Inquiries are freezing somewhere in the mail, in Word, in the heads of analysts, programmers, department managers - depending on which structure is used in the organization.

We decided to remove your chaos using Redmine software. Immediately make a reservation that we will not speak about the methodology. We will talk exactly about the possibilities of Redmine, about how we apply it. Each company has its own nuances, do not take us to us, do not take others. Make your analysis, act as you think correct and necessary for you. Do not be afraid of errors, because on mistakes we learn.

From chaos, which we had, we try to move to order. Now we are in the middle of this way. Of course, not everything was and will be cloudless and smooth, but we are very trying.

Inside our company, we allocated three main problems:

  • First, we needed a system for tracking errors, incidents and incoming requests, i.e. We needed to automate BUG Tracker;
  • Secondly, we wanted to somehow allocate project management. Not fully monitored by automation, which implies the use of methodologies, and to the extent necessary to be made at the stage of development and with some kind of future. Next, you will see how we use redmine for this, and where we are going to develop it further;
  • Thirdly, we allocated the IT services control unit (ITSM) into a separate system, however, also not in full. Our department provides different IT services that need to be managed.

Additionally, we allocated our private problems:

  • This, I repeat, diverse IT services, because programmers live their lives, system administrators, there are still an Internet marketing department and others;
  • Each has its own structure and their wishes for managing the department. In all departments, different methodologies, approaches, managers and psychotypes - it imposes its imprint to the choice of the system. But it is necessary to move with all at the same time, and, reaching one goal - a certain order in the organization, accessibility of information and forecastement;
  • In addition, there is another KPI, which in all is calculated by different indicators;
  • To develop further, we need an additional analysis of the incoming information, what is happening in the departments and how it is reflected in the organization as a whole;
  • We must control the internal budgets, in the framework of which we enter or, most often, do not enter. They also need to somehow analyze and manage them. It is better to do all this in a single system - in particular, it is convenient for the manual.

Thus, we allocated three systems that I would like to combine into one.

For each of these systems there is a separate specialized software. It is all the well-known automation products that have their own pros and cons, so if you choose the system for yourself, consider everything.

Not all products are listed on the slide, there are much more of them, and not only in the Russian market, but also on Western. But for us, one of the requirements was a Russian-speaking interface, because this product would be used not only programmers and system administrators who are more or less understandable English, but also ordinary users.

Where to go? Many products. Requirements for them from various departments and controls are different. We will choose.

As a result of the analysis and choice, as well as with the filing of Alexei Lustin, a redmine product that covers a certain area came to us. Let's find out what kind of region it covers?

It completely covers the Bug Tracker, which we wanted to run in the company. This is the centralization of receipt of applications from users and customers of any level. It was the most basic pain point, which was necessary to quickly automate. I think that everyone has this problem, because, as I have already said, the information comes in disordered and settles in different places - in the mail, in Word, in Excel or heads. Such information is not subject to analyzing and obtaining conclusions and results. As a result, it turns out that:

    • The information component of the knowledge base, which can be analyzed and understand what to do next is absent. This slows down the reaction rate and affects the uninterruptedness and quality of work, from which the profit directly depends;
    • Increases the "dive" time of new employees to work with corporate systems;
    • Failure tolerance is also each of its own - someone without a working system can not live two minutes. Therefore, Bug Tracker plays a big role, and at that time the problematics got very acute.

Redmine project management covers half, because this product does not specialize in managing projects, but there is a certain block, which helps in this. Unfortunately, this is not an ideal product, but at that time he covered the requirements that we set up to the system.

And a very small ITSM block is covered. The Redmine system is not intended to manage IT services, so there are some flaws in conducting and structuring data. We have come out of this situation by selecting your version of the ITSM system.

So, our choice is redmine. It is pretty customized, scalable, flexible and with convenient settings.

Why Redmine?

  • This is the sweet word "freebie". Redmine is free, though, with the reservation, that there are paid plugins that you choose for yourself. In any case, you have some kind of cost forecasting, because if you bought a plugin and do not change the Redmine platform, then for some time this plugin can be used without additional investments. And if you, for example, you need to update it, then you pay for this update and use it further. The Redmine Platform Update occurs once or two per year, and updated or not - this is your desire.
  • REDMINE has an intuitive interface. We have implemented Redmine not only as a product for IT management, but also as a product where applications from users are received for various departments. For example, a separate branch is highlighted for applications of the administrative and economic department.
  • It is possible to control priorities in various analytical forms, including individually according to tasks.
  • Management time and resources. I think this is the main unit for the head. It allows you to understand how much the department is loaded, with what tasks what costs are related and how to classify costs, but about it below.
  • Analytics and reports in RedMine are weakly expressed, but there is an extensive API. You can take data from the API database, unload them to your system and get any reports.
  • Flexible settings, customization and automation of manual operations with plugins.
  • Integration with Git is one of the important indicators. The repository of our database is connected to the Gitlab, and in any REDMINE task you can see logs (related editions): who, when and what has changed according to this task, with the transition to Gitlab.

For information: Git is a distributed version control system. It tracks, fixes and stores information (versions) about changes in any files and directories, and also monitors data integrity. In our case, we are talking about the source code 1C.

This is what the list of related editions looks like:

  • Task management and error tracking. This is a standard Bug Tracker, which we will use.
  • Management of incidents, projects, budgets. All budget formation is carried out in their own way. I will show how we automated it at yourself, and you can then try to automate the management of the budget in yourself - I think it will be easy, because there are labor in Redmine, and you can also transfer them to money too.
  • Wiki in redmine is not very well implemented, so it is better to use another product for the purpose of creating a knowledge base and collaboration. For myself, we chose the Confluence system from Atlassian, which is one of the most common and easy-to-work. You can also consider systems: Dokuwiki, MediaWiki and others.

What is Redmine under the hood?

  • Redmine very quickly and just unfolds.
  • It works on most OS.
  • The platform on which it is implemented is Ruby On Rails. If you want to customize redmine under ourselves, you need to have a competency on Ruby On Rails, otherwise it will not be very convenient, because Not everything can be made ready-made plugins.
  • Support for various DBMS speaks for itself.
  • With RSS or E-mail, you can organize alerts on any events.
  • AD authentication is available.
  • Integration with SCM version control systems (SVN, CVS, GIT, Mercurial, Bazaar and Darcs).

Meet redmine

You can download redmine, install it on your computer and "experiment." Or use the cloud server, and "in one click" to put yourself a pre-installed version of Redmine, which is usually included in the hosting service.

Examples of installation for any system, including the use of cloud service, can be found on the Internet. Official instruction on the link:

So looks like a list of tasks in Redmine.

There is a standard and several additional interfaces. True, when changing interfaces, some functions can stop working, because Custom interfaces do not take into account the plugins with which you will work - after all, this is an Open Source product. But this does not prevent him from being a convenient tool even using the standard interface.

Administration is allocated in a separate and quite understandable structure.

The list of modules connected to your redmine, you can always look and analyze in the appropriate administration section.

We do not have a "clean" redmine, because There are about 35 plugins. We bought a few of them.

Information on plugins can be found in the search engine by keywords "plugins for Redmine". For example, there are two sites where you can download or purchase good plugins to start working with RedMine:

All plugins are Russified, you can buy and use. The main thing is to choose comfortable. Just pay attention to which version of redmine supports the plugin, because if the supported version does not match yours, there is a chance that the plugin will not work.

A little about the automation of our needs

Structure "Projects"

We use Redmine not according to standard leadership. As an example, within the framework of the system, the concept of "project" is a separate branch in the hierarchy of the structure. We use the "projects" tree as a classification of levels. At the top level there is a executive department, he is subject to served departments, then the systems, subsystems and services are followed.

Part of the tree look like this:

The system administration department also uses its approach to the hierarchy of projects. The work is built on the basis of the classification of services provided - it helped solve the problem with the service control. Therefore, in the ITSM branch, project hierarchy is a business service catalog. For convenience, they are numbered.

Admission of applications in Redmine

According to the example, I will tell you how we organized the receipt of applications in Redmine.

Our department is divided into 3 groups:

  • Development team;
  • A group of analytics and accompaniment - here includes employees who produce the level of "two and a half" support. They advise, analyze the problem, if necessary, "read" code can write requests for data analysis, as well as correct errors in the code. As a result, we manage to exclude the distraction of programmers from small problems, as well as with the help of analysts, we separate programmers from customers and back, because Everything, probably, faced the problems of relationships between them.
  • And group of administrators of database 1c.

So, the receipt of applications in Redmine with us is carried out through the writing of the usual letter on the highlighted mailbox. For the organization of individual mailboxes, we in each department and in each group allocated their "projects" structure, for example:

For each of the projects, we in the HelpDesk plugin configured your mailbox. The screenshot shows the settings of the HelpDesk plugin for one of the projects:

Letters entering the mailbox attached to the "project" fall into our system as applications with a view of the "user request". All this leads to a decrease in labor cost employees to the primary classification of incoming requests. (Example in the screenshot: 1.2 Administrators 1C, 1.4 Ticket Confluence, 1.5 Support for Yurait DPP)

If it is impossible to produce such a selection of the structure, then it is quite possible to select one mailbox, and in the tree to create subordinate branches, where the applications will be distributed to the first support line after the primary classification (sample screenshot: 1.3 user support).

As a result, the application passes the cycle:

  • First, the primary automatic entry in the project is happening;
  • Then the analyst distributes the application, i.e. classifies, categorizes and prioritizes it;
  • After that, the analyst transfers the application to the desired branch.

In the application there are certain classification fields, some of them pretentically, and the part is added by us. In accordance with this, the primary needed filling using parameters is performed:

  • Priority;
  • Category;
  • Customer Department;
  • Castom fields of various types.

Those. If an incident occurs, you can be sure that it will not pass unnoticed.

An example of received applications and fields used:

Settings "Project"

Inside the "project" there may be several types of trackers. Here, for example, often used trackers:

  • User request;
  • A task;
  • Error;
  • Sentence;
  • Business project;
  • Program of business projects, etc.

Trackers may be an unlimited number - they can be added manually. Each tracker is flexibly configured.

In the "Project" settings, we can specify which trackers in it are used, as well as which custom fields can be connected.

Also, the necessary modules and other settings are also connected to each branch. You can find this in standard Redmine documentation.

After connecting the modules, you do not need to produce any complex manipulations, you just need to save the list of the modules of the current "project" and they will appear in the form of tabs when you go to which you can make the necessary settings.

In addition, the REDMINE is very flexibly configured to access the rights of different levels both to the "project" and on separate related functions, as well as the availability of each field.

On the Overview page "Project" you can see all kinds of trackers and statistics on them. And also, when "falling down" into the tracker, you see subordinates of this "project" of Issues - let's call them "cards".

Business projects

I repeat a little. Since in the concepts of Redmine "Project" - this is a branch of the structure of the structure, then for the maintenance of real projects, we allocated a separate branch with the "Business Project" and "Business Project Program" trackers. This allows us to keep status reports on our business projects and form costs in terms of distribution bases.

The structure of this branch is also divided into spellings on the specifics: department, customer, system, subsystem.

Because Our management company, departments centrally accompany all companies included in WiseAdvice GK. In this regard, we are conducting projects both individually for any company and joint for several companies. As a result, for each project and the task is to budgeting and writing off the cost of departments.

In a business project card, you can also configure the necessary fields. An example of the fields we use:

  • Base distribution / cost recipient;
  • Bonus for the project;
  • Evaluation of labor costs;
  • Start / completion dates planned;
  • Day status report and others.

All tasks that are created within the project are subordinate to the main card of the business project.

The status report is handed over to customers at least once a week. The whole story accumulates in the card and is sent to interested parties.

The customer and other stakeholders can see the following information on the business project at any time:

  • Project status;
  • Estimated labor costs;
  • Actual labor costs are currently in the context of execution and employees;
  • Project readiness;
  • Formulation of a business project;
  • The entire history of correspondence;
  • The planning date of the project began, if he was postponed due to prioritization;
  • The planned date of completion of the project.

Actual labor costs are collected from the subordinate business project tasks in time spent by the staff of the departments.

Based on the formed tasks, you can build a Ganta diagram, but only in an informative version. Additionally, it is impossible to use it and interactively.

When working with the schedule of calendar planning, you can use graphic reports. For example:

We use task boards to distribute tasks within weekly planning.

All this is implemented through plug-ins, which include the possibility of conducting Agile or Kanban boards.

As an example:

Taking into account the characteristics of the plugin, it turns out like the Kanban board. It can be interactively overpowered by the packets - both between the status and between the performers. On three interfaces were checked - it works only on two. The standard interface is exactly running. Very convenient to display on a large TV / screen for planets / rallies.

Also, planning can be carried out using versions and then convert versions into releases.

As the effectiveness of the work of the department, we form reports in the context of the costs of distribution of costs and actual labor costs of departments.

Standard labor reports can be outlined:

We use the inclination of the report on labor costs:

  • Cost Distribution Database - Our Custom Field;
  • Cost Recipient - Our Castom Field;
  • The user is a standard field.

The formation can occur in the context of periods:

For our budgeting, we use only the "month". Report Example:

The screenshot presents an example with actual labor costs in the context of the distribution base for August.

In addition, you can form a detailed report for each declared time value. If necessary, all reports are converted to CSV, so further analysis can be made in Excel.

And, of course, as the true 1C-nickname, we can write unloading information from Redmine in 1C to form your report in 1C with the necessary groups and information.

An example of one of the cost reports:

A little more about Redmine functions

Of the additional useful functions in RedMine, I would like to highlight:

  • Authentication mode - either by AD, or by login and password;

  • Alerts system. The user will be notified of changes in the task. You can configure email alerts and RSS;

  • Combining users to groups. With this tool, you can form in the Redmine hierarchical structure of the enterprise. There are plugins on integration with the accounting system and cloning its structure in groups;
  • Role model right, with multiple multi-level setup;

  • Setting the Workflow (life cycle) of each tracker for each role;

  • The presence of integration plugins with MS Outlook. For example, a fairly convenient plugin with many functions, such as creating an application in Redmine directly from the letter, commenting, tracking, etc.; Official site:

https://ru.a.ausoftware.com/

  • There are also plugins to integrate with instant messaging systems, such as Telegram, and SMS gateways. On any communication channel, you can send alerts, such as incidents, monitoring information, etc.;
  • If there is a competence, it is possible to make any plugins themselves.

Questions - Answers:

Question from the hall : Suppose we have provided access to the customer, and we have a certain list of supported services for it. For example, as in your example, there are services of sysadminov and coder services. With some kind of customer, we work on both types of services, and with some kind of only one type. Is it possible at the level of rights to limit what type of service is available to the customer?

Answer: This varies only by a separate branch allocated under the customer - "project", where tasks for selected services can be created individually for this customer. Or you will have to provide access to all tasks in the branch - "Project" support for this service. Standard ability to limit the rights on the sign of the service and the customer in the "project" in Redmine "out of the box" is not. You can look for such a plugin or write it yourself. We have no such complex structure, but there are tasks that should be available only to individual major units, so they have been created for them.

Question from the hall: It turns out that each customer is a "project". And inside one "project" can the subprojects do?

Answer: Yes, as much as you like. We, for example, highlighting the greek to separate customer departments, and give it there to be accessed by the key employees so that they do not see the entire HelpDesk associated with the customer, and the whole structure, because She is quite big. Redmine flexible in the settings, but, unfortunately, and in its flexibility there are limitations that are delivering some inconvenience. Of course, there are more convenient highly specialized solutions, but they are paid.

Question from the hall : And the labor costs made on each status are summed up? For example, on the status of "in the work" I set the labor costs 0.3, and then on the status of the "analysis" I set some more labor costs.

Answer : Major costs go in general for the task. It is impossible to classify labor costs according to statuses, but labor costs have a field "Activities", the essence of which can reflect the process in which you write off time. It is also editable. When writing through labor costs, an employee chooses a type of activity that is fixed. Next, using reports, you can withdraw the time in the context of the processes.

Without an indication of the type of activity, the report can only be formed by the total time in the context of the employee + day.

Summary analytical data can be viewed by reports. Directly in the task only the cost of the current task is visible.

Question from the hall : It turns out that I have the first line of technical support and the second line of technical support. Each of them spends on the same task in the same status "in the work" of a certain time. Accordingly, how can I define actual labor costs per person on the task on the first line, on the second line, on the third line?

Answer : I repeat, the costs go in general on the task, but if one person spent so many time, and then another person spent time - this is reflected here. Partially the answer was given under the previous question. Then you can see which of them how much has spent, but only in this version. There are no separate costs only if you add custom fields to write off labor costs or use user groupings and further form analytical reports.

Question from the hall : How is the user interaction organized? Via e-mail?

Answer : Sending goes to an e-mail standard letter or written by the user, or an automatic redmine fold, if it is an observer for this task. Also, if he is a redmine user, then the top panel displays how many tasks is appointed how many new and how many changes. I now see that I have 20 tasks, one of which is new and one altered. From the user side - only e-mail.

As described above, when connecting plugins, you can unilaterally notify users using instant messaging systems.

Question from the hall : Is there a web interface for submission of applications?

Answer : Not. Redmine works on smartphones and tablets, i.e. has an adapted interface. But applications can be submitted either via e-mail, or give access to the user directly into the system, limiting it in rights only to create. As an additional feature, you can put a plugin in Outlook to create tasks in Redmine.

Currently, there is a Tracker Hider plugin, with which you can limit access to trackers in the context of users or roles.

Example: Any user with the "Observer" role in the "Project" is available only cards with the "User Request" tracker.

Question from the hall : And the functionality of working with e-mail is one of the box or from plugins?

Answer :Yes, it is "out of the box." With the help of plugins, it simply acquires additional amenities and settings.

Question from the hall : And is it possible to configure that the notification of the customer, whom we entered into the system, went only on a certain status. Why should he watch our internal ten stages if he needed notice to go only when the task is completed?

Answer :We solved this situation as follows.

1. First of all, we disabled for users-customers standard redmine notifications in user settings. This setting is global for all redmine for the current user.

2. Further, for the required branch ("project") connected the possibility of sending letters.

3. Analyst, or RP-Shnik can send an email using a standard mechanism: by pressing the "Send a Note" sign in the Card Edit mode. If necessary, you can specify additional recipients.

4. The sender can write any text and add the necessary attachments. Or use previously configured patterns.

 

To do this, the finished pattern is selected, substituted into the letter of the letter and it remains only to fill, if necessary, additional information.

After that, you need to click the "Accept" button, then the comment will be saved and the letter will be sent. The customer will receive a notification in the form of a regular letter.

This is a standard mechanism, we didn't touch anything. Templates for each project are customized individual. This is a fairly significant simplification of the analyst consultant, because every time you write the same text - it is laborious.

Hide any text from the Customer, if it has access to him directly to task cards, it is possible only through the use of a "private" comment or by turning off the access to this type of comments.

The second option is to use an additional plugin, because By default, there is no such setting.

Question from the hall: Is it possible to bind the counterparty to the task received? For example, I have a phone call with PBX, where the counterparty number is scored, and Redmine takes the arrived number from PBX, creates a task and taught it to the counterparty. Have you solved the task of the hierarchy of counterparties?

Answer: No, we did not integrate the redmine with IP telephony, it was not our goal. The idea is good, but in our specifics it is not needed. On the Internet, you can find the REDMINE integration with Asterisk.

Question from the hall :We have a question not on IP telephony, but on the hierarchy of counterparties. We want managers to see the same hierarchy of counterparties in Redmine as 1c.

Answer : No, the contact structure is flat. The only thing we added is a link to the Department. Maximum that we use is collecting contacts by departments, we make Bug Tracker for domestic services, and not for external customers. In Redmine itself, it is impossible to organize a hierarchy of counterparties, but you can associate units in Redmine and 1C, and form this report out of 1C.

Question from the hall : And where is the depth of SCRUM? We have conditionally sprint - 7 calendar days (5 business days). Where can I see what is the iteration of the sprint? What is the calendar week, what is the sprint number?

Answer : Scrum depth can be controlled by versions. There is a feature of versions.

For this, there is a special section "Operational Plan" (or "Version" depending on the interface).

I have three versions for example.

 

Each version may have its own name, status and limited to the completion date.

For each version, task lists are visible if they are presented, as well as the number of unfinished.

For visualization, you can form diagrams

Versions can be grouped, break tasks, you can build boards according to them. You can transfer tasks between sprints - such an opportunity is in the version "Planning Versions".

In fact, Redmine can be a tool for organizing work on scope or canbana. However, it is necessary to take into account that sometimes there is not enough sorting and other little things for convenience. Perhaps there are plugins that support it. In the required volume of current functionality, there is enough. Here you can make the assignment of tasks, moving between sprints, see that you did not have time to do for the planned time, etc.

Question from the hall : How do we take into account the tasks that were not fulfilled in the current sprint? Should I see it in status? Or they somehow automatically, I will show it that they are now needed to book a new version?

Answer : You can select the task according to the version. For example, to look at the "Operational Plan", for how many percent it is completed and how fulfilled. Those. How many tasks are closed from the sprint and how much is not yet closed - it will be written here. When you click on the corresponding item, a list of tasks that have not closed are open. Further, as I said, they can be analyzed and transferred to another sprint.

You can also form boards with tasks, according to the same versions and in the context of statuses.

And of course use the standard list of tasks with the necessary selection, which can be saved and used in permanent operation.

Question from the hall : How can you transfer the task to another sprint - I have to open a list of tasks on one tab, Kanban-board on another and transfer?

Answer: Could be so. But it is more convenient to use the Version Planning Tool. Choose from the list of unassigned tasks or unfinished tasks of a specific version of the desired task and throw it into the next version of the mouse - show that we take this task in the sprint.

Question from the hall: And how can you give all the unlocked tasks? Maybe three or four versions back I had some kind of important task there. I recorded it, she hangs there. How can I not lose her so that she was constantly hung with me? As far as I understood, now you can see only unallocated tasks or tasks from the selected sprint. And how to see all the unlocked tasks with a cumulative result, to understand, take them into the current sprint or not to take?

Answer: This can be implemented using filtering in tasks. You can make selection settings in the status "Open" with the necessary parameters and save.

 

For example, we can consider the setting, which is called "tasks for closing". There are tasks with the status "Solved", which were implemented by our department and transferred to the Customer to production operation, but no feedback from the Customer has not yet received. Those. This is a pool of tasks that need to be checked to clarify the results of production exploitation and close. For example, you can change in the status filter value "corresponds" and the sign "new". As a result, new tasks will be displayed that are not yet taken to work. You can vary the status, priorities, categories, any values ​​of both standard and custom fields.

For example, you can add a special user field to the filter. This is a convenient tool, very simple. For the project, for the task, for contact.

New field - indicate the type of object, where we add, most often used "tasks".

We indicate the field format - options that are covered somewhere 90% of the needs.

Indicate the name, how will the roles are available.

We indicate for which projects for which trackers is applied.

Question from the hall : And custom fields can be made mandatory?

Answer : Of course, by analogy with additional details in 1C.

Mandatory fields are marked with a red asterisk to the right of the name.

Question from the hall : And how did you have reports on performed work? In the same task goes to another user - there is a task initiator and there is a performer.

Answer: That's right, if the field is changing - to whom it is assigned, then in the report it returns the final value.

Let me tell you how we all arranged. Partially repeat.

  • The most important tracker for Service Desk is a "user request", with which the mail is disassembled automatically and letters turn into "user requests". If the user sent a response letter to notification from Redmine or sent a clarifying letter with the same topic, then on the topic or ID in the topic automatically attaches text from such a letter to an existing query - a classic gluing function is used.
  • Next - when, for example, a request for counseling in the KIS department came, analyst consultants disassemble the application and produce its primary classification. Determine that this is an incident, error or task. It can even be an idea to a new project. Accordingly, this is also part of the Service Desk. After the classification, all the "user requests" are distributed to the subprojects of the ITASK branch, where further work is already being done with them.
  • If this work degenerates the task for the developer, then on the basis of the user's request, the associated subordinate "task" is created. That is, the "user request" tracker lives in itself, and the Task Trackor is also separate. We are talking about small modifications and error corrections that we have a separate stream - they appear from "user requests".
  • If the task concerns a particular business project and the developer did not do it on the basis of the "user request", it is tied to the subordinate business project to the blocks of the functionality of Kisa, so that later the task could be seen - on which block and in connection with which we did - It was "user request" or a business project.
  • Separately lives the tracker "Business Project", with which we communicate with the business - not with users on request and minor refinement, and already with real projects that carry business value. In the "Business Project" as subordinate tasks can also be their subtasks and even packs of tasks - large, with subordination and connections. This is such a mini-proof. All these subtasks are again tied to the blocks of the functionality of Kis.
  • It does not matter where the task came from - from service Desca or from a business project. But we all tie them to the blocks of functionality.

Based on the above, I repeat, we can see labor costs in the context:

  • Blocks of functionality of kisa;
  • Projects;
  • Performers;
  • Communication "Request - Tasks / Business Project - Subordinate Trackers".

The screenshot presents an example with actual labor costs in the context of projects for August a month. Employees must distribute their actually spent time on the tasks they performed. This is called Time Sheet. We have daily developers enter the special records of "work reports" and distribute their time - the fact of labor is formed. Thus, we at least approximately, in fact, manage the budget of the project.

Our projects have a preliminary work plan. And in each project we see, we exceeded it or not. Redmine automatically summarizes the width of all tasks subordinate to the project. Accordingly, we know that this project is allocated 700 hours. We see the fact - 617 hours have been worked out. This is one of the project management elements.

The process of activity of the system of incidents can be represented as follows:

  • The analyst consultant conducts an analysis of the requested request, if necessary, forms a development task;
  • The developer implements the task and returns its analytics consultant to verify and further communication;
  • The analyst consultant is already communicating at the request of the user with a description of the results;
  • If everything is in order, the analyst closes the task - the developer is forbidden to close the tasks.

In more major tasks, incl. Design, the process is built more expanded:

And, of course, all changes fall into the working base through the release of the release.

If you submit it in a more convenient option, then we have our own "eight".

Those., Really many tasks transitions between responsible, but it is not critical to us. We evaluate labor costs in the context of employees, the costs of distribution of costs, customers and, in rare cases, in the form of activities. All this has already been stated earlier.

Question from the hall : Is it possible to get information about what tasks did a specific developer fulfill?

Answer : There is. There is a "Work Report" tool for which you can see what an employee to which task how much time and what day I spent.

Or it can be viewed by a standard report "labor costs" - it can also be formed in the context of users with decoding.

Question from the hall : And how to track your labor costs?

Answer: An employee also controls their work through the "Working Report". And the fixation of labor costs in the task is done manually - either directly in the task or in the "Working Report". There are plugins that allow you to keep track of time. For example, the Redmine Issue Timer plugin looks like this:

When you start working on a task, an employee clicks the "Play" button, and at the end - the "PAUSE" button. When maintaining the task, labor costs are fixed in it.

Question from the hall : Question to the time management and resources is postfactum management, registering already happened, when I look at how my employees have been loaded, or is it possible to plan? When I look that tomorrow my programmer must take the task of this, and the day after tomorrow this. And I understand that, conventionally speaking, it is a powerful programmer, and he can have any reports without problems for two, three per day to rivet, and I can put a queue of tasks for a week.

Answer :The ability to plan is, but it is not perfect - free product makes your nuances. There is a field of "scheduled time", it is possible to set your custom field if you lack a standard field by planning time - how many hours of hours it will spend. It is possible to specify the planned time and then compare the planned and actual time. And, of course, you can use the standard Story Points field for poker planning.

Question from the hall : You said that Wiki in redmine uncomfortable.

Answer :Wiki in Redmine looks unfriendly.

 

To format articles and tasks, the marking language MarkDown is used. Formatting is not "on the fly", but indicating the marking symbols.

The search is - according to the word inside the text and the headlines. If you enter "Exchange" in the search, it will give both themes and trackers. There is a selection by type of tracker.

The table of contents is not the main page and when entering Wiki is displayed simply a list of created articles.

The table of contents is as follows:

And, of course, Wiki in Redmine is intended for storing articles only. It cannot be used to collaborate.

The history of the change of articles is conducted and can be found when, who and which change produced.

Question from the hall : How does Wiki filling?

Answer : Our process is constructed as follows. Analysis of Service Desk is performed with a certain periodicity over the past period. With the help of an initial classification that was made by analysts when requesting a request, we are trying to summarize the themes and identify the most problematic zones. Next - we introduce self-service, i.e. Documenting how the user himself can solve its problem or the question. In addition, during the current work, the analyst can create articles at its discretion, in the event of a need, without waiting for the overall analysis. Also preparation of the Wiki-instruction is within the framework of developed business projects or specially dedicated documenting projects. This is not a confluence, not collaboration. This is from top to bottom with administrative methods. Users do not participate in this.

Question from the hall : One of the colleagues use a very interesting system. I really liked it, I want to implement it myself. The first line of technical support is always obliged to close the task from Wiki. And if she does not find an article in Wiki, she addresses the second line of technical support. And already the second line creates an article that must be mounted for a task.

Answer :We, too, try so, but we act iteratively - setels, analyzed, made a number of events. But it takes months. Then again - sat down, analyzed, allocated the necessary blocks, made a number of events.

Question from the hall : Not very clear - how is the GIT integration with Redmine?

Answer :When you save changes to the 1C storage (when calculating), the description indicates the task number with the "#" tag, for example "# 74516". Thus, we get through accounting - we can see which committees in the Git storage is tied to the task. It was important for us that this is a desktop solution so that we can conveniently manage them, and, if necessary, go to another solution, because all the same needs grow, and not all redmine needs can be covered. Therefore, I apologize again - if you choose a product, first analyze that you want to automate and which blocks "cover".

Question from the hall : Did you use the mobile application from Redmine?

Answer :Mobile application is, but it is not quite comfortable. In our organization, there is no need for it. We mainly work on a landline computer or laptop. You can also use plugins with information capabilities - for example, using SMS or by Telegram.

Question from the hall : You said that you unload the repository in the Git, and what do you see there in the Git?

Answer : In Commut Git there is a link to the task. From the Committee we open the task itself. And from the problem, we can also open a commote associated with it. To each project, no matter what a hierarchy is, you can connect your repository. Of course, the integration with GIT is administered not completely through the web interface. Handles there still have to climb, but quickly and simple.

What we have in the end:

Based on the above, we will summarize the brief results.

Pros:

  • Redmine - OpenSource-Product with a large and active community;
  • It is projected on costs, inexpensive, flexible, customized, easily integrable and scalable;
  • Completely covers Bug Tracker, half - project management, quite a bit - ITSM;
  • Has integration with GIT;
  • Castomizes "on the fly";
  • It has a fairly wide range of plugins. In addition, it is easy to find specialists to automate their processes;
  • Convenient accounting of actual labor costs. The possibility of planning labor costs and budgets.

Minuses:

  • Uncomfortable wiki;
  • If you need to automate your processes and in the absence of competence on Ruby On Rails, only the use of plugins or search for third-party developers is possible;
  • A small number of analytical reports;
  • Not always a "friendly" interface;
  • Uncomfortable mass classifiers that would like to store in the form of a hierarchy.

In the process of using the Redmine product, we have done a large amount of work on the analysis, systematization and automation of our activities and a decrease in chaos in our structures. They made a change and optimization of processes both within the departments and in business processes of the whole organization. Optimized and improved control, analytical and managerial functions in the work of departments and on design activities.

Further step that we have taken is to highlight the knowledge base in a more convenient Confluence system, because The possibility of working together is one of the main mechanisms in the development of organizations, allows you to quickly produce communications, reduce the time to transfer information, reduce the number of errors and time to solve incidents.

In the RedMine part there will be additional steps to build clearer and controlled business processes.

In general, choose the tool, and let your chaos be left unnoticed.

****************

This article is written on the results of the report read at the InfoStart Event 2017 Community conference. More articles can be found here.

In 2020 we invite everyone to take part in 7 regional allocations, as well as the anniversary InfoStart Event 2020 in Moscow.

Select event.

Redmine. - Open server web application for project management and tasks (including error tracking). Redmine is written in Ruby and is an application based on the well-known web framework Ruby On Rails. Distributed according to GNU General Public License.

Functionality

This product provides the following features:

  • maintaining several projects;
  • Flexible role-based access system;
  • error tracking system;
  • Gantt and calendar charts;
  • Project News, Documents and File Management;
  • alert of changes using RSS streams and email;
  • wiki for each project;
  • Forums for each project;
  • accounting of temporary costs;
  • Customizable arbitrary fields for incidents, time costs, projects and users;
  • easy integration with versions control systems (SVN, CVS, Git, Mercurial, Bazaar and Darcs);
  • Creating error records based on the received letters;
  • Support for multiple LDAP authentication;
  • the ability to independently register new users;
  • multilingual interface (including Russian);
  • Support for MYSQL DBMS, PostgreSQL, SQLite, Oracle.

Database structure

Users system

Users are one of the central concepts of the subject area. The user model is the basis for identifying and authenticating the system of personnel and customers, as well as to authorize them in different roles, projects, etc.

Role

User roles are determined by a flexible model for determining user access rights. Roles include a set of privileges, allowing to distinguish access to various system functions.

The users are assigned a role in each project in which it participates, for example, "Manager in the project for the development of the site A", "Developer in the project to maintain the company's intranet company" or "Client in a refactor project of the information system of the company B". The user can have several roles. Assigning a role for a separate task (ISSUE) is currently impossible.

Projects

The project is one of the basic concepts in the subject area of ​​project management systems. Due to this entity, it is possible to organize collaboration and planning several projects simultaneously with the delimitation of access to various users (see above). Projects admit hierarchical nesting.

Trackers

Trackers are the main classification by which tasks are sorted in the project. In itself, the concept of "tracker" goes back to error accounting systems (eng. Bug Tracking Tool ), represented each separate project.

In fact, in "Redmine" trackers are an analogue of the class "Task" class and are the basis for polymorphism of different types of tasks, allowing different fields to be determined for each of them. Examples of trackers are "Improvement", "Error", "Documentation", "Support",

Tasks

The tasks are the central concept of the entire system, describing a certain task you want to perform. Each task has a mandatory description and the author, at mandatory, the task is tied to the tracker.

Each task has status. Statuses are a separate entity with the possibility of determining the rights to assign status for different roles (for example, the status "rejected" can only be assigned a manager) or determining the relevance of the task (for example, "open", "appointed" - relevant, and "closed", " Rejected "- no).

For each project, a set of development stages and a set of tasks categories are separately defined. Other fields are also interesting for the "Estimated Time", which serves as the basis for building management charts, as well as the selection field of observers for the task (see "Receiving notifications"). The tasks are able to attach files (there is a separate entity "application").

The values ​​of other listed properties (for example, priority) are stored in a separate common table.

Tracking the status of tasks

For tracking changes to the task parameters by users, the system responds two entities: "Recording a change log and" Changed parameter ". The log entry displays one action of the user to edit the parameters of the task and / or add a comment to it. That is, simultaneously serves as a tool for conducting the history of the task and a tool for the maintenance of a dialogue.

The entity "Changed parameter" is tied to a separate log entry and is intended for storing the old and new value of the user-changed parameter.

Communication between tasks

Tasks can be interrelated: for example, one task is a subtask for another or precede it. This information may be useful in the program development planning, a separate entity is responsible for its storage in Redmine.

Accounting spent on the draft time

The system maintains accounting of the spent time due to the essence of the "spent time" associated with users and the task. Essence allows you to store the time spent, type of user activity (development, design, support) and a brief comment on work. These data can be used, for example, to analyze the contribution of each participant in the project or to assess the actual labor intensity and the cost of development.

Binding repositories

Redmine provides integration with various versions control systems (repositories). Integration is to track changes in the external repository, fixing them in the database, analysis of changes to bind to certain tasks. In the infological structure of the system for integration with external repositories, three entities are responsible: "repository", "editors" and "change". The "repository" is a project associated with a project that stores the type of connected repository, its location and identification data of its user.

"Editorial" is the display of the editorial board of the repository, and, in addition to information fields, can be tied to a specific task (for this you want to specify in the description of the "Refs #num" changes, where Num is the task number), and to the author-author of the editorial board. The entity "Change" is designed to store the list of modified (added, remote, displaced, modified) files in each edition.

Receipt of notifications

User notifications about changes occurring on the site is carried out using the essence of "observers" connecting users with objects of various classes (projects, tasks, forums, etc.). In the database, the RSS subscription access keys are also stored, allowing notifications through this technology, also notifications are sent using email.

Some flaws redmine

For the new older version you need to do the same.Check neutrality.

The discussion page must have details.

  • Managing files and documents in RedMine is reduced to adding, deleting and editing them. You can not manage access rights to any files or individual documents.
  • There are no alerts on changing documents.
  • In RedMine, you cannot manage access rights at the level of individual task fields. For example, at the moment, it is impossible to hide estimations of the work on a project or information about the spent time.
  • In Redmine All additional fields are available to all users, all project participants will be able to see them and change them. This restriction can lead to difficulties in the presence of an inhomogeneous command when managers and developers, and customers have access to the project.
  • Redmine does not have rights to separate types of transitions in Workflow. For example, now it is impossible to indicate that when someone finishes correcting the error, it must choose a responsible tester and should specify the build number. Also you can not hide the internal correspondence between programmers from the client.
  • In Redmine, the overall labor-intensity of tasks is not displayed in the task list, and in labor-intensive reports it is impossible to make selection, including according to the Contractor.

Chiliproject.

As a result of the fact that the vision of some users relative to the project was distinguished from the vision of the developers leader, the Forma Redmine called Chiliproject was created.

see also

Literature

  • 前田 剛 (GO Maeda) 入門 Redmine Linux / Windows 対応. - 秀和 システム. - 226 p. - ISBN 978-4-7980-2137-9
  • Gunther Popp. KonfigurationSmanagement Mit Subversion, Maven und Redmine: Grundlagen Für Softwarearchitekten und Entwickler. - 3. - Dpunkt.verlag GmbH, 2009. - P. 362. - ISBN 9783898645218

Links

Redmine. [ɹɛdmɑɪn] - Open server web application for project management and tasks (including error tracking). Redmine is written in Ruby and is an application based on the well-known web framework Ruby On Rails. Distributed according to GNU General Public License.

Encyclopedic YouTube.

  • 1/4Views: 337.

    1,067

    20 314.

    1 108.

  • How To Install Redmine (Project Management) on Antsle

  • Mit Redmine Effizient Mitarbeiter, Projekte Und Aufgaben Verwalten

  • Redmine - Herramienta de Gestion De Proyectos

  • [Kube 42] Deploying Redmine In Kubernetes Cluster

Content

Functionality

This product provides the following features:

  • maintaining several projects;
  • Flexible role-based access system;
  • error tracking system;
  • Gantt and calendar charts;
  • Project News, Documents and File Management;
  • alert of changes using RSS streams and email;
  • Forums for each project;
  • accounting of temporary costs;
  • Customizable arbitrary fields for incidents, time costs, projects and users;
  • easy integration with versions control systems (SVN, CVS, Git, Mercurial, Bazaar and Darcs);
  • Creating error records based on the received letters;
  • Support for multiple LDAP authentication;
  • the ability to independently register new users;
  • multilingual interface (including Russian);
  • Support DBMS MYSQL, Microsoft SQL Server [2] , PostgreSQL, SQLite.

Database structure

Users system

Users are one of the central concepts of the subject area. The user model is the basis for identifying and authenticating the system of personnel and customers, as well as to authorize them in different roles, projects, etc.

Role

User roles are determined by a flexible model for determining user access rights. Roles include a set of privileges, allowing to distinguish access to various system functions.

The users are assigned a role in each project in which it participates, for example, "Manager in the project development project", "Developer in the project to maintain the company's intranet company" or "Client in a refactor project of the information system of the company B". The user can have several roles. Assigning a role for a separate task (ISSUE) is currently impossible.

Projects

The project is one of the basic concepts in the subject area of ​​project management systems. Due to this essence, it is possible to organize joint work and planning several projects simultaneously with the delimitation of access to various users (see above). Projects allow hierarchical nesting.

Trackers

Trackers are the main classification by which tasks are sorted in the project. In itself, the concept of "tracker" goes back to error accounting systems (eng. Bug Tracking Tool ), represented each separate project.

In essence, in "Redmine", the trackers are an analogue of the class "problem" class and are the basis for a polymorphism of various types of tasks, allowing you to determine for each of their type various fields. The trackers are "improvement", "error", "Documentation", " Support".

Tasks

The tasks are the central concept of the entire system, describing a certain task you want to perform. Each task has a mandatory description and the author, at mandatory, the task is tied to the tracker.

Each task has status. Statuses are a separate entity with the possibility of determining the rights to assign status for different roles (for example, the status "rejected" can only be assigned a manager) or determination of the relevance of the task (for example, "open", "appointed" - relevant, and "closed", " Rejected "- no).

For each project, a set of development stages and a set of tasks categories are separately defined. Other fields also are also interesting for the "estimated time", which serves as the basis for building management charts, as well as the field of choice of observers for the task (see "Receiving notifications"). The tasks are able to attach files (there is a separate entity "application").

The values ​​of other listed properties (for example, priority) are stored in a separate common table.

Track the change of task parameters

For tracking changes to the task parameters by users, two entities are responding in the system: "Recording a change log" and "Changeable parameter". The log entry displays one action of the user to edit the parameters of the task and / or add a comment to it. That is, simultaneously serves as a tool for conducting the history of the task and a tool for the maintenance of a dialogue.

The entity "Changed parameter" is tied to a separate log entry and is intended for storing the old and new value of the user-changed parameter.

Communication between tasks

Tasks can be interrelated: for example, one task is a subtask for another or precede it. This information may be useful in the program development planning, a separate entity is responsible for its storage in Redmine.

Accounting spent on the draft time

The system supports the taking into account time thanks to the essence of the "spent time" associated with users and the task. Essence allows you to store the time spent, type of user activity (development, design, support) and a brief comment on work. These data can be used, for example, to analyze the contribution of each participant in the project or to assess the actual time consideration and the cost of development.

Binding repositories

Redmine provides the ability to integrate with various versions control systems (repositories). Integration is to track changes in the external repository, fixing them in the database, analysis of changes to bind to certain tasks.

In the infological structure of the system for integration with external repositories, three entities are responsible: repository, editors and change.

  • Repository - a project associated with the entity that stores the type of connected repository, its location and identification data of its user.
  • Editorial - Displaying the editorial office of the repository, and, in addition to information fields, can be tied to a specific task: this requires specify in the description of the "Refs #num" changes, where Num is the task number), and to the author-author of the editorial board.
  • Change - stores a list of modified (added, remote, displaced, modified) files in each edition.

Receipt of notifications

User notifications about changes occurring on the site are carried out using the essence of "observers" connecting users with the objects of various classes (projects, tasks, forums, etc.). The database also stores access keys to the RSS subscription, allowing you to receive notifications through this Technology, also notifications are sent using email.

Some flaws redmine

  • Managing files and documents in RedMine is reduced to adding, deleting and editing them. You can not manage access rights to any files or individual documents.
  • In RedMine, you cannot manage access rights at the level of individual task fields. For example, at the moment, it is impossible to hide estimations of work time on the task. But you can make additional fields visible only to users with defined roles.
  • In Redmine, the overall labor consideration of tasks is not displayed in the task list.
  • There is no possibility to give the user a role in the entire system; For example, the "Project Office Manager" must have access to all projects in the system: for this you need to add a user with this role to all projects.
  • Connect the Git repository is possible only if Redmine, and the repository are on the same server.

Chiliproject.

As a result of the fact that the vision of some users relative to the project was distinguished from the vision of the developers leader, the Forma Redmine called Chiliproject was created. Currently, this project is closed.

see also

Notes

Literature

  • 前田 剛 (Go Maeda). 入門 Redmine Linux / Windows 対応. - 秀和 システム. - 226 p. - ISBN 978-4-7980-2137-9.
  • Gunther Popp. KonfigurationSmanagement Mit Subversion, Maven und Redmine: Grundlagen Für Softwarearchitekten und Entwickler. - 3. - Dpunkt.verlag GmbH, 2009. - P. 362. - ISBN 9783898645218.

Links

  • Official site redmine (eng.)
  • Android Client for Redmine (eng.)
  • Installing and Configuring Redmine Bundles with Gem, Ruby, Rails, PostgreSQL, Passenger, Nginx
  • Installing and Configuring Redmine Bundles with Gem, Ruby, Rails, MySQL, Passenger, Nginx (inaccessible link)
  • Creating plugins for redmine
  • RedMineApp - iPhone application for redmine
  • Redmine PM - Redmine Client for iPhone / iPad
  • Redmine To Go - Windows Phone Client for Redmine
  • Redmineup is a set of free and commercial plug-ins and themes for Redmine.
  • RMClient is a client for Windows, Mac, Linux, commercial.
  • Setting the life cycle tasks
  • Solving performance problems
  • Operational planning in Redmine
  • Plugins Writing Guide
  • Detailed installation instructions
  • Easy Redmine - Commercial Option
  • Designer Jetware Installars and Virtual Machines with Redmine

This page was last edited on May 3, 2021 at 13:31.

  • - maintaining several projects;
  • - error tracking system;
  • - alerts about changes via email and RSS feeds;
  • - Customizable task statuses;
  • - Customizable arbitrary fields for tasks, time costs, projects and users;
  • - accounting of time costs (hours);
  • - Ganta charts and calendar;
  • - Wiki for each project;
  • - Project News Management, File Management and Documents;
  • - Forums for each project;
  • - multilingual interface, including Russian;
  • - Easy integration with repositories (SVN, CVS, Git, Mercurial, Bazaar and Darcs);
  • - Access separation system based on roles;
  • - support for multiple LDAP authentication;
  • - the ability to independently register new users;
  • - expansion of the functionality of the system by installing additional plugins ;
  • - Support DBMS: MySQL, PostgreSQL, SQLite, MS SQL Server (from version 2.3).
  • Consider the Redmine system in more detail. Below is some screenshots, on the first of them - a list of tasks according to one of the projects.

    Task tab Allows you to see both the current project tasks (by default) and previously closed tasks - customer requests are possible.

    God you are mine, I have conflicts!

    (filters). Custom queries can be saved for subsequent use by all users of the system.

    (When you install the "Public" query checkbox) or for use by the user who created the request. After creating a query, you can configure the list of tasks in one click,

    Sooner or later (probably already during the first update to the new younger version) you will encounter conflicts of mergers. During the Git rebuasion, it uses commits one by one and stops every time the use of the commit occurs with errors. In this case, the team

    Taking advantage of the reference with the query by the "Saved queries" on the side panel on the right.

    • The system implements the mechanisms for tracking tasks and subscriptions to tasks. For each task, observers can be assigned, after which when the status changes, the parameters of the task, add new comments, files to the task, the observer users will receive the appropriate e-mail notifications.
    • All system users can create new tasks. In order to add a new task to the project, you need to go to the New Task tab,
    • Select the task tracker and fill out mandatory (*) and additional (including custom user) task fields. In the "Theme" field, it is briefly formulated, but informatively the meaning of the task (when you go to another field by pressing the TAB key, in the case of an additional plug-in, you can search for the entry of the topic among previously created tasks). In the "Description" field sets out a detailed content of the task. To enhance the readability of the text, you can use the capabilities of the built-in WEB editor.
    • The task can be attached files, the maximum size of which is regulated by the system administrator.
    • Observers can be connected to the task: to create a task, when making meals to the task, change the status of the task, observers will receive appropriate notifications to their email address. Users can also add themselves as an observer to an affordable task, for which in the task card should be followed by the "Follow" link.

    The tasks in the system can be interrelated: for example, one of them is a subtask for another, precedes her or these tasks are simply related to each other.

    Git Status.

    The Redmine system provides a separate entity called "related tasks". Related tasks may have the following types of links:

    Shows problem files.

    - "duplicates" - associates the tasks in such a way that the closing of one entails the closing of another task;

    Check which of the commits made a failure, find out why it was intended (meaningful commit messages will help), correct files, command

    - "related to" is just a reference to another task. Such a link is used to demonstrate that these tasks are combined by one goal or other common attributes; - "Blocks" - shows that this task must be completed before starting work on another task. In both tasks, you can independently change the percentage of execution, dates, status, but with one exception: the locked task cannot be closed until the blocking task is closed. However, in the locked task, it is possible to set the status "performed", the readiness of 100%, even if the readiness of the blocking task leaves much to be desired; - "precedes" - sets the procedure for performing tasks so that this task should be completed for N days before the start of the associated. In the associated task card, it will not only be an entry on binding, but also automatically change the timing and end of the task. The term of the task will be equal to the date of the tied problem, increased by the number of days specified in the bundle;

    Git Add

    - "Next" - sets the procedure for performing tasks in such a way that this task can be performed only after the associated. This connection is reverse the previous one.

    Add each corrected file when you finish. If conflicts have been eliminated, you can view the changes that will be fixed using the command

    Timing will automatically change not in the binding, but in the editable task. Therefore, the link "Next" must be used, only making sure that the tasks should really go one after another at a given time interval between them.

    Git Diff --Cached

    The following pictures are devoted to the configuration and administration of the Redmine system.

    . As soon as you consider the result satisfactory, you can continue to rebuas with the team

    Trackers play an important role in tracking tasks. They are involved in determining the conditions for the transition of tasks from one state to another, the availability of fields.

    Git Rebase --Continue.

    The tracker is a logical association of tasks in one group within the project, for example, the elimination of the error, the development of a new functionality, etc. Tracker may be

    Included in one, several or all projects.

    REDMINE users must be included in one of the role groups, the number of roles is not limited. The system provides two predefined roles:

    The role of "anonymous" - for unregistered users, the role of "non-participating" - for registered, but not included in any user project.

Anonymous cannot create tasks.

Each role is set to access rights to possible actions with tasks, projects, documents, files, Wiki, forums, etc. It's obvious that

The roles of "Project Manager" should be given more powers, the role of "performer" - smaller, the roles of "non-participating" - even less, the roles of "anonymous" to allow minimum possibilities

In public projects, and in individual projects, everything is forbidden. The participants of the system role "administrator" have unlimited rights throughout the system.

Depending on the selected tracker, each task can pass through certain stages and have different statuses.

So, in the example below for the created trackers "Troubleshooting", "one-time task, ADHOC", "New Development" Maximum full way through task statuses:

1. New -> 2. Distributed -> 3. Analysis -> 4. In operation -> 5. Made -> 6. Acceptance by the Customer -> 7. Closed

The roles of "Project Manager", "Executive", "Customer, Member" were created. Since the project manager is an administrator of his project, then within the framework of his project can be moved to the task of in different statuses. The performer of the task or customer / participant can translate the task only from in certain statuses. At any stage, the task may be canceled (translated into the status "rejected") indicating the reason. .

When you make changes to the task, changes in the status of the task, add comments to all the users involved in the task will come automatically e-mail.

For each pair "Role - Tracker" there is an opportunity to configure visibility, the obligation to fill the fields (including configurable fields) in the task card. System fields

"Project", "Tracker", "Theme", "Priority", "Private" (task) are always required to fill. Configuring the sequence of actions for one of the pairs "Role - Tracker",

Sequence settings can be copied for another pair ("Copy" link).

In the Redmine system for tasks, users and other entities, you can create an arbitrary number of customizable (custom) fields. Custom fields will be

Display in a task card in two columns after the area of ​​predefined system fields. Sort determines the order of custom fields in the task card. Custom fields support the following data types: string, long text, integer, real number, date, list for selecting a single value, List for selecting multiple values, link, user. Each custom field can be enabled in all or only the specified projects, use the selected trackers. In defining a custom field, you can immediately install Global settings are required and visibility for roles, as well as field participation in user queries (filters) and search queries. The program for managing servers and services Redmine can be found as start-up -> Bitnami Redmine Stack Group -> Redmine Manager Tool. With this administrative application, you can manage the Redmine services, the Apache Web server, MySQL database server.

Reporting

The Redmine system provides a Gant diagram, and with the help of additional plugins it is possible to form reports to understand the status of projects and tasks.

Perhaps a private submission of developers about the formats of these reports will arrange you.

Nevertheless, analytical reports on project tasks are best created based on the data exported to the CSV file. For this

In the main menu of the RedMine system, select "Projects" -> "All Projects", follow the link "View all tasks",

To the list of tasks, apply / cancel the desired filtering criteria and click on the "Export to CSV" link at the bottom right below the task list.

In this way, the task list will be unloaded - the Issues.csv file.

Next, you must open a new MS Excel book, select "Data" -> "from text" in the main menu, specify the path to the file isSues.csv, In the Select Code Page Dialog box "1251: Cyrillic (Windows)", (Perhaps as a separator symbol, noted - "Other", specify the symbol | (vertical trait)) and click the "Finish" button. Data will be imported to Excel file while saving the connection to the CSV file. On the basis of the source data table, you need to create summary tables, diagrams (highlight the table / columns, then select "Insert" -> "Summary Table"). It is possible to ensure analytical indicators in the base table, you will need to create additional calculated columns.

An example of a report can be found in the investment to this article.

Redmine¶

Redmine IS A Flexible Project Management Web Application. Written using the Ruby On Rails Framework, IT IS CROSS-Platform and Cross-Database.

Redmine Is Open Source and Released Under the Terms of the GNU General Public License V2 (GPL).

Features¶

Some of The Main Features of Redmine Are:

Read More About Redmine Features.

Documentation¶ .

You can read the

Redmine Guide

Other Resources:

Online Demo¶ A Shared Online Demo Can Be Found At http://demo.redmine.org/. IT's Been Setup to Give Registered Users The Ability to Create Their Own Projects This Means Once You Register, You Can Create Your Own Project On There and Try Out The Project Administration Features. Alternatively, You Can Get Your Own Redmine Demo Environment at http://m.redmine.org with Full Administrator Privileges After Filling a Simple Form.

Support & Getting Help¶

For Getting Help or Discussing Redmine, You Can Browse The

Redmine Forums. 

Hosted Right Here in Redmine. WE ALSO HAVE A Chatroom. - Join #RedMine On The Freenode Irc Network.There's Also An Unofficial Workspace ON

Slack Where You can Ask Questions and Participate in Discussions with Other Redmine Users. Before Submitting A Bug Report, A Patch or a Feature Request Here, Please Read The Submission Guidelines.

Contributing and Helping Out¶ Redmine Is Built and Maintained by Community Volunteers. If you enjoy using it and Would Like to Give Back to the Community, The Contribute Page Has Sevel Ideas. Software Development Experience Is Not Required. Check Out The Teams Page If You are Interested in a Specific Area to Contribute Regularly. You can also make a donation and get listed on the redmine donors page. Who Uses Redmine? ¶ This page Lists Some Companies and Projects using Redmine. Redmine Books¶ Mastering Redmine 2nd Edition

IS A Comprehensive Guide with Tips, Tricks and Best Practices for Using Redmine.you Can BUY IT Online.

Redmine Plugin EXTENSION AND DEVELOPMENT Provides An Overview of the Tools Available to Developers Who Want to Extend Redmine To Work Their Way.you Can BUY IT Online. Redmine Cookbook. Chatroom. .

: Over 80 Hands-On Recipes to Improve Your Skills in Project Management, Team Management, Process Improvement, and Redmine Administration.You Can BUY IT Online. Redmine Books¶ Disclaimer: This is not an ordinary type guide "How to install Redmine". In it, I will not dive into the database setting or installing the web server. I will also not talk about setting up Redmine. Redmine documentation in this plan is quite complete. And in order not mentioned in the official documentation, there is a general procedure for running Rails applications that can be easily found on the Internet.

Instead, it will be about accompanied by its own, more or less customized version of Redmine, which can be deployed using one shell command when necessary. Ready? Then let's start. Set the build type "all-in-one" and ready to start virtual machines BitNami installation packages or pre-installed virtual machines are good for the fast REDMINE sample, but are not suitable for productive use. Why? Because they have no update. Oh, a second, Bitnami has. True, it looks more like a joke. "Install the new version of the entire stack to another directory and move your data there," this is not an update. Not a word about setting up, customization and plugins, which probably also need to be saved and reinstall. I wish good luck with such a "update". Reliza REDMINE patches over or twice a month. Corrections of security-related errors are issued as needed - you do not want to miss them?

The fact that people often forget about: updating time does not always depend on you. Of course, you can postpone the update before the release of the next younger version of the Redmine - for a few weeks (probably even for a longer period). But you do not want to detect new security problems in Redmine or Rails sit with a nepostable system until it is possible to release the time to install and configure the new BitNami stack and manually move all the data?

Installation is only the top of the iceberg. Update - this is what will have to do regularly 

The search for the simplest installation method definitely ceases to be relevant as soon as the decision is made to use Redmine in production. Simple accompaniment and the possibility of modernization - this is what you need to sharpen attention to minimize costs and risks associated with the use of your own redmine.

  • Below I will tell you how to simply support the redmine in the current state. Redmine Books¶ .
  • Use Git. Redmine Books¶ Even if you intend to run stock redmine without any settings or plug-ins, use the GIT repository to store the redmine copy. At the very least, the presence of a specialized repository will give you the place of storage of all necessary for deployment (later this will be considered more details). Sooner or later you (or your users) Redmine Is Built and Maintained by Community Volunteers. If you enjoy using it and Would Like to Give Back to the Community, The Contribute Page Has Sevel Ideas. Software Development Experience Is Not Required. Check Out The Teams Page If You are Interested in a Specific Area to Contribute Regularly. .
  • WELL

Install some plugin or custom-made topic, and for this will be ready infrastructure. Experiments with changes and testing of plugins and those in local branches without disorders in the production code are becoming very simple in the presence of the own Git C Redmine repository. So now we will start with the configuration of the repository. Although the main Redmine repository is an instance of Subversion, the GitHub has a semi-official repository that is supported by the main committer and is constantly updated. Use it to configure your own repository: Setting up local clone Redmine

$ Git Clone [email protected]: redmine / Redmine.git $ CD Redmine $ Git Remote Rename Origin Upstream $ Git Remote Add Origin [email protected]: Redmine.git $ Git Checkout -B RedMine / 3.2-Stable Upstream / 3.2 -Stable $ Git Checkout -B Local / 3.2-Stable $ Git Push --Set-Upstream Origin Local / 3.2-Stable

Change the version number 3.2-stable On the number of the last stable version of Redmine.

Remote repository

[email protected] 

It should be private, as it will store the deployment configuration (and possibly other information, which is not worth publishing). Since the deployment process described below will extract the code from this repository, the repository must be available during deployments, so do not place it on desktop computers. The ideal will be the situation when the repository will also be available from a web server on which the deployment occurs. But this, if necessary, you can get around. Now you have two local branches: RedMine / 3.2-Stable Redmine Is Built and Maintained by Community Volunteers. If you enjoy using it and Would Like to Give Back to the Community, The Contribute Page Has Sevel Ideas. Software Development Experience Is Not Required. Check Out The Teams Page If You are Interested in a Specific Area to Contribute Regularly. и which tracks Redmine 3.2 without additional functionality from the Github / Redmine repository presented by the above remote ascending Redmine Is Built and Maintained by Community Volunteers. If you enjoy using it and Would Like to Give Back to the Community, The Contribute Page Has Sevel Ideas. Software Development Experience Is Not Required. Check Out The Teams Page If You are Interested in a Specific Area to Contribute Regularly. repository which tracks Redmine 3.2 without additional functionality from the Github / Redmine repository presented by the above remote Local / 3.2-Stable

where all the settings of the deployment, customization, themes and plugins will be placed.

Advanced updates of versions

Redmine uses the following version numbering scheme: XYZ MAJOR / MINOR / PATCH. Each younger version has its own Stable branch in which fixes and safety patches will be applied over time (as long as this version is still supported). In our case, this is a branch

From time to time, this ascending branch will receive some new commitments. Your task is to include new commits in the local branch For deployment. Although it is possible and just regularly complement the ascending branch, I propose to use Git Rebase. To support your own set of changes over .

stock REDMINE: Rebupping local changes over "naked" redmine: $ Git Checkout Redmine / 3.2-Stable $ Git Pull # New Upstream Commits COMING IN $ Git Checkout Local / 3.2-Stable $ Git Rebase Redmine / 3.2-Stable

Rebase:

Will cancel all local changes in

Links

  1. Update
  2. to reflect the changes that occurred in
If you unexpectedly got a bunch of conflict, and there is no time to solve this problem, you can simply interrupt the current rebuasion using the parameter

All local changes on the "bare" version will re-apply.

Redmine. The result will be Pure story In which your (local) commits are always on top of the last (ascending) Commits of Redmine.

Junior and older updates

Now that there is a new stable branch (let's say 3.3-stable ), do the same - relorate your changes on top of it. Git commands will be slightly different due to the change of the upward branch: Transfer of local changes to a new stable branch $ Git Fetch UpStream $ Git Checkout -B Redmine / 3.3-Stable Upstream / 3.3-Stable $ Git Checkout -B Local / 3.3-Stable Local / 3.2-Stable $ Git Rebase --onto Redmine / 3.3-Stable Redmine / 3.2-Stable Local / 3.3-Stable These teams first create two new local branches for version 3.3: one of the ascending, and the other is from the local branch 3.2. Then they relocate local changes over Redmine / 3.3-Stable

. Local changes here are the difference between

Local / 3.3-Stable (which is still ). Now

Contains RedMine 3.3 plus any local changes.

Добавить комментарий