Bug in Jira Cloud?

Hi everyone,

One of my colleagues notified an interesting thing and this is:

 I activate Resolutions attribute on a project and  beside the defaults attributes I create two more. One of the attributes is called 'New' and I set it to be default resolution when you create a new Issue.

So problem is: when I create a new 'Bug Issue' and I set the Resolution field to be New(as default), Bugs with the resolution “new” appear with strike trough even if the Bus Issue is 'In Progress'. This problem is in all project where Resolutions are in use.

image2016-7-22 14:39:46.png

image2016-7-22 14:40:38.png



2 answers

1 vote

No, it's not a bug.

You must never have a resolution that means "not resolved" and you must never put the resolution field on a screen other than a "transition" screen.


To fix your JIRA now you've made the mistakes:

  • Remove the resolution field from the "create issue" screen
  • Remove the resolution field from the "edit issue" screen if you've accidentally added it there too
  • Rename the resolution "new" as something like "broken resolution - do not use"
  • Find any other resolutions that might mean "not finished with" or "still open" and delete them, migrating to "broken resolution - do not use"

Now you can run a report on all the ones you've broken and analyse how to repair your data

100% agree!

0 votes

Hi Raul,

JIRA considers an issue as open if it lacks a value in the Resolution field, and as closed if it has a value in it.

The Resolution field is intended to be used to provide information about what finally happened with the issue once there's nothing else to do with it.

Typical Resolution values include: Fixed, Done, Couldn't reproduce, Answered, Out of scope, Not a bug, Won't do, Finished, Deployed to Production... etc.

The Resolution field shouldn't be used to substitute workflow statuses, which suits much better for marking an issue as 'New'.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

247 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you