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

Issues raised with Bonfire do not show up on GreenHopper Rapid Board

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Resolved Locally
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • None
    • None

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      This was found on http://ecosystem.atlassian.net by jgordinier.

      It is reported that certain issues, which were raised with Bonfire, are not appearing on the SF Ecosystem Rapid Board.

      An example of such an issue is UPM-2285. It appears in the search results when viewing the filter backing the board in Issue Navigator, but it does not appear on the board.

      I have checked the following common causes:

      • Status mapping - is Open status
      • Sprint and Rank field configurations - all normal
      • Empty Sprint field
      • No active filters

      What's interesting is that, when viewing the issue from View Issue page, if I choose the 'Go To Agile Board' operation, it attempts to go to the board, only to not find the issue (select it) once it gets there. Normally, when an issue does not appear on a board, the operation will fail.

      Another interesting fact is that, once the issue is Ranked To Top/Bottom from View Issue page, it suddenly appears on the board. So you would think that it might be an indexing issue. But if I do a simple edit of the issue's description, this does not solve the problem. So it could be a problem with the rank index.

      I do not have access to the logs to check what's going on – this will be my next port of call.

      Workaround

      Bump the Query Result Limit on ecosystem.atlassian.net. You can safely bump it to 1500-2000; I imagine setting it to ~5000 wouldn't cause too much havoc;

      Refine your board filter (or create a new board) to reduce the number of issues that appear in your backlog. One could argue that having ~5,000 issues in a backlog is not very manageable.

            [JSWSERVER-5914] Issues raised with Bonfire do not show up on GreenHopper Rapid Board

            JerryA added a comment -

            thanks for the sleuthing. and thanks for filing related tickets around messaging this stuff to the end user. we were truly perplexed.

            JerryA added a comment - thanks for the sleuthing. and thanks for filing related tickets around messaging this stuff to the end user. we were truly perplexed.

            Michael Tokar added a comment -

            jgordinier, jkodumal: the workaround for the time being would be to either:

            • Bump the Query Result Limit on ecosystem.atlassian.net. You can safely bump it to 1500-2000; I imagine setting it to ~5000 wouldn't cause too much havoc;
            • Refine your board filter (or create a new board) to reduce the number of issues that appear in your backlog. One could argue that having ~5,000 issues in a backlog is not very manageable.

            Michael Tokar added a comment - jgordinier , jkodumal : the workaround for the time being would be to either: Bump the Query Result Limit on ecosystem.atlassian.net. You can safely bump it to 1500-2000; I imagine setting it to ~5000 wouldn't cause too much havoc; Refine your board filter (or create a new board) to reduce the number of issues that appear in your backlog. One could argue that having ~5,000 issues in a backlog is not very manageable.

            Michael Tokar added a comment -

            I have discovered the cause of the problem.

            There is a setting in GreenHopper's Configuration page ( Admin > Plugins > GreenHopper > GreenHopper Configuration ) called Query Result Limit:

            Query Result Limit

            Some GreenHopper requests, such as cross-project charts, query many thousands of issues. If these requests present a performance issue for your JIRA instance you may wish to limit the number of issues queried in any one request. Users will be notified if their request exceeds the issue limit.

            This setting is set on ecosystem.atlassian.net to 500 issues. For better or worse, this setting also applies to Rapid Boards, in addition to Classic Boards.

            So the problem here is, issues that appear "invisible" on the SF Ecosystem board are just being filtered out by this limit.

            Work Mode does warn the user when issues have been filtered out due to the limit being exceeded, albeit the messaging does not render very nicely at the moment, and does not show accurately depending on which "swimlane strategy" is chosen. But with the SF Ecosystem board, these messages aren't being shown because it is a Scrum board, and the number of issues returned in Work Mode is less than the limit.

            Plan Mode on the other hand does not show this messaging, despite the limit being applied (you can count the number of rows in the Backlog and you will see that it caps out at 500).

            This "feature" is a bit of a forgotten feature; we need to figure out how to best offer limiting, and how to notify users when it is in effect.

            I will raise some separate bugs around this addressing each individual problem.

            Michael Tokar added a comment - I have discovered the cause of the problem. There is a setting in GreenHopper's Configuration page ( Admin > Plugins > GreenHopper > GreenHopper Configuration ) called Query Result Limit : Query Result Limit Some GreenHopper requests, such as cross-project charts, query many thousands of issues. If these requests present a performance issue for your JIRA instance you may wish to limit the number of issues queried in any one request. Users will be notified if their request exceeds the issue limit. This setting is set on ecosystem.atlassian.net to 500 issues. For better or worse, this setting also applies to Rapid Boards, in addition to Classic Boards. So the problem here is, issues that appear "invisible" on the SF Ecosystem board are just being filtered out by this limit. Work Mode does warn the user when issues have been filtered out due to the limit being exceeded, albeit the messaging does not render very nicely at the moment, and does not show accurately depending on which "swimlane strategy" is chosen. But with the SF Ecosystem board, these messages aren't being shown because it is a Scrum board, and the number of issues returned in Work Mode is less than the limit. Plan Mode on the other hand does not show this messaging, despite the limit being applied (you can count the number of rows in the Backlog and you will see that it caps out at 500). This "feature" is a bit of a forgotten feature; we need to figure out how to best offer limiting, and how to notify users when it is in effect. I will raise some separate bugs around this addressing each individual problem.

            JerryA added a comment -

            it was actually two opperations:

            1. first I attempted to change "rank" which just had a checkbox (no box to input value)
            2. I selected rank and hit change

            nothing happened...

            so, I again selected all design improvements component issues (`115 issues)
            1. bulk edit
            2. selected rank and rank [obsolete], the latter of which did have an input box
            3. put the number 1 in the input box
            4. saved

            again, nothing happened...
            nothing was broken on the board in total yesterday, only my issues were still missing (anything filed in bonfire)
            —

            today:

            • went through each issue, one by one, hit rank to bottom
            • went back to board, my design quick filter... had lost the only 40 that were there
            • now none of my issues appear...

            john says his issues have now also disappeared... four out of about 84 still appear...
            tried reindexing, did not work

            JerryA added a comment - it was actually two opperations: 1. first I attempted to change "rank" which just had a checkbox (no box to input value) 2. I selected rank and hit change nothing happened... so, I again selected all design improvements component issues (`115 issues) 1. bulk edit 2. selected rank and rank [obsolete] , the latter of which did have an input box 3. put the number 1 in the input box 4. saved again, nothing happened... nothing was broken on the board in total yesterday, only my issues were still missing (anything filed in bonfire) — today: went through each issue, one by one, hit rank to bottom went back to board, my design quick filter... had lost the only 40 that were there now none of my issues appear... john says his issues have now also disappeared... four out of about 84 still appear... tried reindexing, did not work

            Michael Tokar added a comment -

            Perhaps also relevant: I had attempted before to set rank on the design improvements tickets with bulk issue change... i changed rank and something called "rank [obsolete]"... but did not see any changes reflected. This was yesterday.

            Hi Jerry,

            Can you walk me through what happened here? So I'm assuming you did something like this:

            1. Open Issue Navigator and search for your issues
            2. Use the Bulk Change operation
            3. Choose Bulk Edit
            4. Select some "rank" fields
            5. Enter a value?
            6. Submit?

            Does that sound about right?

            Michael Tokar added a comment - Perhaps also relevant: I had attempted before to set rank on the design improvements tickets with bulk issue change... i changed rank and something called "rank [obsolete] "... but did not see any changes reflected. This was yesterday. Hi Jerry, Can you walk me through what happened here? So I'm assuming you did something like this: Open Issue Navigator and search for your issues Use the Bulk Change operation Choose Bulk Edit Select some "rank" fields Enter a value? Submit? Does that sound about right?

            JerryA added a comment -

            Perhaps also relevant: I had attempted before to set rank on the design improvements tickets with bulk issue change... i changed rank and something called "rank [obsolete]"... but did not see any changes reflected. This was yesterday.

            JerryA added a comment - Perhaps also relevant: I had attempted before to set rank on the design improvements tickets with bulk issue change... i changed rank and something called "rank [obsolete] "... but did not see any changes reflected. This was yesterday.

            JerryA added a comment -

            The plot thickens:

            • I ranked to bottom each issue INDIVIDUALLY (115 issues) with the component design improvements, in an attempt to get them to show on my quick filter
            • After I did so, NONE OF THEM showed on the board
            • jkodumal then found issues were missing from the ENTIRE board... about 80 issues (outside of mine)
            • Re-indexing did not help

            JerryA added a comment - The plot thickens: I ranked to bottom each issue INDIVIDUALLY (115 issues) with the component design improvements, in an attempt to get them to show on my quick filter After I did so, NONE OF THEM showed on the board jkodumal then found issues were missing from the ENTIRE board... about 80 issues (outside of mine) Re-indexing did not help

              Unassigned Unassigned
              mtokar Michael Tokar
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: