Concourse & Jira DC Portal

Description from Hisae:
When we create scope, we would like to re-use(copy from)the scope of other engagement.
It takes much time to create scope properly. Without this feature, we may make mistake to create appropriate scope. It would be helpful especially for similar scope project.

Description from Internal Team:

Put Simply:
Rather than starting from scratch every time, users should be able to reuse scoped work from previous, similar engagements. This feature allows teams to clone an existing engagement’s scope—including deliverables, offering selections, and configurations—and tailor it to new projects.

Why It Matters:

• Drives efficiency: Accelerates scoping by reusing proven setups, especially for repeatable project types (e.g., Oracle, SAP).

• Improves consistency: Helps ensure that key deliverables and configurations aren't missed, and that scopes align across similar projects.

• Reduces user effort: Provides a helpful starting point for users, especially those unfamiliar with the offering catalog.

• Supports scalability: Enables knowledge sharing and standardization across global teams and practices.

• Improves onboarding: New users can learn from existing examples, increasing quality and reducing training overhead.

What’s Needed:

• UI in the scoping wizard to "Start from Previous Engagement".

• Scope cloning logic to copy the key metadata selections of a previous engagement. Not likely a strong path forward to copy the actual work items given those might be stale within the methodology.

• Audit trail and versioning to track what was reused and allow post-clone edits.

• Permissions framework to limit visibility and reuse to authorized engagements.

• Performance optimization to ensure smooth reuse even for large scopes.

Not in Scope:

• Migration of actual deliverables or tasks from one client’s project to another.