Scrum and Kanban backlog is the same.

[Arsen Papoyan]

I have two boards (scrum, kanban). When I create tasks for the sprint, they are also created in the kanban backlog. I want to have a separate backlog for them. How is it possible?

[Alexey Matveev]

It means that your JQL filters for the Kanban and Scrum boards select the same issues. You should change the filters. You can change filters in the board settings -> general

[Arsen Papoyan]

@Alexey Matveev Could you please send me a screenshot of what I should change exactly for both in the JQL filter?

[Alexey Matveev]

If you could share the JQL of your filters, I could give you more details. I am not sure what your filters are currently

[Arsen Papoyan]

@Alexey Matveev please

[Alexey Matveev]

The filter for the board is in the General page. 

[Alexey Matveev]

You can find more info about board filters here:

https://confluence.atlassian.com/jirasoftwarecloud/configuring-filters-764477988.html

[Arsen Papoyan]

@Alexey Matveev Please help to understand what should I change in order to have a separate backlog?

[Alexey Matveev]

Click on the Filter for HT board and Filter for Scurm and you will be able to see the JQL queries. Kindly paste this JQL queries here

[Arsen Papoyan]

Hi @Alexey Matveev. Sorry, but since I am new in Jira, so could you please provide more details about what and where I should copy and past?

[Alexey Matveev]

Ok. Got it. Your JQL filter is the same for both boards. Here it is:

project = HT order by Rank asc (it is seen on your screenshot).

How can you understand if an issue must be shown in the kanban backlog or in the scrum backlog.

For example, if you can differ it by assignees then you should change this query like this:

For the scrum board:

project = HT and assignee = assigneescum order by Rank

For the kanban board:

project = HT and assignee = assigneekanban order by Rank

But first you need to define the condition on which you define to what board an issue belongs.

[Arsen Papoyan]

@Alexey Matveev I have tried, but the SAVE is not being active. 

[Alexey Matveev]

It will not work because you do not have such users as assigneescrum and assigneekanban.

How do you understand that an issue belongs to a scrum board or to a kanban board?

[Arsen Papoyan]

@Alexey MatveevMy problem is that I have two boards in one project (kanban, scrum). Those boards have a backlog. When I create an issue in one of the board backlog, it appears on both boards.
I want to create an issue that will only be in the current board backlog.
I hope that I was able to be more understandable.

[Arsen Papoyan]

Do you have any idea how I can do that?

[Alexey Matveev]

Boards do not contain issues. Issues are selected to boards by JQL queries. That is why if you create an issue from the board interface, it will go to all boards, which select it by their filters.

That is why you need to set some field in the created issue (a group, an assignee, any other flag) so that you could later select this issues based on this flag/group/assignee by your filter.

[Arsen Papoyan]

@Alexey MatveevSorry if I bother you too much.
So how can we create an issue which will not go to all boards, and will only be displayed on the board on which it has been created?
As far as I understand, that is related to JQL filters, but how is it possible, what steps should I do for this?

[Arsen Papoyan]

Can you please have a look at this?
Issues which have been created in the kanban backlog are automatically created in the scrum board as well. Can we are not allowed this behaviour?