You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Two questions in one!?
Sprints are part of the Scrum process. Kanban methodology doesn't use Sprints or any sort of iterative process. In a similar vein, in JIRA Software there is no way to plan Sprints on a Kanban board. However, you can point a Kanban board to a query such as sprint = "It's over 9003"
or sprint = activeSprint()
. Is there a reason the Scrum board doesn't work for you?
Swimlanes indicate explicit queries that show specific issues based on a criteria you choose. There's no way for JIRA to know how you'd want to update issues between lanes. What if someone had a query like updated = 12h
? Would it just change the updated date to 12 hours ago?
On the swimlanes one, another example I ran into yesterday - if you have two swimlanes to drag between:
How is JIRA supposed to know how to change the data? It's possible that it could be Acme + Anvil, and that's a valid combination of data, so it's already in both lanes (althoguh JIRA will hide it in the second one because it's already in the first). Or if it should change Acme, to get it out of the first lane, does it change or drop the Acme? Change to what? Even though it's unrelated to the component?
(Yes, I am watching Road Runner cartoons)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's a perfect example. And I should watch some Tom and Jerry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the kanban board it is changing the Epic or Bug Statuses when moving it across columns.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you want to map specific statuses to columns, you can do this in the Board Configuration and navigating to Columns –
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>In the kanban board it is changing the Epic or Bug Statuses when moving it across columns.
Correct, that's what Kanban boards are for. Columns are a collection of status (often only one status, but you can have many in a column). As the status are a known, fixed list, you know you can change them. Swimlanes are for displaying slices of data which can be unknown and contradictory, so there's no way to move between them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not quite sure what a scrum qualification has to do with this old thread, but I'm already a Scrum Master and I know Steve works with a lot of Scrum teams (I don't know if he's got certifications, but I would not be at all surprised to find out he's even better qualified than me)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I mostly wanted to point out that while JIRA does not support sprints with Kanban, Scrum + Kanban is a real thing so it would be nice if you/they considered adding the feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To do scrumban, start with a scrum board, and don't use all the functions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira allows you to use the same query for both a scrum type board and a kanban board, but will not allow you to administer sprints from a Kanban board. The best way to think about this is that a board in jira is really just a view of a query (jql) but has different interface logic.
Basically the work around is to create a board of type scrum where you can create sprint codes first and then just use your kanban board as normal. This means your issue will then be able to have a value for the sprint field on edit.
In my opinion Atlassian should use the same board logic and allow a switch in the board configuration for turning things on and off, such as story points and showing epics in the tab and/or the board. Right now you need two boards just to manage this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.