1About
2Install
1. 2.1Database
  1. 2.1.1MySql
  2. 2.1.2MariaDB
  3. 2.1.3PostgreSQL
  4. 2.1.4HSQLDB
2. 2.2Configuration
  1. 2.2.1Self contained
  2. 2.2.2Servlet container
3. 2.3Setup
  1. 2.3.1Step 1, Base url or import
  2. 2.3.2Step 2, Login provider configuration
    1. 2.3.2.1Password provider
    2. 2.3.2.2Demo provider
    3. 2.3.2.3Ldap provider
    4. 2.3.2.4Oauth provider
    5. 2.3.2.5Preconfigured oauth providers
    6. 2.3.2.6Custom oauth providers
  3. 2.3.3Step 3 Insert administator
  4. 2.3.4Step 4 Confirm
3Use Lavagna
1. 3.1Project
  1. 3.1.1Create Project
  2. 3.1.2Project settings
  3. 3.1.3Edit Project
  4. 3.1.4Archive Project
  5. 3.1.5Delete Project
2. 3.2Board
  1. 3.2.1Create Board
  2. 3.2.2Edit Board
  3. 3.2.3Archive Board
  4. 3.2.4Delete Board
3. 3.3Columns
  1. 3.3.1Create a new column
  2. 3.3.2Special columns
    1. 3.3.2.1Access the backlog
    2. 3.3.2.2Access the archive
    3. 3.3.2.3Access the trash
  3. 3.3.3Change the name of a column
  4. 3.3.4Column menu
  5. 3.3.5Change status color
4. 3.4Card
  1. 3.4.1Create a new card
  2. 3.4.2Access the card menu in a board
  3. 3.4.3Work with a card
    1. 3.4.3.1Change the card title
    2. 3.4.3.2Change the card description
    3. 3.4.3.3Add a label
    4. 3.4.3.4Move the card
    5. 3.4.3.5Change the card due date
    6. 3.4.3.6Assign the card to a milestone
    7. 3.4.3.7Work with people
      1. 3.4.3.7.1Assign the card to a user
      2. 3.4.3.7.2Personal operations
    8. 3.4.3.8Work with action lists
    9. 3.4.3.9Attachments
    10. 3.4.3.10Activity
5. 3.5Labels
  1. 3.5.1Use labels
  2. 3.5.2Manage labels
    1. 3.5.2.1Create a label
    2. 3.5.2.2Edit a label
    3. 3.5.2.3Delete a label
6. 3.6Milestones
  1. 3.6.1Use milestones
    1. 3.6.1.1Close a milestone
  2. 3.6.2Manage milestones
    1. 3.6.2.1Create a new milestone
    2. 3.6.2.2Edit a milestone
7. 3.7Search
  1. 3.7.1Filters
    1. 3.7.1.1label
    2. 3.7.1.2to
    3. 3.7.1.3by
    4. 3.7.1.4created
    5. 3.7.1.5watched
    6. 3.7.1.6updated
    7. 3.7.1.7due
    8. 3.7.1.8updated by
    9. 3.7.1.9milestone
    10. 3.7.1.10status
    11. 3.7.1.11location
    12. 3.7.1.12Free text search
  2. 3.7.2Single board search
  3. 3.7.3Global and project specific search
8. 3.8Operations on multiple cards
  1. 3.8.1Select cards
  2. 3.8.2Operations
9. 3.9Calendars
10. 3.10Project Statistics
  1. 3.10.1Filtering
  2. 3.10.2Basic statistics
  3. 3.10.3Chart statistics
11. 3.11Import data from external sources
  1. 3.11.1Trello
    1. 3.11.1.1Requirements
    2. 3.11.1.2Import data
12. 3.12Create tickets via E-mail
  1. 3.12.1Manage ticket E-mail configuration
    1. 3.12.1.1Create mail configuration
    2. 3.12.1.2Add ticket configuration
    3. 3.12.1.3Edit configurations
    4. 3.12.1.4Enable/Disable configuration
    5. 3.12.1.5Delete configuration
  2. 3.12.2Support localized E-Mail notifications
13. 3.13Manage profile
  1. 3.13.1Profile
  2. 3.13.2Calendar access
  3. 3.13.3Change password
4Administration
1. 4.1Configuration parameters
2. 4.2Login
  1. 4.2.1Anonymous user access
  2. 4.2.2Login providers
    1. 4.2.2.1Demo
    2. 4.2.2.2Password (internal provider)
    3. 4.2.2.3Ldap
    4. 4.2.2.4Oauth
    5. 4.2.2.5Preconfigured oauth providers
    6. 4.2.2.6Configurable oauth providers
3. 4.3Users
  1. 4.3.1Add User
  2. 4.3.2Import users from a file
  3. 4.3.3User actions
4. 4.4Access control
  1. 4.4.1Global and Project Roles
    1. 4.4.1.1Default roles
    2. 4.4.1.2Use roles for effective access control
  2. 4.4.2Permissions
  3. 4.4.3Manage roles
    1. 4.4.3.1Add a new role
    2. 4.4.3.2Edit a role
    3. 4.4.3.3Delete a role
    4. 4.4.3.4Edit project role
5. 4.5Mail notifications
6. 4.6Import/Export data
  1. 4.6.1Exporting
  2. 4.6.2Importing
7. 4.7External integrations
  1. 4.7.1Script creation
    1. 4.7.1.1Supported events
  2. 4.7.2Script example
  3. 4.7.3Manage the integration

2.1Database
1. 2.1.1MySql
2. 2.1.2MariaDB
3. 2.1.3PostgreSQL
4. 2.1.4HSQLDB

2.1Database

Lavagna support the following databases:

MySQL version 5.1 or later
MariaDB version 10.0 or later
PostgreSQL version 9.2 or later
embedded HSQLDB version 2.3.1

If it’s not possible to use MySql or Postgresql and the full text search feature is not important, the HSQLDB backend can be used with a file backend. See the HSQLDB section below.

2.1.1MySql

When using MySql, for ensuring a good full text search experience, it’s advisable to set in the MySql configuration file:

[mysqld]
ft_min_word_len=3
ft_stopword_file = ""

The default minimal word length (4) and the stopwords can be problematic for searching acronyms or short words.

Additionally, when creating the database, it must ensured that utf-8 is used everywhere:

CREATE DATABASE lavagna CHARACTER SET utf8 COLLATE utf8_bin;

2.1.2MariaDB

Unit tests are run also on MariaDB and as a general rule everything that must be done for MySql must be done also for MariaDB.

2.1.3PostgreSQL

When using PostgreSQL, ensure that the database/schema is in utf-8.

For the full text search support, the unaccent extension must be present. In general it’s already included in the PostgreSQL
installation. If it’s not present, an error will be launched when running lavagna the first time.

2.1.4HSQLDB

It’s the default development database. But it’s possible to use it a persistent way: when configuring the jdbc url, the file backend can be used: -Ddatasource.url=jdbc:hsqldb:file:lavagna.