We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20976

Commit details missing on development panel in certain issues when sync is performed with Gitlab Repository

      Issue Summary

      The issue is observed with Jira-Gitlab DVCS integration offered with Jira 8.14.0.
      For some issues, Commit details are missing and does not appears on the Development even though Pull requests details are fetched from Gitlab to Jira database.

      Steps to Reproduce

      1. Create an issue in a project (i.e. TST)
      2. Move that issue to another project (i.e. QA)
      3. Create a branch with a title such as 'TST-1 QA-6' and another with 'TST-1'
      4. Perform a sync
      5. There will be a Nullpointer exception error in the logs

      Expected Results

      The sync should not fail with exception and the Commit information should get displayed on the Development panel.

      Actual Results

      The below exception is thrown in the atlassian-jira.log file and commit details are not shown on development panel

      2021-03-02 10:11:29,258+0300 devstatus.dvcs.gitlabselfmanaged:thread-17 ERROR ServiceRunner     [c.a.j.p.devstatus.provider.LoggingDecorator] Call 'summary for [TST-6436, TST-4330, TST-7086]' has thrown an exception2021-03-02 10:11:29,258+0300 devstatus.dvcs.gitlabselfmanaged:thread-17 ERROR ServiceRunner     [c.a.j.p.devstatus.provider.LoggingDecorator] Call 'summary for [TST-6436, TST-4330, TST-7086]' has thrown an exceptionjava.lang.NullPointerException at java.util.AbstractCollection.addAll(AbstractCollection.java:343) at com.atlassian.jira.plugins.dvcs.dao.impl.querydsl.BranchDaoQueryDsl.lambda$addIssuesToBranches$11(BranchDaoQueryDsl.java:233)
      

      Workaround

      • Remove any branches with multiple issue keys in the name

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-20976

            Commit details missing on development panel in certain issues when sync is performed with Gitlab Repository

                Issue Summary

                The issue is observed with Jira-Gitlab DVCS integration offered with Jira 8.14.0.
                For some issues, Commit details are missing and does not appears on the Development even though Pull requests details are fetched from Gitlab to Jira database.

                Steps to Reproduce

                1. Create an issue in a project (i.e. TST)
                2. Move that issue to another project (i.e. QA)
                3. Create a branch with a title such as 'TST-1 QA-6' and another with 'TST-1'
                4. Perform a sync
                5. There will be a Nullpointer exception error in the logs

                Expected Results

                The sync should not fail with exception and the Commit information should get displayed on the Development panel.

                Actual Results

                The below exception is thrown in the atlassian-jira.log file and commit details are not shown on development panel

                2021-03-02 10:11:29,258+0300 devstatus.dvcs.gitlabselfmanaged:thread-17 ERROR ServiceRunner     [c.a.j.p.devstatus.provider.LoggingDecorator] Call 'summary for [TST-6436, TST-4330, TST-7086]' has thrown an exception2021-03-02 10:11:29,258+0300 devstatus.dvcs.gitlabselfmanaged:thread-17 ERROR ServiceRunner     [c.a.j.p.devstatus.provider.LoggingDecorator] Call 'summary for [TST-6436, TST-4330, TST-7086]' has thrown an exceptionjava.lang.NullPointerException at java.util.AbstractCollection.addAll(AbstractCollection.java:343) at com.atlassian.jira.plugins.dvcs.dao.impl.querydsl.BranchDaoQueryDsl.lambda$addIssuesToBranches$11(BranchDaoQueryDsl.java:233)
                

                Workaround

                • Remove any branches with multiple issue keys in the name

                        15c9fc99333a Maciej Sujkowski (Inactive)
                        556084c56f12 Rinish
                        Affected customers:
                        1 This affects my team
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            15c9fc99333a Maciej Sujkowski (Inactive)
                            556084c56f12 Rinish
                            Affected customers:
                            1 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: