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

Increase DVCS connector limit on fetching commits into JIRA issues

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Increase DVCS connector limit on fetching commits into JIRA issues. Currently, it is set to 401 commits which is blocking JIRA users from getting the information.

            [JSWSERVER-14443] Increase DVCS connector limit on fetching commits into JIRA issues

            Thank you Ben.

            The suggested commit search yields all the commits, as expected.

            Pieter Rautenbach added a comment - Thank you Ben. The suggested commit search yields all the commits, as expected.

            Hi pieter3 we are still looking into possible solutions. As an interim you can try out the bitbucket commit search i.e. something like this page - https://bitbucket.org/atlassian/jira-dvcs-connector/commits/all?search=FUSE-297

            We will update this ticket when we finish our investigation.

            Benjamin Morgan (Inactive) added a comment - Hi pieter3 we are still looking into possible solutions. As an interim you can try out the bitbucket commit search i.e. something like this page - https://bitbucket.org/atlassian/jira-dvcs-connector/commits/all?search=FUSE-297 We will update this ticket when we finish our investigation.

            We need some feedback on this issue please, even if it's just that you are still investigating.

            Pieter Rautenbach added a comment - We need some feedback on this issue please, even if it's just that you are still investigating.

            Hi Ben, we need advice on how to increase this limit on a JIRA OnDemand instance.

            Pieter Rautenbach added a comment - Hi Ben, we need advice on how to increase this limit on a JIRA OnDemand instance.

            Thank you for the information – it's good to know there is such an option. However, I don't think I can set this myself on a online/cloud JIRA instance. Please advise.

            Pieter Rautenbach added a comment - Thank you for the information – it's good to know there is such an option. However, I don't think I can set this myself on a online/cloud JIRA instance. Please advise.

            We implemented a limit of 401 for performance and stability reasons, there is a system property that you can override if you want to increase the number of commits returned.

            Set 'dvcs.connector.max.entities.per.key' to an integer value and that will be the new limit that is applied. Be warned that because there is no pagination of the results you may find this can cause your JIRA to have an exception if there are too many commits against an issue.

            Benjamin Morgan (Inactive) added a comment - We implemented a limit of 401 for performance and stability reasons, there is a system property that you can override if you want to increase the number of commits returned. Set 'dvcs.connector.max.entities.per.key' to an integer value and that will be the new limit that is applied. Be warned that because there is no pagination of the results you may find this can cause your JIRA to have an exception if there are too many commits against an issue.

            Refer to JST-155423 for the prior investigation.

            Pieter Rautenbach added a comment - Refer to JST-155423 for the prior investigation.

            I don't believe there should be any limit. I assume the performance constraint exists because these commits are read as a single batch, instead of small incremental batched updates, otherwise this wouldn't be a problem.

            The trouble is that this particular issue on JIRA is an epic (in terms of issue type), so it is reasonable to expected that there could be several hundred commits. We now loose information in terms of tracking our progress, and the ability to report to our clients.

            Pieter Rautenbach added a comment - I don't believe there should be any limit. I assume the performance constraint exists because these commits are read as a single batch, instead of small incremental batched updates, otherwise this wouldn't be a problem. The trouble is that this particular issue on JIRA is an epic (in terms of issue type), so it is reasonable to expected that there could be several hundred commits. We now loose information in terms of tracking our progress, and the ability to report to our clients.

              Unassigned Unassigned
              mfahd Fahd
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: