Watcher Enhancements

What does this patch provide?

(view as slideshow)
	Adding previous assignee as watcher		Adding watchers at the time of issue-creation

This patch is against 3.1 enterprise and has the following 2 enhancements.

• Add watchers at the time of issue creation: I hacked the relevant jsp's and java code so that the the issue creation form shows an add watcher text box similar to the one seen on managewatchers.jsp.
  • You can select multiple users and when you click "create issue", all valid jira users that were specified in the watchers textbox are added as watchers.
  • Since the startWatching() (or the method named likewise, I forget the name) is called after create-issue and before the related notification-events are queued, all the users attached as watchers also get notification e-mails (if configured that way in the project's notification scheme).
  • If an non-existent jira-user is entered, no error is shown on the GUI (this is the same policy used for attachments). Since issue creation is already done, I decided not to create too much complexity. An error is thrown which could be otherwise caught and appropriate action taken if one might desire.
• Add previous assignee as watcher: I hacked assignissue.jsp and commentassignissue.jsp, there is an additional checkbox below the "Assign to" dropdown. Checking this results in the previous assignee being added as a watcher. This was something of a bother for some of our groups when the issue passes from person to person and sometimes the previous assignees were "left out of the conversation", so to say. This helps address that problem.. somewhat.
  • There are no validations as such... if a user is already a watcher, I leave it for the existing code to handle it.

How to apply the patch

You need to get the 3.1 enterprise source and ofcourse, the patch attached to this page. Before you deploy this patch, make sure you build and deploy the source to ensure that everything is still alright with your jira instance. Follow instructions given in jira documentation.

Once you had done the above, go to jira/src from the BASE_DIR of the the enterprise source and uncompress (tar xvfz jira-3.1-enterprise-patch.tgz). The following files should be deployed.

praveen@ion:~/qa/src/java/atlassian-jira-enterprise-3.1-source/jira/src $ tar tvfz jira-3.1-enterprise-patch.tgz
-rw-r--r-- praveen/praveen 23946 2005-05-19 10:32:48 java/com/atlassian/jira/web/action/issue/CreateIssueDetails.java
-rw-r--r-- praveen/praveen  4895 2005-05-19 10:35:40 java/com/atlassian/jira/web/action/issue/AssignIssue.java
-rw-r--r-- praveen/praveen  6802 2005-05-19 11:26:43 java/com/atlassian/jira/issue/AssignIssueUtilsImpl.java
-rw-r--r-- praveen/praveen   590 2005-05-19 11:39:51 java/com/atlassian/jira/issue/AssignIssueUtils.java
-rw-r--r-- praveen/praveen  4911 2005-05-19 11:43:49 webapp/secure/views/issue/commentassignissue.jsp
-rw-r--r-- praveen/praveen  1839 2005-05-19 11:44:24 webapp/secure/views/issue/assignissue.jsp
-rw-r--r-- praveen/praveen  5195 2005-05-19 11:46:57 webapp/includes/panels/issue/create_fields.jsp
-rw-r--r-- praveen/praveen  1878 2005-05-19 11:51:08 webapp/includes/panels/issue/reporter.jsp

Build and deploy again, and you should be on your way. I am not completely certain, but it may help to remove the work dir in tomcat in order to have the new jsp's compile. You should do this only if you don't see the above mentioned changes.

I have to write this... please test fully before you use it in mission-critical production environments!!! Enjoy.