Adeptus is a simplistic issue, task, and idea-tracking application for personal projects.
It's a handy tool that I've found to be convenient for my personal projects such as reZonator, Spectrum, Procyon, Adeptus itself, and many others.
Adeptus manages the project's issues, storing them in a single SQLite database (plus one single folder for attachments). It intentionally doesn't use any backend server; you are free to choose your favored sync service, like Dropbox or Google Drive, to share the database between your working machines.
Apart from textual description, issues contain several dictionary properties, like “Category” or “Severity”; possible values can be configured for every database independently according to particular projects' needs. (TODO: add issue tags like in GitHub). Issues also can have attachments like example files or screenshot images. Issues can have relations to other issues.
The main window with the issue table, filter panel, and filter presets menu:
An issue page with a detailed description, pasted image, relations panel, and changes history:
A dictionary editor for the “Severity” property and how you can add a new value for the property:
Prerequisites: Visual Studio Community, CMake, vcpkg, optionally Qt Creator.
Clone the repository
git clone https://github.com/orion-project/adeptusUpdate submodules:
cd adeptus
git submodule init
git submodule updateNote, that submodules are in 'detached head' state by default.
Build:
# Shared libs build
mkdir build
cd build
cmake .. -DCMAKE_TOOLCHAIN_FILE=%VCPKG_ROOT%/scripts/buildsystems/vcpkg.cmake -DUSE_VCPKG_QT=ON
# Static libs build
mkdir build_static
cd build_static
cmake .. -DCMAKE_TOOLCHAIN_FILE=%VCPKG_ROOT%/scripts/buildsystems/vcpkg.cmake -DUSE_VCPKG_QT=ON -DVCPKG_TARGET_TRIPLET=x64-windows-static
# Regenerate adeptus.vcxproj
# Normally should be done automatically, but can be usefull to run manually
# in case of build issues because of configuration mismatch,
# e.g. when switching between shared and static builds
cmake -S .. -B .
# Build in debug mode, results will be in build*/Debug
cmake --build .
# Build in release mode, results will be in build*/Release
cmake --build . --config Release

