Lavagna HELP
Index
  1. 1About
  2. 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
  3. 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
  4. 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
Import data from external sources
Index
Manage profile
  1. 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

3.12Create tickets via E-mail

Lavagna supports creating cards via E-mail.

3.12.1Manage ticket E-mail configuration

To manage mail ticket, go to the Project Settings, and then the “Mail Ticket” tab.

Mail ticket

3.12.1.1Create mail configuration

To add a new mail configuration, click on the plus button.

Fill the dialog with the following information:

  • Name: A name identifying the configuration

  • Inbound Config: The E-mail account Lavagna reads from.

  • Protocol: Mail server protocol. One from: IMAP, IMAPS, POP3, POP3S. We recommend using IMAPS.
  • Host: Mail server address
  • Port: Mail server port
  • User: Mail account username
  • Password: Mail account password
  • Properties: Properties for the Java Mail client. One property per line.

  • Outbound Config: The E-mail account Lavagna uses to notify the user a new ticket has been created.

  • Protocol: Mail server protocol. One from: SMTP, SMTPS.
  • Host: Mail server address
  • Port: Mail server port
  • User: Mail account username
  • Password: Mail account password
  • From: What to send the E-Mail as.
  • Properties: Properties for the Java Mail client. One property per line.

  • Notification E-Mail: The content of the notification E-Mail sent to the user.

  • Subject: The subject of the notification E-Mail. Use the identifier to reference the created card.
  • Body: The content of the notification E-Mail. Supports markdown. Use to reference the display name or address of the user creating the ticket, and to reference the created card.

Then click Save.

3.12.1.2Add ticket configuration

Once a mail configuration is added, click “Add Ticket Config”. A dialog will appear.

Add ticket config dialog

  • Name: A name identifying the ticket configuration
  • Alias: The address this configuration should read E-Mails from. If no alias is configured on the E-Mail account, use the address.
  • Send mail as alias: Whether to send the notification E-Mail using the configured alias.
  • Create card in: Configure where the card is created.
  • Board: Select a board
  • Column: Select a column in the selected board
  • Notification E-Mail: The content of the notification E-Mail sent to the user.
  • Override Mail Config Template: Override the subject and body configured in the Mail Config
  • Subject: The subject of the notification E-Mail. Use the identifier to reference the created card.
  • Body: The content of the notification E-Mail. Supports markdown. Use to reference the display name or address of the user creating the ticket, and to reference the created card.

Then click “Save”.

3.12.1.3Edit configurations

Use to edit both mail configuration and ticket configuration. See the previous section to find details about each parameter.

3.12.1.4Enable/Disable configuration

Single ticket configuration can be enabled or disabled, or entire mail configuration. When a mail configuration is disabled, no ticket configuration will be processed.

To enable, click .

To disable, click .

3.12.1.5Delete configuration

To delete a configuration, click .

NOTE: mail configuration with one or more ticket configuration can’t be deleted.

3.12.2Support localized E-Mail notifications

By taking advantage of the possibility to override notification templates for a specific alias, it’s possible
to create a more customized experience for users in different language regions.

An organization can have a generic Mail Config (e.g. support@organization.com) with a english notification template.

A default ticket configuration using support@organization.com as alias, with “Override Mail Config Template” left unchecked will cover international users.

Then, a set of aliases (e.g. support-es@organization.com, support-fr@organization.com) can share the same mail account (support@organization.com),
but by using different aliases can send localized mail notification, while still creating cards in the same column as any other ticket config.

While this solution requires the duplication of some configuration, in our opinion it improves the experience of the end users.

Import data from external sources
Index
Manage profile