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; } } }

Status change when moving issues between projects

winfred Peerebo

Hi,

We have 2 projects and when an issue is reviewed in the first project we move the issue to the other project. It looks like it copies the status from the first project to the other project. Is it possible to define this and have the issue in the second project within another status?

example:

project 1 -> issue x -> status: ready for developemnt

MOVE TO PROJECT 2

desired situation:

project 2 -> issue x -> status: open

Accepted answers

All comments

Mizan

are they using the same workflow ?

winfred Peerebo

No they have got there own workflow

Mizan

Dont you get options to choose the project ,status, issue type while you move the issue ?

winfred Peerebo

Now i look more to the move process. It looks like "step 2" is passed. This is the step about chaning the status. I can't change it. And don't know where to enable this step

Mizan

I think your projects are using the same workflow(workflow scheme ) . Can you confirm again

winfred Peerebo

First project:

PBL Workflow

Used for workflow within Product Backlog

assigned schema: Product Backlog

Second project

SDD Functional issuemanagement

Functional issue management San Diegeo Development

assigned schema:

This is copied from the workflow overview

Does this confirm the use of separate flows?

winfred Peerebo

See my new comment

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud