Can be examined from a Listener:
package com.netic.eventlistener
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.link.IssueLink;
import com.atlassian.jira.issue.comments.CommentManager
import com.atlassian.jira.util.JiraUtils;
import com.opensymphony.workflow.WorkflowContext;
import com.atlassian.jira.event.issue.AbstractIssueEventListener
import com.atlassian.jira.event.issue.IssueEvent
class EventListener extends AbstractIssueEventListener {
@Override
void workflowEvent(IssueEvent event) {
String IssueType = event.issue.getIssueType().name
String ProjectName = event.issue.getProjectObject().name
String IssueKey = event.issue.key
String EventId = event.getEventTypeId()
System.out.println("Event: " + EventId)
}
}
Reference: https://jamieechlin.atlassian.net/wiki/display/GRV/Listeners and Script Runner Listener and https://ecosystem.atlassian.net/wiki/display/JTOOL/Auto+Transition+Listener
| Event | ID |
|---|---|
| Issue Created | 1 |
| Issue Updated | 2 |
| Add/Remove Attachment (Issue Updated) | 2 |
| Issue Assigned | 3 |
| Issue Resolved | 4 |
| Issue Closed | 5 |
| Issue Commented | 6 |
| Issue Reopened | 7 |
| Issue Deleted | 8 |
Issue Moved The Event is fired for the target project, not the source | 9 |
| Work Logged | 10 |
| Work Started On Issue | 11 |
| Work Stopped On Issue | 12 |
| Generic Event | 13 |
| Issue Comment Edited | 14 |
| Issue Worklog Updated | 15 |
| Issue Worklog Deleted | 16 |
| Issue Comment Deleted | 17 |