Important: Status Mapping Logic (MS Teams to Jira CrewRadar)
Dear Jury Members,
Please evaluate the integration based on the status mapping logic defined in the table below. This logic was specifically developed to bridge Microsoft Teams presence with Jira workflows.
Status Mapping Table:
Developer Notes & Design Choices
The current mapping follows a specific logic chosen for the hackathon:
- Workflow Optimization: These mappings are designed to fit a specific operational workflow (e.g., treating 'Do Not Disturb' as 'Available') to ensure that urgent ticket assignments are not missed.
- Hackathon Prototype: A hardcoded approach was intentionally chosen to build a fast, stable, and working solution within the competition timeframe.
- Organizational Flexibility: I am aware that different organizations may require different mapping logic.
Future Roadmap (Post-Evaluation)
This system is designed to be highly scalable and will be improved after the evaluation phase:
- Configurable UI: I plan to add a user interface (UI) that allows organizations to customize their own mapping rules.
- Enhanced Flexibility: This will make the application flexible for a wider range of professional audiences and different organizational needs.
Please take these design choices into consideration during your testing. Thank you!
Log in or sign up for Devpost to join the conversation.