JRA-9444 Notifications associated with "Issue Resolved" (under "Edit Notifications") does not work all the time. Notifications under this trigger only works sometimes, but mostly not at all.
JRA-9446 Notifications associated with "Issue Commented" (under "Edit Notifications") does not work if the item has been Resolved. (see Detailed Description below)
JRA-9435 Add to Upgrade Guide advice that IssueEvent changelog can now be null
Duplicate
This issue is duplicated by:
JRA-4957 event.getComment() in issueUpdated() returns null if no fields modified (except comment)
When doing an edit issue or a bulk edit and only adding a comment an IssueUpdated event is not thrown. We need to be throwing an issueUpdated event in this case. Be careful, because when just adding a comment (via add comment), we want the issueCommented event to be thrown.
Description
When doing an edit issue or a bulk edit and only adding a comment an IssueUpdated event is not thrown. We need to be throwing an issueUpdated event in this case. Be careful, because when just adding a comment (via add comment), we want the issueCommented event to be thrown.
As requested here's a patch consisting of one file: DefaultIssueUpdater.class
Install instructions follow:
If you are using JIRA Standalone please do the following:
1. Download attached file
2. Copy the file to <jira_install_dir>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/issue/util/ overwriting the file there
3. Restart JIRA
If you are using the WAR distribution of JIRA:
1. Download attached file
2. Rename CvsRepositoryUtilImpl_1.class to CvsRepositoryUtilImpl$1.class
3. Rename CvsRepositoryUtilImpl_2.class to CvsRepositoryUtilImpl$2.class
4. Rename CvsRepositoryUtilImpl_3.class to CvsRepositoryUtilImpl$3.class
5. Copy the file to <jira_install_dir>/webapp/WEB-INF/classes/com/atlassian/jira/issue/util/
6. Run 'build.sh clean' on unix or 'build.bat clean' on windows
7. Run 'build.sh' on unix or 'build.bat' on windows
8. Redeploy the JIRA web app into your application server
9. Restart the application server
Chris Mountford [Atlassian] added a comment - 23/Feb/06 01:01 AM As requested here's a patch consisting of one file: DefaultIssueUpdater.class
Install instructions follow:
If you are using JIRA Standalone please do the following:
1. Download attached file
2. Copy the file to <jira_install_dir>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/issue/util/ overwriting the file there
3. Restart JIRA
If you are using the WAR distribution of JIRA:
1. Download attached file
2. Rename CvsRepositoryUtilImpl_1.class to CvsRepositoryUtilImpl$1.class
3. Rename CvsRepositoryUtilImpl_2.class to CvsRepositoryUtilImpl$2.class
4. Rename CvsRepositoryUtilImpl_3.class to CvsRepositoryUtilImpl$3.class
5. Copy the file to <jira_install_dir>/webapp/WEB-INF/classes/com/atlassian/jira/issue/util/
6. Run 'build.sh clean' on unix or 'build.bat clean' on windows
7. Run 'build.sh' on unix or 'build.bat' on windows
8. Redeploy the JIRA web app into your application server
9. Restart the application server
Bug
Resolved
Critical
When doing an edit issue or a bulk edit and only adding a comment an IssueUpdated event is not thrown
Install instructions follow:
If you are using JIRA Standalone please do the following:
1. Download attached file
2. Copy the file to <jira_install_dir>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/issue/util/ overwriting the file there
3. Restart JIRA
If you are using the WAR distribution of JIRA:
1. Download attached file
2. Rename CvsRepositoryUtilImpl_1.class to CvsRepositoryUtilImpl$1.class
3. Rename CvsRepositoryUtilImpl_2.class to CvsRepositoryUtilImpl$2.class
4. Rename CvsRepositoryUtilImpl_3.class to CvsRepositoryUtilImpl$3.class
5. Copy the file to <jira_install_dir>/webapp/WEB-INF/classes/com/atlassian/jira/issue/util/
6. Run 'build.sh clean' on unix or 'build.bat clean' on windows
7. Run 'build.sh' on unix or 'build.bat' on windows
8. Redeploy the JIRA web app into your application server
9. Restart the application server