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

How to configure fields while moving an issue

tifonas-katrina

Hi,

Recently I have an issue with Move functionality of Jira.

As soon as a Task is moved to Bug within the same project, previous admin mentions that "Modified the DT scheme to enforce the Epic field when issues are moved". Where can an admin configure things when an issue is mived?

Any answer is helpful,

Katerina

Accepted answers

Nic Brough -Adaptavist-

You do not configure the move operation.

The move operation scans for differences in the configuration between source and target and makes sure they are minimally compatible. If something is compatible, it does not ask or perform any migration or update because it doesn't need to.

All comments

Nic Brough -Adaptavist-

You do not configure the move operation.

tifonas-katrina

Ok, then statement from previous admin is invalid.

Nic Brough -Adaptavist-

Indeed, it must be an optional field for the target.

If you made it mandatory, then the move would start prompting you to enter it for issues where it is currently empty.

tifonas-katrina

No prompt, no nothing.

This is madness. I'm investigating issue for months

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration