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

JIRA won't list changeset if commit message contains special character at the beginning

      Premises:

      • JIRA 6.3.9 is integrated with FishEye/Crucible 3.5.1.
      • OAuth is being used as authentication method

      Steps to reproduce:

      1. Commit something using the following commit message:
        - JRA-1 - This is a test
        
      2. Let FishEye incrementally index the repository
      3. In FishEye, it will list that changeset, and clicking the issue key will open the popup with the issue details as usual.
      4. In FishEye, note that searching for JRA-1 returns 15 commits and that commit 85 shows the commit message with a hyphen at the beginning.
      5. In JIRA, clicking the "x commits" link in the development panel will list 14 commits, and commit 85 is not among them:

          Form Name

            [JSWSERVER-14893] JIRA won't list changeset if commit message contains special character at the beginning

            I am also facing the same issue. 

             

            any workaround till this is fixed?

            Krishna Ponnekanti added a comment - I am also facing the same issue.    any workaround till this is fixed?

            Should be higher prio, IMO. It's paramount to understand which changes have been made for an issue.

            Kissenschlachter added a comment - Should be higher prio, IMO. It's paramount to understand which changes have been made for an issue.

            DJ added a comment -

            We are experiencing this same issue in the latest versions of FishEye (4.7.1) & Jira (8.4.1) as well.

            It's been haunting us for a while, but I finally saw the pattern, and then found this and see it's a known bug.

            Sad to see that it isn't getting the attention it should.

            DJ added a comment - We are experiencing this same issue in the latest versions of FishEye (4.7.1) & Jira (8.4.1) as well. It's been haunting us for a while, but I finally saw the pattern, and then found this and see it's a known bug. Sad to see that it isn't getting the attention it should.

              Unassigned Unassigned
              fkraemer Felipe Kraemer
              Affected customers:
              19 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated: