Meta

This issue duplicates AOD-6676, so please close it wherever it isn't appropriate:

• I've been unsure where to file it and in hindsight JRA might have been the better choice, but I'm unable to move it myself and almost a week has passed w/o any feedback whatsoever, so I hope to get some attention to this potentially severe issue here eventually.
• I realize that you are having a hard time getting on top of the issue queues currently, yet I consider security and data integrity issues critical and expect an initial acknowledgement/triage at least - lacking this minimum feedback, I'm not comfortable recommending JIRA/OnDemand to my clients/teams right now.

Original Issue (filed as AOD-6676 at 2013-08-02T00:49Z)

[...]

I've received a few watch notification for AMKT issues just closed as Won't Fix by jkodumal ~4 hours ago, e.g. AMKT-4509/[AMKT-4510|https://ecosystem.atlassian.net/browse/AMKT-4510]/[AMKT-4602|https://ecosystem.atlassian.net/browse/AMKT-4602]/[AMKT-6358|https://ecosystem.atlassian.net/browse/AMKT-6358] - I've visited a few issues for details now and am slightly disturbed by what I've seen:

• they are still listed with Status=Open and Resolution=Unresolved
• likewise the last updated date seems to reflect the previous activity only
• yet all issue tabs properly reflect John's closing, i.e.Comments, History, Activity and Transitions Summary properly recorded him closing the issues as Won't Fix
• sure enough the issues still show up as Unresolved via JQL now, i.e. the current status is handled consistently at least, see e.g.

  project = "Atlassian Marketplace" and resolution = Unresolved and issuekey = AMKT-4602
  

• other than non formerly closed open issues they don't offer the Return to Triage transition anymore, so the workflow system seems to know about the intended current state Closed not offering that transition in fact

How is this possible? Am I missing something or is this a severe data integrity violation?