This manual refers to Easy Redmine and Easy Project. The functionality of the programs is identical, which is why the names “Easy Redmine” and “Easy Project” are used synonymously here.
\nNow that the application has been set up and configured, we can look at the impact of the settings and, above all, at the actual project work.
\nIn the following chapters, we will take a top-down journey from the highest level – the projects – through the issues down to the individual time entries.
\nThe terminology remains largely identical to versions 12 and 13. Even in version 14, it is possible to define projects without a start or end date. This flexibility does not always correspond to classical PM theory, but it remains useful due to configurability.
\nThe central attributes still exist: name, parent project, description, start/due date, public visibility, planned status, custom fields, modules, issue types, etc. The logic for membership inheritance, private comments and custom fields remains in place.
\nName
\nThe name of the project serves for unique identification and is displayed throughout the user interface.
\nSubproject of
\nThis entry defines whether the current project is a subproject of another project. This creates a hierarchical structure between projects. The parent project can aggregate issues, resources, or reports from several subprojects.
Description
\nA text area to explain the content of the project, its goals, requirements or other important information.
Start date / Due date
\nIndicates the planned project period. These dates help with scheduling and in Gantt charts.
Public visibility
\nDetermines whether the project is visible to all users or only to project members. Public projects are visible to everyone.
Planned status (status: planned / active / closed)
\nIndicates which phase the project is in. This helps with filtering and organizing projects.
Custom fields
\nAllow you to store additional project-specific information that goes beyond the standard attributes (e.g. customer number, budget).
Modules
\nHere you define which functions (e.g. issues, time reports, wiki, documents) are available in the project. Modules can be enabled or disabled depending on project needs.
Issue types
\nDefine the categories of issues in the project, e.g. “Feature”, “Bug”, “Support”. Each type can be configured with its own workflows and fields.
Inheritance of memberships
\nMembers and their roles in parent projects can be inherited by subprojects. This ensures that access rights remain consistent.
Private comments
\nComments on issues can be marked as “private”, so they are only visible to certain users (or groups), e.g. only project managers or admins.
Custom fields (still valid)
\nThese fields retain their validity and functionality from previous versions, with continued flexible adjustability per project.
After creating the project, you are taken to the project settings page, where you will find some additional options. To make it easier to set up future projects, there is the option of creating project templates – more on this in chapter 2.6.
\nWe will now explain all the important options within projects so that you are prepared for all eventualities. To access the menu, move the mouse over the gear icon in the upper right corner when you are inside the project.
\nIn this section, you can manage the central attributes of your project, such as name, description, start and end date, and the visibility of the project. In addition, you can configure custom fields, enable or disable modules, and define issue types. Changes to these settings directly affect the structure and functionality of your project.
\nIn this section, you will find a log of changes to the project attributes as well as comments written on the project for important announcements or changes. These comments can also be displayed on the project overview page.
\nApart from the regular modules to enable/disable, you can also define the default project page here, i.e., when you open the project, you first land on this page. You can also reorder the items in the project menu for maximum convenience by checking Has a custom menu?.
\nAdding/removing/editing memberships is intuitive, but there are a few principles you need to keep in mind.
\nGroup memberships
\nMilestones are important points in the project plan. Here you see a simple list of milestones and options to create, edit or delete milestones.
\nThe best way to create and edit milestones is in the Gantt chart, where they are displayed clearly together with the underlying issues.
\nHere are some recommendations and general information on the use of milestones:
\nIn the project’s module bar, milestones are listed under Roadmap, which symbolizes the path marked by the milestones. The Roadmap menu item appears as soon as a milestone has been created.
\nThe agile modules Scrum and Kanban have been functionally extended and made more user-friendly. Empty swimlanes are now automatically hidden, which improves clarity. Boards can be integrated more individually into dashboards, including new widgets and flexible display options. Issues can be edited directly on the board via the Quick Task Editor, without leaving the page. In addition, performance and loading times for large boards have been optimized, and there are more configuration options for card appearance and automatic status updates when moving issues.
\nRight with the first setting, an important decision must be made.
\nIn addition, it is possible to enable/disable activities for time tracking in this project to simplify the process a bit.
\nBased on a global setting (chapter 1.3.1 – Assign activities to roles) you will see a matrix of roles and activities that you can configure to define which roles can log time for which activities. These settings are very complex but can significantly simplify evaluations and overviews later on.
\nThese settings are identical to the global task timer settings (chapter 1.5.4). The difference is that here you have the option to override the global settings if you decide that behavior in this project should differ from the rest of the system.
\nNew in version 14: see also https://www.easyproject.com/blog/easy-project-14-powered-by-ai
\nThe project overview remains modular (project description, project team, history, information, issues from filter).
\nNew:
\nHere is an example of a project overview page. It follows the principles explained in the previous chapters. Consider it a recommendation for the beginning, which you can later adapt according to your own practice.
\n2.5 Project building blocks (components / elements of the project)
\n2.6 Project templates (Project Templates)
\n