Note required permission for setting assignee (#128)

Author: Mossop

.secrets.baseline

@@ -106,7 +106,7 @@
         "filename": "README.md",
         "hashed_secret": "04e78d6e804f2b59e6cb282cb9ed2c7bfd8a9737",
         "is_verified": false,
-        "line_number": 183
+        "line_number": 184
       }
     ],
     "config/local_dev.env": [
@@ -126,5 +126,5 @@
       }
     ]
   },
-  "generated_at": "2022-07-14T17:13:15Z"
+  "generated_at": "2022-07-21T07:58:50Z"
 }

README.md

@@ -91,7 +91,8 @@ features on top of the default.
 
 It will attempt to assign the Jira issue the same person as the bug is assigned to. This relies on
 the user using the same email address in both Bugzilla and Jira. If the user does not exist in Jira
-then the assignee is cleared from the Jira issue.
+then the assignee is cleared from the Jira issue. The Jira account that JBI uses requires the "Browse 
+users and groups" global permission in order to set the assignee.
 
 If configured, the action supports setting the Jira issues's status when the Bugzilla status and resolution change.