Concourse & Jira Cloud Portal
An activated scope should reflect a snapshot in time and serve as a historical record of what was agreed upon during the pursuit phase and in the SOW to validate what was deployed to a JIRA delivery plan. Today an Activated Scope is being changed to reflect any adjustments to admin portal and no longer reflects what was agreed upon with the client.
Expected Scoping behaviour:
During pursuit phase, and scoping workflow is active, scopes should update to reflect latest and greatest content
Once a scope is activated, that scope is fixed and does not show Admin Portal PDM changes
Hi @James Schulze ! I wanted to provide a quick update: Product and development teams have identified and planned the work. The plan is for this to be completed, for both Building Blocks and Offerings, in the release post-9/1. Please reach out if you have any questions/comments!