Translated with AI from the Russian original.

EvaTeam has released an update to version 2.30 "Irkutsk" of its EvaProject and EvaGit products. The updates include improvements and additional features designed to enhance the efficiency of development teams and simplify project management.

Among the innovations in EvaProject is the development of a new requirements management module that allows organizing hierarchical structures with unlimited nesting depth, automatically assigning numbers to requirements, and comparing their versions. Dashboards have become more flexible with the support of Rich-filters, similar to Jira's capabilities. The gadget architecture now ensures independence from each other and individual customization of data presentation.

In addition to the existing logic, the task approval process can be carried out individually in the card of each task. Information about the status of task archiving is displayed directly in the card, preventing erroneous changes in outdated data. Kanban boards are supplemented with indicators of planned labor costs.

The new version of EvaGit includes tools for discussing and managing comments. For example, in change proposals, you can leave a discussion of specific lines of code. Additionally, functions for editing and deleting comments have been implemented, as well as automatic linking and marking of outdated threads when the corresponding sections of code are changed or deleted.

Now on the front page

Articles

Why even a PC case should be branded

In Russian conditions, the popularity of PCs assembled by small local companies or in-house corporate IT departments continues to grow rapidly. Such solutions have historically been more popular in Russia than in other developed markets, but today new nuances have emerged in the segment's evolution, which we discussed with Karim LASKRI, Business Director of FSP Group in the CIS region.

News

Storage you can trust in the background: Basis SDS 2.3 released with scheduled diagnostics and an observer role

A storage system is the only infrastructure layer where an error cannot be “rolled back”: neither a reboot nor a configuration rollback will restore lost data. That is why users expect predictability from software-defined storage rather than just new features—ensuring background processes finish what they started, and administrators can see the cluster status not only “right now,” but also over time.