Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-14004

Adding an existing access key to another repository returns invalid information on expiry date on the UI

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 8.8.7, 8.9.4, 8.10.4, 8.11.3, 8.12.1, 8.13.0
    • 8.7.0, 8.7.2, 8.7.3, 8.7.4, 8.8.0, 8.8.1, 8.8.2, 8.8.3, 8.8.4, 8.8.5, 8.9.0, 8.9.1, 8.9.2, 8.10.0, 8.10.1, 8.10.2, 8.11.0, 8.11.1
    • Access Keys
    • None

    Description

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Add the access key for repository A and set the expiry days to X days
      2. After two days, add the same access keys for repository A into repository B
      3. The expiry date shown in the UI does not match the expiry date for repository A

      Expected Results

      The expiry date calculated in the UI for repository B should be the same as repository A

      Actual Results

      The expiry date calculated in the UI for repository B mismatch repository A

      Workaround

      There is no workaround, it is just a bug in the UI during calculation of expiry date when adding the access key. Once user click 'Save' button, the expiry date matches with the other repository.

      Attachments

        Issue Links

          Activity

            People

              7adba17237c7 James Adams
              b365a93d7dac Pamara Lim
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: