Concourse & Jira DC Portal


Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.


For immediate technical support, please follow this guidance to open a Service Now ticket.

Automate creation of recurring work items

Users should be able to select the cadance at which they can create work items. Example automate the creation of Weekly Status Report task or subtask for the duration of the engagement instead of having to manually create those work items for each week for the duration of the engagment as some Managed Services engagement go for 3-5 years.

Put Simply:
Finalized scopes in Concourse often become the foundation for client contracts, such as Statements of Work (SoWs). By integrating Concourse with Icertis, we can streamline the process of contract generation—ensuring that accurate, structured scope data flows directly into legal documentation without rework or manual transfer.

Why It Matters:

  • Supports contractual alignment: Ensures that what’s scoped and agreed upon is what gets signed—minimizing disconnects between delivery and contracts.

  • Improves efficiency: Reduces time and manual effort needed to draft SoWs and other documents in Icertis.

  • Boosts accuracy: Prevents translation errors and rekeying mistakes that often occur when moving between systems.

  • Enables scale: Helps standardize how scopes transition into contracts across practices, regions, and project types.

What’s Needed:

  • API integration between Concourse and Icertis to transmit finalized scope data.

  • Mapping of Concourse scope fields (e.g., offerings, deliverables, workstreams) to Icertis contract fields.

  • UI element in Concourse to trigger "Send to Icertis" action once scope is finalized.

  • Permissions logic to control who can initiate the integration.

  • Support for version control and re-sync if scope changes after initial push.

  • Audit trail to track when and what was sent to Icertis.


  • Guest
  • Feb 6 2025
  • Not started