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

Don't force a change in "Resolution" when Bulk transition issues to close

Christina Fausbøll

When I bulk change issues and transition them though our workflow from Resolved to Closed ( to remove them from my boards") i would like my issues to keep the resolution code they already were set with, when I resolved the issues.

But as it is now, I have to Change the Resolution when i move the status. I can't unmark the "Change Resolution" and I need to choose a new value, which overwrite the value that the issue already has.

Does anyone knows how I can change this, or if it is possible.

When I close the issue from the issue card, the resolution option is kept, without a force to change.

Accepted answers

Nic Brough -Adaptavist-

Your screen shot implies you have made the resolution mandatory in your field configuration.

NEVER do that. And in a similar vein, NEVER put the resolution field on any screen other than a "transistion to a closed type status".

(Well, not quite "never", there's a couple of edge cases, but for most Jira systems, it breaks it completely)

Radek Janata

Unfortunately, there is no solution for this problem. Resolution field (when set on a screen) is always required and this cannot be changed (see also this question). This causes bulk edit/transition action to always require filling resolution (and therefore overwrite other resolution if they are different).

Atlassian doesn't not seem to resolve this in near future:

JRASERVER-34902 (Won't Do)
JRASERVER-43564 (Gathering Interest @ May/2020 + duplicate to Suggestion above)

All you can do is to vote & watch & comment the latter issue.

All comments

Moses Thomas_08kyb0

@Christina FausbøllYour resolution field is set mandatory this is why you can set the resolution field to be optional in the field configuration scheme for the issue type. Then you will not be force to change resoulution

Best!

Nic Brough -Adaptavist-

Your screen shot implies you have made the resolution mandatory in your field configuration.

NEVER do that. And in a similar vein, NEVER put the resolution field on any screen other than a "transistion to a closed type status".

(Well, not quite "never", there's a couple of edge cases, but for most Jira systems, it breaks it completely)

Jack Brickey

@Nic Brough -Adaptavist-, I certainly understand the second never but why do you suggest the first? It seems to me that in some scenarios you want to require the user to select a resolution when closing an issue. Is it because once mandatory in the field config it is mandatory for all possibly? And the alternative approach is use the validation property to require it for the specific WF?

Nic Brough -Adaptavist-

Yes, it's exactly that. If you make the resolution mandatory, you have to fill it in (i.e. resolve the issue) when you create the issue, and you can't blank it out!

Christina Fausbøll

Thanks for the input.

Our "Resolved" status is when an issue has been resolved. We just move them to Closed when we don't want them to figure om out boards anymore. So it is only on screen where we resolve/close the issue.

I'm pretty sure that it is set up by our consultant who has helped us make out workflow schemes.

I will discuss with my team of how to change this, and I think that the validation in the transition, might be a better idea for make sure that it is filled out, than it being mandatory- with the examples that you have given us.
@Nic Brough -Adaptavist- do you see an issue in doing this instead? As far as I have understood there is some Jira logic that handle issues with the resolutions code " Unresolved" in a particular way.

Tom Hawkins

We use "Resolved" to indicate "Ready to go live" (with Resolution) and "Closed" for "Live and believed to be working", so I think that it would still be a useful feature for the bulk update to have the untick which @Christina Fausbøll mentioned or some other "Retain current" (would be ok if it didn't support retaining None) even after reading the above comments and warnings, and indeed, that's how I found this page. Does anyone know if there is an Atlassian Jira ticket requesting this? Thanks

Jack Brickey

I would not expect to see such a suggestion. Are you saying that the Resolutuon code changes from Resolved to Closed. I would suggest that Resolution in your case would be applied at transition to Resolved and then transition to CLosed would be done when issues are “released”. This equates to removing any requirement on updating resolution on transition to Closed.

Tom Hawkins

Hello @Jack Brickey thanks for coming back to me. RE: "Are you saying that the Resolutuon code changes from Resolved to Closed." No, I don't WANT resolution to change, but it may do if I only run one bulk transition action and have multiple resolution entries in that bulk list. RE: "I would suggest that Resolution in your case would be applied at transition to Resolved" Yes.

Example Use Case:

I have 10 issues, all in RESOLVED status, 7 with FIXED resolution, 2 with WON'T FIX resolution and 1 with DUPLICATE resolution. I want to bulk transition them to closed maintaining the same resolutions. Because of facing the same as @Christina Fausbøll mentions above, I can't see a way of doing all 10 in one bulk transition, (would need one per existing Resolution value, eg. 3)

A related issue is that I have seen instances where someone has inadvertently updated some of their resolutions because of making a single selection in that screen for a list where multiple values applied at RESOLVED point. I've now found https://jira.atlassian.com/browse/JRASERVER-43564 and am voting and commenting on it, @Christina Fausbøll suggest you do the same!

Thanks, Tom

Jack Brickey

if the Resolution is set when transitioning to Resolved status then it will not change when moving to Closed unless you specifically have something configured to require it be updated or some automation, etc. A single transition or a bulk transition from Resolved to Closed should have no impact on the resolution value at all. If you are seeing the Resolution updated during either of these actions then it needs to be analyzed to understand why.

Radek Janata

Atlassian doesn't not seem to resolve this in near future:

JRASERVER-34902 (Won't Do)
JRASERVER-43564 (Gathering Interest @ May/2020 + duplicate to Suggestion above)

All you can do is to vote & watch & comment the latter issue.

Radek Janata

Resolution field is a system field and it can never be set as required/optional in field configuration scheme. When Resolution field is set on screen, it's always required.

Jack Brickey

Never make Resolution required in field config.

Jack Brickey

WARNING: Editorial....

I don't think this is the correct answer or at least it is incomplete. You should not make the Resolution mandatory in the Field Configuration screen. As Nic so eloquently put it below...

NEVER do that. And in a similar vein, NEVER put the resolution field on any screen other than a "transition to a closed type status".

If you make it mandatory then it is ALWAYS required and that includes bulk update. There is no way to avoid other than not make it required which is the proper solution.

Moses Thomas_08kyb0

@Radek Janata Yep that's right! well most likely but , I thought some time ago it could be optional

Ricky Lin_1m211u

All Atlassian needs to do is to give us the same "Retain Value" option during bulk transitioning and it'll save a lot of trouble... Anybody might know why this isn't an option when it's available for other fields?

As of now, we're getting around this limitation by via 2 days:

Bulk-transition the tickets grouped by Resolution. So if 100 tickets yield to 5 different Resolution values, we'll need to do this 5 separate times.
Temporarily change the Close screen to one without Resolution field on it and bulk transition. This is quite an inconvenient workaround since we need to do it afterhours.

Radek Janata

> you should not make the Resolution mandatory in the Field Configuration screen

@Jack Brickey, you cannot make Resolution field (a system field) as non-mandatory via Field Configuration. It's always mandatory and you cannot change it.

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-cloud

jira-server