Access to add users to user groups for Worklog Report generates error: is it a bug or access perms?

[rujschafer]

Checklist before you being

• I am sure that I am already using latest version of Jira Assistant
• I had verified that, no similar issues are already reported in issue tracker
• I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
• I had verified that, my query is not answered in FAQ section of website
• I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Browser extension

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Cloud Jira

Version of Jira Assistant

v2.59

What browser are you using?

Chrome

What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.

Windows

Bug Description

Organization switched from hosted Jira to cloud Jira. I am trying to add users to a group so I can generate a report but it gives me the following error in the upper-right most part of the browser window with "Server error: The 'accountId' query parameter needs to be provided".

I dont know if this is a permissions problem with Cloud Jira or if this is a bug. Additionally, this browser extension has not been cleared out since the switchover in case that matters. I could really use help understanding the error and figuring out what to do next.

Checklist before you submit

• I have ensured not to paste any confidential information like Jira url, Mail id, etc.
• I have verified my browser console logs and added necessary details (if required)
• I have added required screenshots if the bug is related to UI (as necessary)

[github-actions]

Hi @rujschafer, thank you for reaching out regarding your issue. Were you using the extension with your hosted instance of Jira?

If so, after your organization switched to Cloud Jira, what steps did you take regarding the extension setup? Specifically, how were you able to use JA with the new Jira instance?

Did you simply change the Jira URL in JA? If that's the case, it may not work properly, as Cloud Jira requires a different type of profile setup. Existing settings and user groups will not function with the new Jira because they involve different configurations.

In this situation, instead of just changing the URL, you will likely need to reconfigure the profile. First, if you have any custom reports, please export them so you can import them later. No other settings will be useful, so there's no need to export anything else. Additionally, if you have any pending worklogs that haven't been uploaded to Jira, you may not be able to use them, as all the IDs and configurations would have changed.

After backing up any custom reports, you should clear the local database of JA.

Here are the steps to clear the JA database:

1. Open JA in your browser and then open Developer Tools by pressing the F12 key.
2. In Developer Tools, go to the Application tab at the top.
3. On the left side, under the Storage heading, expand IndexedDB and select the JiraAssist database.
4. Click the "Delete Database" button to remove your local database.
5. Once the database is deleted, close the extension page and click the JA icon in the top right corner. JA should now behave like a freshly installed extension. Alternatively, you can uninstall and reinstall JA, which achieves the same result. Feel free to choose whichever option you find simpler; both will work the same way.
6. Try integrating with Jira again to see if it resolves the issue.

Note: Deleting your local JA database will remove all settings, reports, pending worklogs (not uploaded to Jira), and JA user groups. However, since you have migrated your Jira to a different instance (from hosted to cloud), you should be fine to delete it.

If you still encounter any issues after this, please press F12, go to the Network tab, and check which API call is failing. Sharing a screenshot of the Network tab’s request and response sections may help me identify the cause of the issue.