Ok, there's a few things in here:
An important thing to understand is that a board is not a container for issues, it is a view of a selection. I know you've not mentioned anything about this in the question, but I always find it's worth re-stating when people are new to boards.
>Components to be put up on the board that run concurrently and do not change:
"Components" in Jira is a Jira-speak reserved word - there is a system field called components that is a project concept and it is usually used for breaking up projects, or rather, grouping things in a project. Really bad analogy, but if you were using Jira issues to track "pets", you might have components representing "colours", so with a list of options like blue, grey, ginger, black, white, lilac. PET-1, PET-2, PET-3 in our house all used to have the single component of "black" before they died, but PET-4 has components of white, ginger and black, and PET-5 grey, ginger, white, black and lilac.
These values are issue values, not things that directly appear on a board outside the issues. You can of course, use them for filtering (quick filters or swimlanes, or even for the board itself)
But for your overarching billing/auth/development etc, yes, you may find Epics are a far more natural and easy way to see things grouped on the board. A lot of people run boards with never-ending epics for exactly that reason
>are different types of Kanban Boards
Almost - it's not so much that there are different types of Kanban board, but the Kanban boards function differently depending on where they are defined, and they have a lot of flexibility, so you might well see two Kanban boards that (for ease of explaination) are of the same "type" but work very differently.
Broadly, you'll see four "types" of things that look like Kanban boards:
- Kanban boards from team-managed projects - these will look similar to each other, they're tied to a project and don't have a huge amount of flexibility
- Business boards in Jira Core projects - these are also tied to a project and have almost zero configuration. They look a bit Kanban-y but really are not Kanban boards
- Scrum boards that have been configured to be very close to Kanban boards (I'll ignore these, you could argue that they are all very close to cases 1, 2 or 4 anyway)
- Kanban boards that handle company-managed projects
The 4th is the most important here - they are based on filters more complex than just "the project", you can build all sorts of cross-project, ignore other stuff lists of issues for your board, and have multiple boards all doing different things with the same issues.
>I would also like to add a backlog lane to the swim lanes that they have and not display it on the board-is this possible? At the moment they have selected for development, blocked, in progress, review and test, done.
I think you are mixing up Columns with Swimlanes here. A column contains one or more status and the idea is that as an issue progresses, it will move from one column to the next, eventually landing in the last "done" column.
A swimlane goes across the board, grouping issues into layers.
I think what you mean is you want that issues in the backlog do not show on the board. Depending on the type of board you're using, this is possible, check the backlog and board settings (a company managed project for example, you could not map the status from the backlog. team-managed let you do it with config flags)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.