JIRA separate swimlanes for each issue

[Marcin Matelski]

Hi,

We're trying to create universal kanban board when every issue is in separate swimlane.

We have a 'parent' issue with linked issues (not subtasks). 

We can create separate swimlane filters like:

issuekey = "ISS-1"

issuekey = "ISS-2"

issuekey = "ISS-102"

and so on, but that requires us to manually create new swimline filter each time new parent issue is created... 

Is there a way to crate swimlane filter to aggregate linked issues under a parent issue in separate swimlane?

[Prem Chudzinski _extensi_ · Accepted solution]

Yes,

Use epics and stories (linked to epics).

Afterwards select swimlane type by epic using the board configuration.

That way new swimlanes will be created automatically, and tasks (stories) will be aggregated.

[Marcin Matelski]

I'm already using custom issuetypes, can merge them somehow with epics and stories?

[Prem Chudzinski _extensi_]

Epic link relationship is set to Issue type(s):Global (all issues).

Thats why custom issuetypes can be linked to an epic.

Add EpicLink field to your custom field screen configuration.

Use the bulk change operation to migrate all "Parents" to epics.

Afterwards link Epics and custom type issues.

The best way to do that is to create a temporary scrum board and do it using backlog.

Afterwards delete the scrum board and create a new Kanban board.

The reason for that is that Kanban backlog won't show you all the issues from the board. You'll see backlog and the next status only... We'll fix that Jira issue in our plugin Agile Board Filter pretty soon :)

Using scrum backlog you'll se all issues on the backlog.

[Marcin Matelski]

OK, but what about any new 'parent' issues? They will have to be manually copied as epics and linked back?

[Prem Chudzinski _extensi_]

All new "parents" should be created as epics.

While creating a child, select the Parent epic link - that is why you have to modify the child create issue screen by adding the epic link field.

While using bulk you don't copy existing issues but migrate to epic type.

If you use epics you'll be able to use backlog epics panel.

[Marcin Matelski]

OK, thanks, thats one solution. I guess it would work but would require us to drop our custom "parent" issue and use epic type instead; technically this shouldn't be hard to do, but I'm just affraid that for the end user this'd leverage whole workflow logic, as the epic name doesnt fit anywhere here. 

I guess custom issue types can't be set to be used as epics?

[Deleted user]

Here...you want a suggestion for how it should work.....look at this..

;tldr

Either you make the "Story" Swimline view, which groups by sub-tasks, also supported in the reports where your burn-up and burn-down show progress by "sub-task" (whereas right now you only show progress by "Story" or by "Issue").

Or....

You support a view for the Active Sprint to allow groups by Story with all "Relates to" links (i.e. Issues) pointing AT THAT STORY, categorized underneath it.

Fix this...and it will be INFINITELY more aligned with how the vast majority of Scrum Teams use their Scrum (Kanban) Board. 

Long version

What if you aren't using SUB-TASKS, because the Burn-Up reports don't report completed Sub-tasks as "completion" (which if it was working the way it SHOULD, it WOULD)?

How would one do that.

Story

^^

||

|| Relates to

||

\==== Task

||

\==== Task

How do we monitor progress when Jira operates so illogically. If you're going to have Swimlanes to monitor Story progress by viewing Sub-tasks in the active Sprint, then support reporting the Burn-down or Burn-up via counting sub-tasks.....Sheesh!