-
Suggestion
-
Resolution: Fixed
As a scrum master, I'd like to be able to group tickets by project in work mode.
We run many concurrent projects from the same board. Currently we use epics for projects, but there are some significant disadvantages to that since the rest of jira, plug-ins, etc. don't really know anything about epics, but they do know about projects & versions.
(Really, I'd like to be able to create swimlanes by pretty much ANY field, and I'd like to be able to dynamically change them on the fly without going into "configure", but that seems like a significantly larger ask.)
original Suggestion included by Version but this is now tracked in GHS-5720
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
- was cloned as
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-9719] Swimlanes by project
This feature is now available in JIRA Software Cloud. It will be available for JIRA Software Server in a forthcoming release.
Kind regards,
Martin
JIRA Software
micah1, as noted at https://jira.atlassian.com/browse/GHS-9719?focusedCommentId=690847&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-690847 I wish to change this Suggestion to track swimlanes by project and will track swimlanes by version on GHS-5720
Splitting the stories allows better tracking of the items which would be implemented independently.
It would be helpful if you do not revert the summary and description when I make the changes.
Kind regards,
Martin
JIRA Agile
+1 this issue.
Today I make one Kanban Board to see all projects in our organization using JQL queries in the swimlanes - this is manual and needs frequent updates. Unfortunately it doesn't scale. I work in an organization with 5,000 employees (500 teams) and am looking for a single automated view where each week I don't have to tweak swim lanes.
Examples:
Swimlane 1: project = ABC
Swimlane 2: project = XYZ
Swimlane 3: project = 123
etc
In addition it would be great to say all projects (grouped in swim lanes) where issues match certain criteria (eg a label called "efficiency") so I can get a view, across all teams, grouped by team, of the issues across the company working to improve efficiency.
More at (along with other customers requesting):
https://answers.atlassian.com/questions/223061/answers/4050221/comments/12281173
Many thanks!
I have updated this issue to just track swimlanes by project.
Swimlanes by version is tracked by GHS-5720
Kind regards,
Martin
JIRA Agile
Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.
Regards,
JIRA Agile Team
Scot Mitchell
added a comment - The expand/collapse all is very useful when using the swimlanes but there are a lot of times you don't want the swimlanes at all especially when you are also using quick filters (the swimlane breaks make it harder to visualize). Also you can't prioritize (rank) between all users (assuming your swimlanes are assignee).
I know this is a little nit-picky since it only takes 5 clicks to switch back and forth but it would make it much easier on users who aren't really savvy and quick with a mouse. It's just updating 1 field in 1 database record and then refreshing the screen so it doesn't seem like it would be very hard to do.
Scot Mitchell
added a comment - The expand/collapse all is very useful when using the swimlanes but there are a lot of times you don't want the swimlanes at all especially when you are also using quick filters (the swimlane breaks make it harder to visualize). Also you can't prioritize (rank) between all users (assuming your swimlanes are assignee).
I know this is a little nit-picky since it only takes 5 clicks to switch back and forth but it would make it much easier on users who aren't really savvy and quick with a mouse. It's just updating 1 field in 1 database record and then refreshing the screen so it doesn't seem like it would be very hard to do. Scot Mitchell
added a comment - I would like to see almost any of the fields be able to be used for swimlanes (version, project, priority, assignee, reporter, etc). I would also like to be able to use label and component fields but understand that would be a little more difficult because their could be multiple values. One way to deal with this would be to put the same issue under each of the swimlane values.
To add to my above suggestion, instead of a checkbox or button on the Work page, another option would be to have a dropdown list of swimlanes (including no swimlanes) to choose from. This would allow quick restructing of the board and would eliminate the need to have a lot of quick filters.
Scot Mitchell
added a comment - I would like to see almost any of the fields be able to be used for swimlanes (version, project, priority, assignee, reporter, etc). I would also like to be able to use label and component fields but understand that would be a little more difficult because their could be multiple values. One way to deal with this would be to put the same issue under each of the swimlane values.
To add to my above suggestion, instead of a checkbox or button on the Work page, another option would be to have a dropdown list of swimlanes (including no swimlanes) to choose from. This would allow quick restructing of the board and would eliminate the need to have a lot of quick filters.
This feature is now available in JIRA Software Cloud and JIRA Software Server 7.2.
Kind regards,
Martin
JIRA Software