nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I can't move an issue to other Kanban status than Done

Antti_c2fqd1

I have a Jira project ORIGIN which contains a "master backlog". There's a project DESTINATION that has its project filter set so that they receive all issues with Label = 'Dev' from the ORIGIN project.

In the DESTINATION project Kanban board we see the issues in the Backlog column. We're trying to move the "borrowed" issues to Development column but can't move them to any other status except Done. Does anyone know why this is happening?

The Workflow in the ORIGIN project says that stories are allowed to move freely.

Accepted answers

Tushar Mathur_p6izaa

For your DESTINATION project Kanban board, check board configuration under Columns. Looks like you need to map the statuses to correct columns.

All comments

Tushar Mathur_p6izaa

For your DESTINATION project Kanban board, check board configuration under Columns. Looks like you need to map the statuses to correct columns.

Trudy P Claspill

Hello @Antti

Issues that are in the ORIGIN project will be able to change to only statuses that are valid for those issues in the ORIGIN project. In the DESTINATION project Kanban board, what are the Statuses mapped to the Development column? Does the column include statuses that are valid for the ORIGIN issues?

Do the users trying to change the status of the ORIGIN issues have permissions to change them to statuses other than Done? Are there Conditions specified in the Workflow for the ORIGIN issues that limit who can change the Status to certain values?

Antti_c2fqd1

Thanks for these ideas. The ORIGIN project uses the Kanban backlog. The issues are pulled from the backlog to the DESTINATION project and taken into a Kanban sprint. I.e. the ORIGIN project backlog is more like a storage and a place for prioritisation.

The DESTINATION project has many more columns that are not present in the ORIGIN project. Still, both projects have Columns like Ready for development and In development. Both projects have a Workflow that allows "All" statuses for all issues.

The users in the DESTINATION project have also admin permission to the ORIGIN project.

Should this work given the above conditions?

Trudy P Claspill

There are a couple of points I want to clarify.

You are talking about the ORIGIN project and the DESTINATION project, and that the DESTINATION project has its "filter" set to pull issues from the ORIGIN project where Labels = 'Dev'.

A project is a container for issues. An issue cannot exist in more than one project at a time.

A project does not use a filter to determine which issues are contained in the project.

A board uses a filter to select issues from 1..n projects to display in the board.

Given that, are ORIGIN and DESTINATION both actually projects? What is an issue key for an issue in the ORIGIN "project"? What is an issue key for an issue being "pulled in" to the DESTINATION "project"? Can you provide screen images of what you are viewing when you are looking at each of these projects?

I see that you marked the other Answer as accepted. If your problem has been solved then there is no need for you to respond to my addition questions.

Antti_c2fqd1

Thanks for your detailed enquiry. I'm learning a lot from this. The first answer did solve the main issue I had, so I accepted that.

So, ORIGIN and DESTINATION are both projects though I'm seeing DESTINATION as one of the options to select in the "Boards in this project" selector. I don't have admin permission to DESTINATION but have it for ORIGIN.

From this I assume that both the project and board names are ORIGIN and respectively DESTINATION.

I wouldn't like to share images of the boards but I checked the issue keys. In ORIGIN projects ORIGIN board an issue key is e.g. ORIGIN-85 and the same issue "pulled" into DESTINATION is shown on their board as ORIGIN-85 as well.

It now seems that when I created Kanban columns that match the DESTINATION board, they can move the issues between the shared states.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server