Concourse & Jira DC Portal

Put Simply Statement:
Let admins create, track, and select estimate versions for flexible, auditable estimation

create a full version and iteration, log and tracking history by admin

Why it Matters:
Supports consistent, quick and ideally iterative sales and delivery cycles

Allows for safer and quicker model updates (i.e. want to add a new team the Admin can duplicate an existing version and then work on it over time with other admins while the model is not public)

Reduces risk of data loss, and enables robust audit trails for compliance and learning.

What’s Needed:

• Backend logic for storing version history

  • Ability to delete versions, duplicate versions, select "Active" version

    • Restrictions in deleting

• Backend logic for storing iterative history

  • GUID tracking, session tracking, etc

• UI for viewing and reverting to previous versions.

• Notifications for major version changes.

  • question - in the admin or user section?

• Early ACs:

  • UI to be able to view all changes to estimates are tracked as versions.

    • big question - do you mean all changes for an ESTIMATE or for an Estimation Model

  • UI to be able to select your Estimation Model and view active Version

    • Additional tabs for history views and to view versions available

      • As I'm typing this out I'm wondering if we need even more permission types in ePro

  • Admins can view a history of changes and revert as needed.

    • Do we want like "block" reversion i.e. revert all changes made by GUIDXXX from X to Y range? and various other options?

  • Version metadata (who, what, when) is accessible.

    • Do we want reversions based on this