Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    COMPASS-141Consider changing Deployment Frequency calculations
  2. Suggestion
    COMPASS-140Ability for Compass to manage GitHub - Jira Issues
  3. Suggestion
    COMPASS-95Please develop a dedicated Mobile app for Compass Operation alerts, which does not require a JSM license to use.
  4. Suggestion
    COMPASS-89Add GitLab support for templates
  5. Suggestion
    COMPASS-101Support for Gitlab Dedicated/Self hosted
  6. Suggestion
    COMPASS-24Support for Monorepos in Compass
  7. Suggestion
    COMPASS-133Integration support for Jenkins with Compass
  8. Suggestion
    COMPASS-127Request for 2LO OAuth for Compass APIs
  9. Suggestion
    COMPASS-27Support root org token for GitLab auth
  10. Suggestion
    COMPASS-70Add support for more Component types in Grapqhl API query (Component creation)
  11. Suggestion
    COMPASS-137Allow discovery and management of components within repositories with multiple levels of nested directories for SelfHosted SCM Platform
  12. Suggestion
    COMPASS-13Integration between Compass and Bitbucket Data Center
  13. Suggestion
    COMPASS-14Enable cross-site use of Compass + JSW
  14. Suggestion
    COMPASS-21Ability to auto-connect and identify components in Statuspage
  15. Suggestion
    COMPASS-37Map the deployment event name in Compass using the same configuration of Jira
  16. Suggestion
    COMPASS-114App/Tools to integrate Backstage.io with Compass
  17. Suggestion
    COMPASS-106Ability to send annoucement notifications to Slack/MS Teams
  18. Suggestion
    COMPASS-72Enhance Flexibility of Compass Component Overview Area
  19. Suggestion
    COMPASS-48Allow exporting of component lists with all or selected fields based on display to excel or CSV
  20. Suggestion
    COMPASS-82Ability to save a custom view over which columns are visible in the component view.
  21. Suggestion
    COMPASS-10Include pagination to the Teams page in Compass
  22. Suggestion
    COMPASS-28Read-only user access
  23. Suggestion
    COMPASS-46Ability to bulk edit custom fields via UI
  24. Suggestion
    COMPASS-103Request for Terraform provider for Compass
  25. Suggestion
    COMPASS-128Ability to set specific API Token Scope for Compass endpoints
  26. Suggestion
    COMPASS-86Capability to add JSM on-call links to Compass component on-call sections.
  27. Suggestion
    COMPASS-125Admin Control Over Contact Methods and Do Not Disturb Settings
  28. Suggestion
    COMPASS-32User Activity Audit Log for Compass
  29. Suggestion
    COMPASS-6IP allowlist
  30. Suggestion
    COMPASS-97Ability to have a custom dependency tracker that isn't limited to a specific package type
  31. Suggestion
    COMPASS-61Add support for custom component types in Gitlab Forge App Importer
  32. Suggestion
    COMPASS-62Display custom component type in Jira Software
  33. Suggestion
    COMPASS-38Ability to mass import select field options via CSV import
  34. Suggestion
    COMPASS-71Ability to turn off/disable notifications when new components are created
  35. Suggestion
    COMPASS-75Capability to prevent or reject component creation or import if a duplicate name already exists.
  36. Suggestion
    COMPASS-85Support depends_on relationship in the CSV importer
  37. Suggestion
    COMPASS-138Enable Compass to support integration with GitLab on-premise instances that require proxy configuration
  38. Suggestion
    COMPASS-134Integration support for Datadog with Compass
  39. Suggestion
    COMPASS-69Ability to add Compass Business Stakeholders
  40. Suggestion
    COMPASS-131Markdown support on Compass
  41. Suggestion
    COMPASS-108Ability to enable data residency for Compass
  42. Suggestion
    COMPASS-124Display non-production deployments (e.g., DEV and TEST environments) in the activity view under Deployments, as they are currently omitted.
  43. Suggestion
    COMPASS-36Explore the possibility of not requiring Owner role for Group Token as part of Gitlab Integration
  44. Suggestion
    COMPASS-119Ability to manually refresh and/or set refresh rate for JQL metrics
  45. Suggestion
    COMPASS-118Add sections to the Compass components dropdown in Jira Work Item View
  46. Suggestion
    COMPASS-112Support for defining scorecard passing criteria at the component level.
  47. Suggestion
    COMPASS-116Integration support for Kubernetes (K8s) with Compass
  48. Suggestion
    COMPASS-117Update Needed for On-Call Scorecard Criterion
  49. Suggestion
    COMPASS-113Enhance Metrics Visibility and Aggregation Across Teams
  50. Suggestion
    COMPASS-93Ability to View Metrics Over Time
Refresh results
1 2 3Next >>
1 of 104
Uploaded image for project: 'Compass'
  1. Compass
  2. COMPASS-141

Consider changing Deployment Frequency calculations

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Health - Metrics
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, the deployment frequency calculation is as explained below,

      • If a component suddenly has 5 deploys in the most recent week, and none in the previous weeks, we only found deployment events in 1 week.
      • 5 deploys / 1 week with deployment activity = average of 5 deploys per week.
      • The component only started getting deploys in the last week(in this example), so the frequency is calculated as below,
      Number of deployments / Number of weeks between the oldest and newest event (plus one)
      
      5/1 = 5 deploys per week
      

      Instead, it would be good to have the calculation as below,

      All the deployments in the last 4 weeks/4
      
      ## as per the above example, it would be, 
      5/4 = 1.25 deploys per week. 
      

          Form Name

            • All
            • Comments
            • Work Log
            • History
            • Activity

            Cornelia Jeppsson added a comment - 3 hours ago

            Also to clarify further: If a deploy was made 5 weeks ago, that is not included in the calculation, since it does not take into account any deployments made over 28 days ago. This means that if a service is deployed 5 times on one day every second month, the deployment frequency will either show 0 deploys/week or 5 deploy/week, and never the actual average of 1.25 deploys/week.

            Cornelia Jeppsson added a comment - 3 hours ago Also to clarify further: If a deploy was made 5 weeks ago, that is not included in the calculation, since it does not take into account any deployments made over 28 days ago. This means that if a service is deployed 5 times on one day every second month, the deployment frequency will either show 0 deploys/week or 5 deploy/week, and never the actual average of 1.25 deploys/week.

              Unassigned Unassigned
              a3002c6cc185 Swetha Boyapati
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                2 hours ago
                Updated:
                2 hours ago
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian