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 reset resolution after moving an issue to another project?

Frank Adler

Steps to reproduce:

Issue in a resolved status in project A (e.g. RESOLVED fixed)
Move issue to Project B - status is not available
Choose status in an unresolved state (e.g. OPEN)

Actual Result: Issue is in an Open state with resolution set (e.g. OPEN fixed)

Expected Result: Resolution is reset/purged.

Question:

How can I force the reset of resolution in the workflow?

I tried to reset in the POST Function of the target workflow to no avail.

Accepted answers

Nic Brough -Adaptavist-

I'm afraid you need to push the issue through a transition that clears the resolution. When you move an issue into another project, that really is all it does. It checks the config for incompatibilities and makes the minimal changes required, then moves it, with existing data.

All comments

Amir Ghaemian

Have you tried adding a Post-Function in the Create transition of your target project to Clear the resolution field?

Nic Brough -Adaptavist-

Joe Pitt

If it is always going to the 'open' status put a transition that clears the resolution field the only an administrator (JIRA or Project) can execute that goes back to Open. You do realize by resolving the issue in one project and moving and reopening in another your created vs resolved reports won't be correct?

Frank Adler

I have tried it even in different positions without success:

before issue create

Transition: Create

Post Functions

The following will be processed after the transition occurs

The contents of the field Resolution will be purged.
Creates the issue originally.
Re-index an issue to keep indexes in sync with the database.
Fire a Vorgang erstellt event that can be processed by the listeners.

after issue create

Creates the issue originally. 
The contents of the field Resolution will be purged. 
Re-index an issue to keep indexes in sync with the database. 
Fire a Vorgang erstellt event that can be processed by the listeners.

Joe Pitt

I think the problem is moving it doesn't go through the create tranisiton

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

workflow