Details

    • Symptom Severity:
      Severity 3 - Minor
    • Occurrence Factor:
      10%
    • Current Status:
      Hide
      Atlassian Update – 28 May 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 28 May 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      Description

      Hello

      Our company recently start using JIRA and i'm trying to schedule backup.
      As far as I see backup was configured automatically after installation on daily basis at 12:00 AM

      But according to the actual backup files I spot that back up happens twice a day, at 12:00 and at 00:00

      because of not native format (AM/PM) for Europeans - which as i see in reality happen twice a day - I can't set to backup once per day exactly at 00:00, so i decide to use advance option and with crontab format

      if I enter "0 0 * * * ?" and hit "Update" it return to the main "Settings" page and show rule as that:

      "0 0 * * *" - is not every hour, it is must be 00:00

      Also as sub task or suggestion for improvement mentioned in JRA-6152 which already closed, why dont you complete this feature fully? Please allow to switch to 24h format once and for ever in entire portal including back up settings.
      Please complete this feature on 100% and not on 80% as you did!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              briksins Vadims Briksins
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: