Im experiencing again the same problem. Some issues show different status from the issue view or from a search.
There is a Listener involved that catches all "commented" or "file attached" events, and reopens the issue if closed and the comment/attachment is done by the reporter. Is a legacy Listener and there are no errors in atlassian-jira.log or other logs. Performing an "background reindex" does not fix the inconsistency of the status.
The code of the relevant parts of the listener:
public class ReabrirOnReporterActivity extends AbstractIssueEventListener implements IssueEventListener { ... public void workflowEvent(IssueEvent event) { ... if ( .... some conditions ...) { boolean wasIndexing = ImportUtils.isIndexIssues(); ImportUtils.setIndexIssues(true); MutableIssue mIssue = vIssueManager.getIssueObject(event.getIssue().getKey()); // perform the transition as the user that generated the event this.workflowTransitionUtil.setIssue(mIssue); this.workflowTransitionUtil.setUsername(event.getUser().getName()); this.workflowTransitionUtil.setAction(c.getTnIDAportar()); this.workflowTransitionUtil.validate(); this.workflowTransitionUtil.progress(); mIssue.store(); // deprecated! ImportUtils.setIndexIssues(wasIndexing); .... }
Some time ago I opened the same question: https://confluence.atlassian.com/display/JIRAKB/Different+Issue+Status+between+the+View+Issue+Screen+and+the+Issue+
But this time is on 5.2.7.
Thanks.
Community moderators have prevented the ability to post new answers.
Solved by reimplementing the listener to use IssueService, as suggested here
and working at this time :)
>Is a legacy Listener
That rings alarm bells - has it been recompiled and re-tested against the current version? I've seen stuff that works fine in 5.0 pretend to work fine in 5.2 and actually be silently failing because it needed recompiling.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the code is copy-pasted from previous versions but is compiled against 5.2.7 SDK.
Legacy means that does not use the new listener interface: https://developer.atlassian.com/display/JIRADEV/Writing+JIRA+event+listeners+with+the+atlassian-event+library, but extends from AbstractIssueEventListener
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.