Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-1128

Have a way to find issues on or over the per issue limits.

XMLWordPrintable

    • 0
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As the page below, there were limits implemented to issues:

      New Limits

      Comments are limited to 5000 per issue.
      Worklogs are limited to 5000 per issue.
      Attachments are limited to 2000 per issue.
      Linked issues are limited to 2000 per issue. This does not include child issues.
      Remote links are limited to 2000 per issue. This includes:

      • web links
      • Confluence pages
      • links to an external issue on a different Jira instance
      • links to other Atlassian products

      Currently, there's no way to find the affected issues, and users need to rely on emails sent in the first two weeks of March 2024.

      The suggestion is to implement a way to find issues that are about to breach anyone of the limits, maybe by a JQL, a field, automatic comment, etc. So, the users will be able to take necessary actions on these issues.

            [AI-1128] Have a way to find issues on or over the per issue limits.

            Jason Ball made changes -
            Component/s Original: XP - Content Search [ 60997 ]
            Component/s New: Search - Quick Search [ 75293 ]
            Key Original: JRACLOUD-83311 New: AI-1128
            Project Original: Jira Platform Cloud [ 18514 ] New: Atlassian Intelligence [ 23110 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS New: 1

            Andreas Springer (Actonic) added a comment - - edited

            I have just published an article about the current state of the rollout of these issue limits here: https://actonic.de/en/understanding-atlassian-jira-cloud-issue-limits-and-how-to-manage-them/

            Also included in the article is a way to quickly identify and surface issues that are affected by these limits right on your dashboard:

            It's a custom report built in Report Builder, which means its source code can be modified to any requirement you or a client might have (more details in the article):

            This report is not part of the app yet, but you will find a guide on how to add it manually in the article. Or just let me know and I will help you do that.

            Hope this can be helpful to someone!

            Andreas Springer (Actonic) added a comment - - edited I have just published an article about the current state of the rollout of these issue limits here: https://actonic.de/en/understanding-atlassian-jira-cloud-issue-limits-and-how-to-manage-them/ Also included in the article is a way to quickly identify and surface issues that are affected by these limits right on your dashboard: It's a custom report built in Report Builder , which means its source code can be modified to any requirement you or a client might have (more details in the article): This report is not part of the app yet, but you will find a guide on how to add it manually in the article. Or just let me know and I will help you do that. Hope this can be helpful to someone!
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Rodrigo Goulart made changes -
            Description Original: As the page below, there were limits implemented to issues:
             * [Upcoming changes: Introducing per issue limits for list fields in Jira Issues|https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-Introducing-per-issue-limits-for-list-fields-in/ba-p/2468177#:~:text=New%20Limits&text=Worklogs%20are%20limited%20to%205000,limited%20to%202000%20per%20issue.]

            {quote}
            h2. *New Limits*

            Comments are limited to 5000 per issue.
            Worklogs are limited to 5000 per issue.
            Attachments are limited to 2000 per issue.
            Linked issues are limited to 2000 per issue. This does not include child issues.
            Remote links are limited to 2000 per issue. This includes:
             * web links
             * Confluence pages
             * links to an external issue on a different Jira instance
             * links to other Atlassian products{quote}
            Currently, there's no way to find the affected issues, and users need to rely on emails sent in the first two weeks of March 2024.

            The suggestion is to implement a way to find those issues.             		New: As the page below, there were limits implemented to issues:
             * [Upcoming changes: Introducing per issue limits for list fields in Jira Issues|https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-Introducing-per-issue-limits-for-list-fields-in/ba-p/2468177#:~:text=New%20Limits&text=Worklogs%20are%20limited%20to%205000,limited%20to%202000%20per%20issue.]

            {quote}
            h2. *New Limits*

            Comments are limited to 5000 per issue.
            Worklogs are limited to 5000 per issue.
            Attachments are limited to 2000 per issue.
            Linked issues are limited to 2000 per issue. This does not include child issues.
            Remote links are limited to 2000 per issue. This includes:
             * web links
             * Confluence pages
             * links to an external issue on a different Jira instance
             * links to other Atlassian products{quote}
            Currently, there's no way to find the affected issues, and users need to rely on emails sent in the first two weeks of March 2024.

            The suggestion is to implement a way to find issues that are about to breach anyone of the limits, maybe by a JQL, a field, automatic comment, etc. So, the users will be able to take necessary actions on these issues.
            Rodrigo Goulart made changes -
            Description Original: As the page below, there ware limits implemented to issues:
             * [Upcoming changes: Introducing per issue limits for list fields in Jira Issues|https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-Introducing-per-issue-limits-for-list-fields-in/ba-p/2468177#:~:text=New%20Limits&text=Worklogs%20are%20limited%20to%205000,limited%20to%202000%20per%20issue.]

            {quote}
            h2. *New Limits*

            Comments are limited to 5000 per issue.
            Worklogs are limited to 5000 per issue.
            Attachments are limited to 2000 per issue.
            Linked issues are limited to 2000 per issue. This does not include child issues.
            Remote links are limited to 2000 per issue. This includes:
             * web links
             * Confluence pages
             * links to an external issue on a different Jira instance
             * links to other Atlassian products
            {quote}

            Currently, there's no way to find the affected issues, and users need to rely on emails sent in the first two weeks of March 2024.

            The suggestion is to implement a way to find those issues.             		New: As the page below, there were limits implemented to issues:
             * [Upcoming changes: Introducing per issue limits for list fields in Jira Issues|https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-Introducing-per-issue-limits-for-list-fields-in/ba-p/2468177#:~:text=New%20Limits&text=Worklogs%20are%20limited%20to%205000,limited%20to%202000%20per%20issue.]

            {quote}
            h2. *New Limits*

            Comments are limited to 5000 per issue.
            Worklogs are limited to 5000 per issue.
            Attachments are limited to 2000 per issue.
            Linked issues are limited to 2000 per issue. This does not include child issues.
            Remote links are limited to 2000 per issue. This includes:
             * web links
             * Confluence pages
             * links to an external issue on a different Jira instance
             * links to other Atlassian products{quote}
            Currently, there's no way to find the affected issues, and users need to rely on emails sent in the first two weeks of March 2024.

            The suggestion is to implement a way to find those issues.
            SET Analytics Bot made changes -
            Support reference count New: 1
            eneis created issue -

              Unassigned Unassigned
              83c98eb92a41 eneis
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: