| Summary: | Populate list of system preferences when first introduced in Koha database | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Ola Andersson <ola.andersson> | 
| Component: | Database | Assignee: | Bugs List <koha-bugs> | 
| Status: | NEW --- | QA Contact: | Testopia <testopia> | 
| Severity: | enhancement | ||
| Priority: | P5 - low | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Crowdfunding goal: | 0 | 
| Patch complexity: | --- | Documentation contact: | |
| Documentation submission: | Text to go in the release notes: | ||
| Version(s) released in: | Circulation function: | ||
| 
        
          Description
        
        
          Ola Andersson
        
        
        
        
          2024-05-27 07:49:21 UTC
        
       I think maybe not something for the database - documentation should better be kept outside. A pref can also be backported in some cases, which makes it harder to tell when it was first introduced. I think a script generating something from git history similar to what is used for the release notes might be a better way. |