-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.1.11, 7.3.8, 7.2.11, 7.4.4, 7.5.1
-
7.01
-
4
-
Severity 3 - Minor
-
0
-
Summary
When viewing a board's backlog, the epic panel is not populated and no epic labels are shown if the board's filter includes Epic Link conditionals.
Steps to Reproduce
- Create a Scrum project with sample data (Test Project)
- Add two epics to the project (TP-24,TP-25)
- Associate issues in active sprint to these epics
- View backlog, see that epic panel is populated and epic labels are visible (Board > Show epic labels)
- Edit filter for board to specifically filter for issues contained in the two epics (project = TP AND "Epic Link" in (TP-24,TP-25) ORDER BY rank ASC)
- View backlog, observe that epic panel is blank and epic labels are NO LONGER present
Expected Results
Expect to see epic information in epic panel & epic labels for issues when viewing issues in backlog.
Actual Results
Epic data is omitted for the issues in the backlog, but is visible when viewing the active sprint.
Workaround
Explicitly add the epics to the board filter: project = TP AND ("Epic Link" in (TP-24,TP-25) OR issue in (TP-24,TP-25)) ORDER BY rank ASC
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-16178] Epic Panel/Labels not populated in backlog if board filter includes epic links
@Ignacio. That the Epic panel is blank is the expected behavior since the original query filters out Epics, but that the Epic labels are not shown is a bug.
Thomas Bithell
added a comment - What is the name of the ScriptRunner function you mention? This is not a bug, but the expected behaviour.
Issues of type Epic cannot have Epic Links, therefore they are filtered out by the initial query.
Your suggested "workaround" is not something weird you have to do in order to circumvent a bug, but the actual query you should set as your filter query so that (only) those Epics are shown in the epic panel.
Note that you could have used this alternative board query if you didn't mind other epics to be shown:
project = TP AND ("Epic Link" in (TP-24,TP-25) OR type = Epic) ORDER BY rank ASC
ScriptRunner provides a function to make it easier to recursively retrieve just your selected epics together with the issues that belong to them, including their subtasks.
Including a similar function as a JIRA native functionality would be a feature request.
Sorry, I attached the csv file incorrectly.
It is a csv file irrelevant to the issue.
Please delete it.
Oh, I see, that's a bug then!
And reviewing SR JQL functions, I've noticed I wasn't remembering correctly, as the function with the recursivity was linkedIssuesOfRecursive, which is not useful in this case.