Concourse Feedback

Summary Idea Name:
Bidirectional Syncing of Planned Dates to Address User Confusion and Admin Overhead

Description:
Implement automated, bidirectional synchronization specifically between Concourse’s planned date fields (even if differently named) and Jira’s Planned Start Date and Planned End Date fields. Currently, Jira PMO administrators manage automated notifications triggered when the JSM engagement record’s Planned End Date passes. Engagement Points of Contact (POCs) receive automated emails prompting them to confirm an updated planned end date or archival status. Once confirmed, Jira admins must manually update the dates in Jira, as only admins have the permission to modify Jira engagement records.

This manual step has caused confusion and frustration, as Engagement POCs frequently respond to automated emails indicating they have already updated the planned end date in Concourse, assuming it would automatically sync to Jira. The lack of synchronization creates additional administrative overhead and misunderstanding among users. It could also cause unexpected closure of Jira engagements earlier than expected if there are automations for closure on the Jira side if an end date is updated in Concourse but not synced to Jira Cloud. O

Implementing this automated bidirectional syncing would significantly improve user experience, eliminate confusion, and reduce administrative burden.

Area of Feedback:
Integration, Workflow Automation, Project Administration, User Experience, and Data Consistency

Perceived Impact:
High (Significantly reduces confusion, eliminates unnecessary manual steps, and enhances user satisfaction.)

User Pain Points:

• Engagement POCs mistakenly believe updating dates in Concourse automatically updates Jira, causing confusion and frustration.

• Additional manual intervention required by Jira administrators, creating administrative overhead and potential delays.

• Increased communication overhead when clarifying discrepancies in dates between systems.

Feature Suggestions:

• Automate bidirectional synchronization between Concourse's planned date fields and Jira’s Planned Start Date and Planned End Date fields.

• Clearly map differently named planned date fields between Concourse and Jira to ensure accuracy and reliability.

Prioritization Rationale:

• User Value: High improvement in user experience by eliminating confusion and reducing unnecessary manual communication.

• Business Impact: Reduces administrative overhead, ensures consistent data across platforms, and improves overall operational efficiency.

• Technical Feasibility: Medium (involves field mapping, synchronization logic, permissions management, and API integrations).

• Urgency: High (Immediate improvement to address ongoing user frustrations and operational inefficiencies).