Opened 6 years ago

Closed 6 years ago

#56 closed defect (fixed)

[trac] avoid overwriting dropdown defaults when provisioning

Reported by: philll Assignee: philll
Priority: P2 Milestone:
Module: Infrastructure Keywords:
Cc: trev Blocked By:
Blocking: Platform:
Ready: Confidential: no
Tester: Verified working: no
Review URL(s):



Trac instance installed for ABP

How to reproduce

  1. Provision the trac instance with vagrant
  2. Log in to the trac instance at
  3. Click "New Issue"

Observed behaviour

The preset values of the fields "Priority" and "Component" are "P1" and "ABP-Android" respectively.

Expected behaviour

As set previously via Trac frontend admin, the default values should be "Unknown" for both fields.

Change History (6)

comment:1 Changed 6 years ago by trev

This shouldn't be set in the frontend but rather in the trac.ini we deploy:

default_component = Unknown
default_priority = Unknown
default_resolution = fixed
default_type = defect
Last edited 6 years ago by trev (previous) (diff)

comment:2 Changed 6 years ago by trev

  • Cc trev added

comment:3 Changed 6 years ago by trev

  • Priority changed from Unknown to P2

comment:4 Changed 6 years ago by philll

Setting those defaults in the config file means we have to change it every time we rename the vaue. As the frontend admin offers this possibility as well as setting the default database-wise, I would recommend not using the config file to avoid confusion.

comment:5 Changed 6 years ago by trev

The frontend doesn't set this in the database but rather in trac.ini - the very settings I listed.

comment:6 Changed 6 years ago by philll

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.