The Import/Export tool is a generic framework to import and export objects like tickets or config items in several formats like CSV or XML.
active 2023-08-24 → 2024-12-14 (UTC)
Complete coverage26,371 / 26,371 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-17 (UTC)
Events
277
Pushes
252
Pull requests
1
Issues
8
Stars
0
Forks
1
Activity over time
Daily event counts in the loaded window
Line chart, 479 days from 2023-08-24 to 2024-12-14. Pushes: 252 total, peak 14 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 8 total, peak 4 in a day. Comments: 15 total, peak 4 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| otobo-bot | 237 | 237 | 0 | 0 |
| bschmalhofer | 28 | 14 | 1 | 9 |
| laiminhtrung1997 | 4 | 0 | 0 | 3 |
| stefanhaerter | 4 | 0 | 0 | 3 |
| svenoe | 3 | 1 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#6stefanhaerter2024-10-30 10:25The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue#6stefanhaerter2024-10-30 10:25The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6stefanhaerter2024-10-30 06:09The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6bschmalhofer2024-10-29 16:23The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6stefanhaerter2024-10-29 12:32The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6bschmalhofer2024-08-30 09:30The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#7bschmalhofer2024-08-30 09:28Enable cache configurations as default after import is done.
- Pull request#7bschmalhofer2024-08-30 09:28
- Issue comment#7bschmalhofer2024-08-30 08:59Enable cache configurations as default after import is done.
- Issue comment#4bschmalhofer2024-08-28 10:50Add JSON as an output format
- Issue#4bschmalhofer2024-08-28 10:50Add JSON as an output format
- Issue comment#1bschmalhofer2024-08-28 10:47Add a README.md file
- Issue#1bschmalhofer2024-08-28 10:47Add a README.md file
- Issue comment#2bschmalhofer2024-08-28 10:45Remove duplicate copyright notes
- Issue#2bschmalhofer2024-08-28 10:45Remove duplicate copyright notes
- Issue comment#3bschmalhofer2024-08-28 10:43Convert the test scripts to RegisterOM or RegisterDriver
- Issue#3bschmalhofer2024-08-28 10:43Convert the test scripts to RegisterOM or RegisterDriver
- Issue comment#6laiminhtrung19972024-08-25 08:56The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6bschmalhofer2024-08-24 08:08The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6laiminhtrung19972024-08-24 04:42The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue comment#6laiminhtrung19972023-11-21 04:49The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue#6laiminhtrung19972023-11-20 11:54The message "OTOBO Daemon is not running." always pops up after the user imports the CSV file in Import/Export Management.
- Issue#5svenoe2023-08-28 06:15Improve search data storing in DB. (Possibly breaking change for customizations!)
- Issue#5svenoe2023-08-28 06:03Improve search data storing in DB. (Possibly breaking change for customizations!)
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.