Import Data
Send Data to Systems
Last Firebase Sync: Never
Last Oracle Sync: Never
Import Summary
Advanced Data Grid
No data to display. Import from Jira or load a file to begin.
Executive Dashboard
CapEx vs. OpEx Hours
Top 5 Projects by Hours
Team Contribution by Hours
Historical Trend
No data available for reporting. Process a file or select a saved period.
Project Overview
Jira/Tempo APIs to Oracle for CapEx/OpEx
The project aims to integrate Jira and Tempo APIs to extract worklogs and issue information, seamlessly transferring this data into Oracle for accurate Capital Expenditure (CapEx) and Operational Expenditure (OpEx) tracking. By automating the flow of time-tracking and project-related data, the solution ensures precise financial reporting, enhances resource allocation, and streamlines compliance with organizational accounting standards.
Key Objectives
- Automate worklog data extraction from Jira/Tempo
- Accurate CapEx/OpEx categorization
- Seamless Oracle integration
- Real-time financial reporting
- SOX compliance tracking
Data Flow & Criteria
Data Sources
The integration pulls data from two primary sources and combines them for processing.
1. Jira API CSV
Provides issue-level details such as project IDs, summaries, and issue types (Story, Sub-Task, etc.).
Required Fields:
- Key
- Summary
- Resolved
- Status
- Parent
- Parent Name
- Parent Resolution Date
- Started Date (Sub-task worklog first date)
- Oracle Project ID
2. Tempo API CSV
Provides detailed worklog information, including hours, dates, and approval status.
Required Fields:
- Worklog ID
- Key
- Logged
- Date
- Updated
Integration Criteria
Only data meeting the following criteria will be pulled into the system for processing and sending to Oracle.
Jira Issue Data (CapEx)
- Only CapEx subtasks and stories are pulled.
Oracle Project IDfield must not be empty.- Issue must have been updated since the last successful integration run.
- Issue Type must be one of: Story, Sub-Task, Sub-Bug.
Tempo Worklog Data
- Worklog
Approval Statusmust be Approved. - Worklog must have been updated since the last successful integration run.
Special Requirements & Considerations
Start Date Requirement (Tom's Note)
Critical: We need to send a "Start Date" with the subtasks/stories that we are sending to Oracle. Ideally this start date would be the date of the earliest worklog for that issue.
Note: This may need to be populated within Jira, or potentially handled in MuleSoft integration layer.
CapEx/OpEx Categorization
All work must be accurately categorized as either Capital Expenditure (CapEx) or Operational Expenditure (OpEx) for financial reporting compliance.
Oracle Integration
Data must be formatted and validated according to Oracle's financial system requirements before transmission.
SOX Compliance
All data movements and transformations must be logged and auditable for Sarbanes-Oxley compliance requirements.
Technical Implementation Status
✅ Completed Features
- Jira/Tempo API integration framework
- CapEx/OpEx categorization engine
- Oracle payload generation
- Firebase data storage
- Audit trail logging
- Data validation & quality checks
- Cost analysis & reporting
🔄 In Progress / Pending
- Start Date calculation logic
- Advanced trend analysis
- Auto-sync scheduling
- Custom date range reporting
- Enhanced SOX compliance tools
- Oracle API authentication
Task Type Mapping
API Configuration
Used for cost calculations and reporting
Firebase Data Management
Database Statistics
Loading statistics...
Team Access
Each user has their own data storage. To share data across your team:
- Use the same login credentials for team members
- Export and share data backups
- Send data to your central Oracle system
Current User: