Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21256

Intermittently Jira development panel does not show commit option for FishEye Repositories.

      Issue Summary

      Whenever FishEye User Checkin code, the commit information is not updated in Development Panel of Jira. This issue is intermittent and randomly occurring on newer commits.

      Steps to Reproduce

      Issue cannot be reproduced since it is intermittent and randomly occurring on different Jira tickets.

      Observation:

      • User Checkin the code from FishEye Repository:
        <removed-screenshot-as-per-customer-request>
      • Dev Panel in Jira fails to load the builds:
        <removed-screenshot-as-per-customer-request>
      • The issue is related to older bug: JSWSERVER-16760 where the issue was suspected to be a problem with timestamps in Jira cache and this issue was marked as Fixed in 8.x versions. However, the customer still face this issue in the following version:
        • Jira: 8.20.2
        • FishEye: 4.8.8

      Expected Results

      The commits events from FishEye should be updated correctly in the Jira issue.

      Actual Results

      The Development Panel shows 2 builds failed:
      <removed-screenshot-as-per-customer-request>

      Workaround

      Manually delete the fusion cached data related to the issue in the Jira database. Follow the steps mentioned in this bug: FE-6953

            [JSWSERVER-21256] Intermittently Jira development panel does not show commit option for FishEye Repositories.

            Brent P made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]

            Brent P added a comment -

            Unfortunately, we're not able to reproduce this bug with the information provided or based on information from the support case where this originated.

            I'd encourage affected customers to get in touch with support who can rope in developers to investigate more.

            Brent P added a comment - Unfortunately, we're not able to reproduce this bug with the information provided or based on information from the support case where this originated. I'd encourage affected customers to get in touch with support who can rope in developers to investigate more.

            Hi 0abfcbc3365d - We have validated that all the attachments are removed from the ticket and as for Support ticket: GHS-238352 the attachments will be automatically archived

            Mohan C S (Inactive) added a comment - Hi 0abfcbc3365d - We have validated that all the attachments are removed from the ticket and as for Support ticket: GHS-238352 the attachments will be automatically archived
            Mohan C S (Inactive) made changes -
            Attachment Original: image-2022-02-16-21-16-12-437.png [ 416753 ]
            Mohan C S (Inactive) made changes -
            Attachment Original: image-2022-02-16-21-16-09-850.png [ 416754 ]
            Mohan C S (Inactive) made changes -
            Attachment Original: image-2022-02-16-21-15-35-334.png [ 416756 ]
            Mohan C S (Inactive) made changes -
            Attachment Original: image-2022-02-16-21-15-12-384.png [ 416755 ]

            Hi Mohan,

            I can see those screenshots on ticket's attachments section without login into the application. Please, validate and removed from this as well.

             

            mahesh.shinde added a comment - Hi Mohan, I can see those screenshots on ticket's attachments section without login into the application. Please, validate and removed from this as well.  

            Hi 0abfcbc3365d, - We have removed the screenshots per request but it has been shared it with our Internal Staffs.

            Mohan C S (Inactive) added a comment - Hi 0abfcbc3365d , - We have removed the screenshots per request but it has been shared it with our Internal Staffs.
            Mohan C S (Inactive) made changes -
            Description Original: h3. Issue Summary

            Whenever FishEye User Checkin code, the commit information is not updated in Development Panel of Jira. This issue is intermittent and randomly occurring on newer commits.
            h3. Steps to Reproduce

            Issue cannot be reproduced since it is intermittent and randomly occurring on different Jira tickets.
            h4. Observation:
             * User Checkin the code from FishEye Repository:
            !image-2022-02-16-21-16-12-437.png|width=528,height=67!
             * Dev Panel in Jira fails to load the builds:
            !image-2022-02-16-21-15-35-334.png|width=529,height=266!
             * The issue is related to older bug: JSWSERVER-16760 where the issue was suspected to be a problem with timestamps in Jira cache and this issue was marked as Fixed in 8.x versions. However, the customer still face this issue in the following version:
             ** Jira: 8.20.2
             ** FishEye: 4.8.8

            h3. Expected Results

            The commits events from FishEye should be updated correctly in the Jira issue.
            h3. Actual Results

            The Development Panel shows build failed:
            !image-2022-02-16-21-15-12-384.png!
            h3. Workaround

            Manually delete the fusion cached data related to the issue in the Jira database. Follow the steps mentioned in this bug: FE-6953
            New: h3. Issue Summary

            Whenever FishEye User Checkin code, the commit information is not updated in Development Panel of Jira. This issue is intermittent and randomly occurring on newer commits.
            h3. Steps to Reproduce

            Issue cannot be reproduced since it is intermittent and randomly occurring on different Jira tickets.
            h4. Observation:
             * User Checkin the code from FishEye Repository:
            _<removed-screenshot-as-per-customer-request>_
             * Dev Panel in Jira fails to load the builds:
            _<removed-screenshot-as-per-customer-request>_
             * The issue is related to older bug: JSWSERVER-16760 where the issue was suspected to be a problem with timestamps in Jira cache and this issue was marked as Fixed in 8.x versions. However, the customer still face this issue in the following version:
             ** Jira: 8.20.2
             ** FishEye: 4.8.8

            h3. Expected Results

            The commits events from FishEye should be updated correctly in the Jira issue.
            h3. Actual Results

            The Development Panel shows 2 builds failed:
            _<removed-screenshot-as-per-customer-request>_
            h3. Workaround

            Manually delete the fusion cached data related to the issue in the Jira database. Follow the steps mentioned in this bug: FE-6953

              Unassigned Unassigned
              af0461e84050 Mohan C S (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: