This document contains key information about the Redmine environment structure to help with future issue management and API interactions.
- Default Project: Operations (ID: 1, identifier: "ops")
- Project Status: Active (Status ID: 1)
- Project Visibility: Public
- Created: March 15, 2025
- Last Updated: March 18, 2025
All members have Manager role (Role ID: 3):
- Alex Wilson (ID: 5)
- Morgan Chen (ID: 6)
- Taylor Roberts (ID: 7)
- Jordan Bailey (ID: 8)
- Task - Technical (ID: 1)
- Task - Advisory (ID: 2)
- Deployment (ID: 3)
- Task - Customer (ID: 4)
- Task - Portal (ID: 5)
- DEV (ID: 6)
- Code (ID: 1) - Default tracker
- Feature (ID: 2)
- Support (ID: 3)
Status IDs identified in the system:
- New (ID: 1, is_closed: true)
- In Progress (ID: 2)
- Feedback (ID: 4)
- Done (ID: 5, is_closed: true)
- Cancelled (ID: 6, is_closed: true)
- Backlog (ID: 7, is_closed: true)
- Pipelined (ID: 8)
- Pull Request Reviewers (ID: 2, multiple: true)
- Pull Request Targeted Branches (ID: 3, multiple: true)
- When creating or updating issues, the default tracker is "Code" (ID: 1)
- All issues in the Operations project should have a category assigned
- Work Units (WU) are calculated at 8 hours (1 day) per unit
- Estimated hours should be set in hours (WU × 8)
- In Redmine, start_date and due_date format is "YYYY-MM-DD"
This does not give any useful information, please ignore.
/projects/ops.json- Project details/projects/ops/memberships.json- Project members/projects/ops/issue_categories.json- Issue categories/trackers.json- Available trackers/issues.json?project_id=ops- Issues for Operations project/issues/{issue_id}.json- Specific issue details