Ir al contenido

DOC-04: Functional Configuration and Customization

Version: 1.0 Scope: Redmine application configuration (Post-Deployment).

0views

Version: 1.0 Scope: Redmine application configuration (Post-Deployment).

  • URL: http://<IP-SERVER-UBUNTU>:5588
  • Default credentials: admin / admin
  • Immediate action: The system will request a mandatory password change.
  1. Download/Copy the theme (e.g., circle) into the ~/redmine/themes folder on the Ubuntu server.

  2. Restart the container if necessary (usually not required for themes, but recommended):

    docker compose restart redmine
  3. Go to Administration → Configuration → Display and select the theme.

To install plugins (Checklists, Tags, Kanban, etc.):

  1. Copy the plugin folder to ~/redmine/plugins.

  2. MANDATORY: Run dependency installation and database migration:

    # Instalar gemas nuevas
    docker compose run --rm redmine bundle install --without development test
    # Migrar base de datos del plugin
    docker compose run --rm redmine bundle exec rake redmine:plugins:migrate RAILS_ENV=production
    # Precompilar assets (iconos, css, js)
    docker compose run --rm redmine bundle exec rake assets:precompile RAILS_ENV=production
  3. Restart service: docker compose restart redmine.

4. Organizational Structure (Roles and Flows)

Sección titulada «4. Estructura Organizativa (Roles y Flujos)»

4 key profiles have been defined for the organization:

  • IT (Admin): Full access. Global visibility.
  • Project Manager: Full control within their assigned project (Members, versions, Gantt).
  • Collaborator: Operational task management (status changes, time assignment), without access to project configuration.
  • Employee: Only creation of their own tickets and comments. Visibility restricted to "My requests".
  • The transition matrix is configured to prevent low-level roles (Employee) from closing tickets directly.
  • Field visibility (Read-only / Mandatory) is configured according to the status (e.g., “Rejection reason” is mandatory when rejecting).
  • Verify in Administration → Configuration → Notifications.
  • Sender: Must match portel_user@portelcore.local (Configured in DOC-02).
  • Test: Use the “Send test email” button to a user with a valid email (not example.com).
  • ✓ Email Integrity: Validation of notification delivery via a unified sender and correct SMTP authentication.
  • ✓ Role Security: Restricted workflows so that lower roles cannot alter critical statuses or close tickets.
  • ✓ Customization: Visual themes and plugins correctly loaded and migrated to the database without asset errors.