Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-16220

Cron schedule displayed in confusing way in scheduled triggers

      Regression as this used to work on earlier releases.

      1. Add scheduled trigger
      2. Edit schedule
      3. Select Cron
      4. Add expression like: 0 55 * ? * *
      5. Done
      6. Shows up properly on display
      7. Save trigger
      8. View trigger - switched to a daily every hour
      9. Edit schedule - Daily selected, every hour, minutes are not shown or editable

      Update: it's just a display issue, underlying cron is saved and interpreted correctly.
      Workaround: switch to cron view to see the actual expression.

            [BAM-16220] Cron schedule displayed in confusing way in scheduled triggers

            Ishwinder Kaur made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Atlassian Update - 9 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.

            Kind regards,
            Bamboo Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 9 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Bamboo Data Center, please check our public roadmap . Kind regards, Bamboo Data Center
            Ishwinder Kaur made changes -
            Labels Original: da-regression onboarding triage-reviewed New: cleanup-seos-fy25 da-regression onboarding triage-reviewed
            Venkata Sateesh Pentela made changes -
            Remote Link Original: This issue links to "BDEV-9901 (Atlassian JIRA Extranet - Special Projects)" [ 113519 ] New: This issue links to "BDEV-9901 (Hello Jira)" [ 113519 ]
            Pawel Skierczynski made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1440963 ] New: JAC Bug Workflow v3 [ 3386249 ]
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 3 New: 2
            Bugfix Automation Bot made changes -
            Support reference count Original: 2 New: 3
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            VICTOR-OSEGHALE (Inactive) made changes -
            Affects Version/s New: 6.3.1 [ 76995 ]

              Unassigned Unassigned
              bob.swift@charter.net Bob Swift
              Affected customers:
              0 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: