-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
6.2.4, 6.3.13.0, 7.4.1, 7.2.12, 7.7.1, 8.13.8, 8.13.9
-
6.02
-
5
-
Severity 3 - Minor
-
3
-
Summary
When navigating to a board after viewing the Agile Wallboard Gadget with a quick filter applied, the quick filter will also be applied to the board without any visible highlighting to show that a quick filter is applied. Clicking on the quick filter itself will unapply the quick filter, although it will now be highlighted as if it were selected.
Steps to Reproduce
- Create a board (Kanban or Scrum)
- Create 4 issues, and assign 3 to yourself. Leave one unassigned or assigned to someone else.
- Create a Dashboard.
- Add the Agile Wallboard Gadget and configure it with the created board and the 'Only My Issues' Quick Filter selected.
- If the board is a scrum board, create and start 1 sprint with all 4 issues in it. Otherwise, skip to the next step.
- View the Dashboard.
- Navigate back to the board.
Expected Results
The board is displayed with no quick filter applied. All 4 issues display.
Actual Results
The board is displayed with the quick filter applied but without any visible evidence that it is (all quick filters unhighlighted). Only the 3 issues assigned to yourself are shown. The quick filter is displayed in the URL (i.e. http://localhost:47212/j7212/secure/RapidBoard.jspa?rapidView=1&quickFilter=1). Clicking on the quick filter will highlight it as if it's applied but will actually unapply it. The quick filter parameter is also removed from the URL so it appears that it's not filtered (http://localhost:47212/j7212/secure/RapidBoard.jspa?rapidView=1).
This causes confusion as there is no clear way to know if there is a quick filter applied and/or remove it.
Workaround
Refresh the page.
=============
Original Description
I have an Agile board (Kanban style) defined for our project.
I also have the Greenhopper Wallboard Gadget included on my Dashboard.
I have configured my Wallboard Gadget to activate one of the Agile board's Quick Filters, for example, the "Only my issues" Quick Filter.
When I display the actual Agile board, the Quick Filter selected for the gadget is active on the Agile board, but the corresponding Quick Filter button is shown as inactive.
Selecting that Quick Filter now turns the filter OFF, but displays ON.
Using the browser's reload will sync the state of the Quick Filter and the displayed state of the button.
I am using chromium-browser Version 27.0.1425.0 on Linux, but I have seen this behavior in other browsers.
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
[JSWSERVER-8198] Quick filter selected for Agile Wallboard Gadget is also selected for the actual board, but the state is shown unselected
We just had some very confused users run into this on 7.2.12, multiple browsers.
Andrew Muraco (Tuxp3)
added a comment - Should I create a new support request/ticket or will one of them be re-opened. Consistently repeatable on Safari 10.1/JIRA 7.2.2
Andrew Muraco (Tuxp3)
added a comment - Should I create a new support request/ticket or will one of them be re-opened. Consistently repeatable on Safari 10.1/JIRA 7.2.2 Hello @Marek Broda,
All the issues in the duplicate chain are marked resolved as duplicates.
Shouldn't one of them be open or resolved with a reason?
I still experience the problem with Jira v6.3.15 and Agile 6.7.12
Anthony
Willie Conen
added a comment - Hi,
Joost Haverkort here (my own Jira account at Atlassian is somehow having login issues, so I'm using my colleague's).
Earlier today I filed a support request for this issue and already got response from Atlassian saying that they will treat this as a valid bug report.
@Michael Elias: I'd really like to have this one reopened please. Not only for me, but also for other people who come here after extensive Google-searching when encountering this issue 
@Anthony Veale: Thanks for originally reporting this.
Kind regards,
Joost
Willie Conen
added a comment - Hi,
Joost Haverkort here (my own Jira account at Atlassian is somehow having login issues, so I'm using my colleague's).
Earlier today I filed a support request for this issue and already got response from Atlassian saying that they will treat this as a valid bug report.
@Michael Elias: I'd really like to have this one reopened please. Not only for me, but also for other people who come here after extensive Google-searching when encountering this issue
@Anthony Veale: Thanks for originally reporting this.
Kind regards,
Joost Michael Elias: do you want each of who have commented on this issue to open separate support tickets?
I'm the original reporter on this issue and while I would like to see it fixed, I have a workaround and considered it trivial. I'm not likely to open a support request myself.
Other reporters seem to feel it is of higher priority and I am sure that they will make support requests.
However, I am interested following the progress on this bug and if the entire process moves into four separate support requests, I will miss out on three quarters of the information.
Also, if I choose not to open a support request, then I am likely to miss any announcement of a fix to this issue because you have closed this issue.
I thought that this was actually the appropriate forum for this particular issue.
melias, please do we need to have this re-opened? There may really be some kind of bug here really. I can reproduce this consistently with the latest version of Firefox (Firefox 29.0.1, JIRA 6.2, JIRA agile 6.3.13 and 6.3.13.1). However, I can't seem to be able to reproduce this with Chrome and IE.
Why the mode/environment of reproducing it doesn't appear to be consistent beats me though.
Hi,
Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com).
Regards,
JIRA Agile Team
Joost Haverkort
added a comment - This bug is very consistent here. Having the quick filter (which is only applicable for the gadget) applied on the scrum board by default is annoying enough, but not having an indication that you're only seeing part of the sprint is a major bug in my opinion. This leads to misinterpretation of situations which cost time and money (not to mention frustration).
I don't agree with this being marked as 'trivial'.
JIRA v6.2.4 on Ubuntu 14.04.
Windows 7 64bit, using Google Chrome 34.0.1847.131 m
Joost Haverkort
added a comment - This bug is very consistent here. Having the quick filter (which is only applicable for the gadget) applied on the scrum board by default is annoying enough, but not having an indication that you're only seeing part of the sprint is a major bug in my opinion. This leads to misinterpretation of situations which cost time and money (not to mention frustration).
I don't agree with this being marked as 'trivial'.
JIRA v6.2.4 on Ubuntu 14.04.
Windows 7 64bit, using Google Chrome 34.0.1847.131 m
Magnus Weström
added a comment - Same behaviour here, can reproduce consistently. This is somewhat detrimental to our work since we use dashboards to increase visibility for multiple teams to stakeholders, and visibility is reduced by quite a lot if we can't filter out irrelevant stories/tasks
JIRA version 6.1.6 and JIRA Agile version 6.3.7
Chrome Version 33.0.1750.146 m
Windows 7
Magnus Weström
added a comment - Same behaviour here, can reproduce consistently. This is somewhat detrimental to our work since we use dashboards to increase visibility for multiple teams to stakeholders, and visibility is reduced by quite a lot if we can't filter out irrelevant stories/tasks
JIRA version 6.1.6 and JIRA Agile version 6.3.7
Chrome Version 33.0.1750.146 m
Windows 7
We're experiencing this bug on Jira Software Server v8.17.1. Very confusing for the less tech savvy employees that don't know the filter can be cleared by editing the URL.