Pages on core Redmine features that most implementations configure first: trackers and workflows, issue creation by email, and time tracking.
Designing Redmine trackers, statuses and role-based workflows: who may move which issue type between which statuses, read-only and required fields per status, and keeping the model simple enough to maintain.
Turning email into Redmine issues and notes: mail server forwarding versus IMAP or POP3 polling, handling unknown senders, keyword overrides for project and tracker, and automatic watchers from To and Cc.
Setting up Redmine time tracking for billing and capacity: activities, logging from issues and commit messages, estimates, and building spent time reports for projects and clients.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.