Priority between Issue Attributes/Resolutions and Issue Type Resolution Scheme

Question

Hello community,

The Issue Attributes/Resolutions were set to "Done(Default)" (for all projects) and the Issue Type Resolution Scheme (ITRS) was set to "Fixed(Default)" - for a specific issue type and project.

There are 3 options in my ITRS - Duplicate, Fixed(Default) and Not Fixed. For some reason, when trying to set the Resolution field in a transaction (the Resolution field is a required field), instead of Fixed(Default), Duplicate is already preset. Not like in my ITRS - "Fixed" (by default).

I could also figure out that this is a simple alphabetical order - a-b-c-D (for Duplicate) and then f (for Fixed). However, after disabling the Issue Attributes/Resolutions "Done(Default)", my ITRS works as expected - Fixed is preset by default, plus there is an option to preset the value of Resolution to "Please select...", so a conscious decision has to be made (what I actually want to achieve).

However, I can't completely disable the Issue Attributes/Resolutions "Done(Default)" because we need this option in all our projects, otherwise it will confuse our users.

So how can I configure both parts:

1. The Issue Attributes/Resolutions set to Done(Default)

AND

2. The ITRS (for a specific issue type in a specific project) set to "Please select..." to force the conscious decision?

Why does this conflict occur?

Sincerely,

Dave

Marc -Devoteam- · Answer

Hi @Atlassian User

Yes, create another transition to done.

Limit the default existing transition to Done with a Value Field Condition based on issue type not equal to your specific issue type

Set the same condition on the new transition to Done and set it to equal to the specific issue type and add the transitions properties on that transition

Mykola · Answer

Hi @Marc -Devoteam- ,

I appreciate your help,

There are a number of specific projects we have that require almost the same actions. So it was decided to keep the same workflow for all of them to better control these types of projects. Instead of having to go through all the separate workflows in each project in case of a slite change. In our case, there is no need to overload Jira with a bunch of similar or identical workflows.

Are there any suggestions if we cannot ensure that this project uses its own workflow schema and workflows?

Marc -Devoteam- · Answer

Hi @Atlassian User

On the project where you require ITRS, make sure that this project uses its own workflow scheme and workflows.

On the transition to the status where the resolution needs to be set, provide workflow properties.

See use-workflow-properties and check the part about Transition properties

This wil provide you the option to only include the select options on the resolution that you want, you need to specify them by the resolution id (id of the resolution option)