Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Difference between Issue resolved and Issue closed events in notification scheme

In JIRA notifications schemes there are "Issue resolved" and "Issue closed" events.

 According to this

Issue Resolved:

An issue has been resolved (usually after being worked on and fixed).

Issue Closed:

An issue has been closed. (Note that an issue may be closed without being resolved; see Workflow).

In particular i'm interested in that an issue may be closed without being resolved.

But according to

  • An issue is Open if its Resolution field has not been set.
  • An issue is Closed if its Resolution field has a value (e.g. FixedCannot Reproduce).

The question is when the "issue closed" event is fired? And how does it connects with obliterated representation of an issue. That is, JIRA-1 means an issue being resolved or closed? And what's the meaning of "closed" that way?

5 answers

1 accepted

6 votes
Answer accepted

JIRA has two "fields" (one of them isn't a field, but for this, it might as well be).

The Status tells you where the issue is in the workflow.  It does not tell you anything about the issue's resolution, even though it might say "resolved", "closed", "done", "fed to penguin", it's just an indicator of where it is.

Resolution is the more important one - if it is empty, JIRA sees the issue as "open" (and displays "unresolved" on screen, even though it's empty), whatever the status is.  It considers it "done" if it has any data value at all.

Events are not really related to that.  Some are fired by "actions" (edit, comment, move, etc), but the two you're looking at are part of the workflow.  In JIRA version 1, there was only one workflow, and it had status including Resolved and Closed.  The workflow fired "issue resolved" when a user went through a transition into "resolved" and it fired "issue closed" when they went through transitions to "closed".

In version 2 and above, workflows became flexible.  Not only could we move the transitions around and change the list of status in them, we can also change the events fired, and define our own.  The two you're looking at now don't necessarily have to mean what they say any more - you could easily have a transition from "purple" to "orange" that fires "issue resolved" and equally, have a transition from "open" to "resolved" that fires "issue re-opened".  Of course, there's little sense in doing it, but you could.

Think of the list of events you have as being a default set of events that are configured well by default (by the built in workflow and by the ones JIRA can create when you use project templates).  The events do NOT have anything to do with the resolution directly though.

A good guideline is to always think about where you want to set and clear your resolution when you build a workflow, and then, as a different task, what events you want that workflow to fire on a transition.


in order to identify the event fired, you need to check in your worklow settings which event is fired on the transition. It should be the last "post-function" launched. 


The strikethrough means that the issue has been resolved.

For the closed vs. resolved, it's a question of interpretation. I suggest you to read :


 Nic Brough [Adaptavist], Corentin Mehat, thank you for your answers!

With you help i finaly got it clear. The last thing that bothered me was that i couldn't find "Issue closed" event in list of options of "fire event" postfunction. The reason is the name of event is translated by JIRA (it is contained in the list, but is called differently) , though english is set in my preferences.

Your instance might have been initially installed with a base language that is not English, or english is your profile preference but not the default JIRA language. In either case I  suggest that you have a look at the workflow transition postfunction and I think you should find the proper event over-there.

I am a Tester and I wonder why isn't anyone talking about a status of Compliance/QA! Maybe all are developers haha! My idea of the workflow is:


Open............................Un Resolved

In Progress...................Un Resolved




From QA it can go another way Re opened (Status) with unresolved (resolution)


Correct me if I am wrong

This is what I am looking for, and I am a developer.

That's just one workflow.  It's right, as it maps resolution in a useful way, but I'd question the "QA = fixed" because it means the issues are resolved when they are in QA, and that is wrong for a lot of people.

Its not Resolved when testing isnt done yet, its just Fixed which means its fixed by Developer. But the Status shouldn't be set to Resolved, it should be set to Compliance/QA.

Nope.  If you put a value in the resolution, then the issue is resolved/closed/ended/done/whatever.  End of story.

In your workflow, if you don't want "in QA" to mean "resolved", you need to not map a resolution.

Please have a read of the answer I gave two years ago

I believe the simple answer is:

  • If Status is of the "Done" category (the green box in the workflow), the issue closed event is fired. 
  • If resolution is set that will fire issue resolved event.

Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you