Hello Anne,
"Issue Updated" covers all issues which have had their details changed that includes Editting an issue, changing the summary, deleting a comment, attaching files to the issue, linking an issue.
I hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think status changes will trigger ISSUE_UPDATED event. Instead workflow event is generated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Status change will only be due to transitioning an issue. In each transition is defined what event is triggered. So you need to check your workflow transitions. If you have in every transition "fire Issue Updated event" then the answer is yes, otherwise no.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FYI: at the time of this writing, emails are NOT generated when an issue is linked to another issue. https://jira.atlassian.com/browse/JRA-14618
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the event fired when watchers were changed?
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.
Does it fire when a new Request Participant is added? (e.g. in JIRA Service Desk)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just did some testing today. When request participants are added or removed, the Issue Updated notification does NOT fire.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does it fire if issue type is changed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is there a way to associate the issue updated event to specific issue types within an issue key?
e.g.
Key is called Help Desk (or HD)
issue types include: infrastructure, risk, softwaredev
I want to create events that use issue updated for each separate issue type within the key HD.
Is this possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nevermind, solved my own problem...
In my condition logic i just added "&& issue.issueType == 'Risk' " after the priority evaluation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.