Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I move a Jira story from one Kanban to another?

Valerie Lipow
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 19, 2025

I created a Jira story on one Kanban board. I want to move it to a different board.  I don't see a written option in any window or menu to do this. I tried dragging the story from the current board into another board in a different window. That was unsuccessful.

How do I do this?

2 answers

1 vote
Trudy Claspill
Community Champion
August 19, 2025

Hello @Valerie Lipow 

Welcome to the Atlassian community.

Issues are displayed on a board based on them matching an issue selection filter used by the board. Yo need to make your issue match the criteria of the filter used by the board. The next step is to determine what is the filter for the destination board.

When you look at the issue you created it had a "key" that is a combination of letters, a dash, and a number, like ABC-123.

When you look at the issues on the other board do they have the same letter prefix in their keys as the issue you want to move?

 If not then you may need to move the issue from one project to another.

Can you provide screen images showing the board where the issue is now and the board you want to move it to? That may provide us with info that will help us give you more targeted advice.

Valerie Lipow
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 20, 2025

Hi Trudy,

Thanks for taking the time to answer my question. I  shared screen shots of what I see today. Yesterday, the story I was working on was NOT included on the Kanban Board it's displayed on today.

My colleague who administers the boards moved it to the current board earlier today.

So, I wonder if what I should know is WHO is authorized to move a story from one Kanban board to another. Then, the HOW may become clear on a menu. I can create a story and update/comment on a story. Perhaps I'm not authorized to move a story. Please comment on that.

I will also tell you that a lot of the jargon you use is gobbledygook to me. I'd appreciate it if you'd use the same words I use ("story", for example).

Thanks,

Val

Trudy Claspill
Community Champion
August 20, 2025

Hello @Valerie Lipow 

As of now I don't see any screen images added to this post. Without those images I cannot assess what might have been done by your colleague to move the story.

In the answer I provided the only difference in terminology that I used was "issue" instead of "story". Otherwise I believe I used the same words as you where possible, and used the appropriate terminology for items that you did not specifically mention.

If your are new to Jira and the terminology is unclear, you may want to avail yourself of the free, on-demand training available from the Learning link at the top of the community pages. I would recommend starting with this course:

https://community.atlassian.com/learning/hub/all-learning-paths/path/get-the-most-out-of-jira

I'll try to clear up some of the terminology:

"story" is a type of "issue", also known as a "work item". Work Items (issues) can have a variety of types like story, task, and bug. Each Work Item has a Summary, Description, Status, Reporter, and other fields.

Work items are stored in "Projects". (Note that Atlassian is starting to roll out a terminology change here where Projects will be referred to as Spaces.) A Project has a name and a short key; i.e. This Is My Project, with the key TIMP. A given work item exists in one and only one project at any given time.

Each work item in a project is assigned a "key" which uniquely identifies that work item. The key is a combination of the Project Key and a number; i.e. TIMP-1. The work item key is shown throughout Jira.

Screenshot 2025-08-20 at 11.59.13 AM.png

The work item key always includes the Project key for the project in which the work item exists. A work item can be moved from one project to another, and in that move the work item would get a new Key comprised of the destination project's key and a number.

Boards are just a way to view and manipulate work items. Work items are not "in" the board - work items are "in" projects.

The work items displayed in a board are based on a Filter that is part of the board's configuration. The Filter specifies which work items to show in the board. A filter could, for example, select all the issues from a single project:
project = "This Is My Project"

Filters can be constructed to select work items in a variety of ways using criteria applied to various fields within the work items.

The board that is created automatically along with the creation of a Project will use a filter that selects all the issues in that one project. But it is possible to construct additional boards that are based on different filters.

Because boards are based on Filters, and Filters are just selecting work items, any given work item can match multiple Filters and could be shown in multiple boards.

To understand why a particular work item is shown in one board or another it is necessary to first figure out what the Filter is for each board. If the story of interest to you is not showing in the original board and now is showing in the desired board then something in the story changed so that it no longer matches the filter of the original board and now does match the filter of the desired board.

But without knowing what those filters are, we can't figure out why the issue is or isn't displayed. Without that information we don't know what change had to be made in the story to change where it displayed. Without knowing what change had to be made we can't explain what permissions would be needed so that you can determine WHO could make that change.

So, I don't have enough information to comment on why you might not be able to "move" a story. That is dependent on figuring out if it is being moved between projects in order to match the filter of a different board, or if it just required setting some field within the story to make it match the filter of the other board.

0 votes
Shalini Pradhan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 19, 2025

Hello @Valerie Lipow ,

Good day! Welcome to Atlassian Community. :)

In Jira, boards do not contain issues, they are views based on filters (usually JQL filters). That means you don’t actually move an issue from one board to another. Instead, you make changes to the filter query that is associated with the targeted board so that the issue appears on your targeted board

1. Understand the Target Board’s Filter

  • Go to the destination board.

  • Click Board settings -> Details -> Board filter
    Screenshot 2025-08-20 at 10.28.31 AM.png

  • Look for the filter query, this defines what issues are shown on the board (based on project, labels, components, issue types, etc.).

2. Update the Story to Match the Filter

To make your story appear on the new board, you need to edit it so it satisfies that filter.

Thank you!

Trudy Claspill
Community Champion
August 19, 2025

Note that the filter basis of a board can't be viewed if the destination is the board that is built-in to a Team Managed projects.

For built-in board of a Team Managed projects the filter is effectively selecting all the issues in the associated project.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer