-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.12.0
-
1
-
Severity 3 - Minor
-
Issue Summary
When a custom field with the "Make filter assign strict" option selected is added to an issue, whenever the assignee/reporter is changed, the custom field takes up to 30 seconds to update, but the screen stays held while waiting for the update.
Assets Customfields with Filter Assign Scope should update the field in the background, as currently it's performed in the foreground, causing slowness every time the reporter/assignee is changed.
This is reproducible on the Data Center: yes
Steps to Reproduce
- Configure an Assets custom field referencing an object type that has a user attribute (see the screenshot below).
- Set this field with the Filter Assign Scope. The filter uses the reporter smart value as the reference
- Whenever the reporter is changed and Jira has many users, the field takes too long to update. This update is performed in the foreground, holding the page refresh for 30 seconds. This field update shouldn't be holding the page refresh.
Expected Results
The page refresh shouldn't wait for the field update and hold the screen.
Actual Results
Nothing is added to the logs, as this is not an error, but the screen keeps waiting for the field update.
Workaround
The workaround is to setup an automation to update the field in backgrouns intead of checking the Filter Assign Scope attribute in the field configuration:
1 - Create an Automation Rule that triggers when an issue is created or edited.
2 - Create a "Send Web Request" action to get the ObjectID from Assets related to the reporter user:
2.1 - You have to create a secret to authenticate in Jira API, you can generate from the command line:
echo -n "user:password" | base64
Replace with your username and password. You can add it directly in the automation header field or add using a Jira Automation secret.
2.2 - Action configuration:
Webhook URL (replace your Jira Base URL):
https://<JIRA-BASE-URL>/rest/assets/1.0/aql/objects?qlQuery=%22Jira%20User%22%20=%20%22\{{reporter.displayName.urlEncode}}%22
Headers:
- Authorization: Basic <BASE64-AUTH-OR-SECRET>
- Content-Type: application/json
Type: GET
Mark the "Wait for response: Delay execution of subsequent rule actions until we've received a response for this webhook"
3 - Then add the Edit issue action, do not choose any field and on "More options" use this in the "Additional fields":
{ "update" : { "customfield_10518" : [{"set": [{"key" : "{{webhookResponse.body.objectEntries.get(0).objectKey}}"}]}] } }
- links to
- mentioned in
-
Page Loading...