Medium Issue Summary
User with Assets Developer or Manager permission is unable to export object
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create an Object Schema and add multiple objects
- Create a User: developer1
- Add the user to Object Schema --> Configure --> Roles --> Add User 'developer1' to Object Schema Developers or Object Schema Managers role
- Add the user to Object Type --> Configure --> Roles --> Add User 'developer1' to Object Type Developers or Object Type Managers role
- Login with 'developer1'
- Navigate to Object Schema (for which developer1 has the above role)
- Select the Object Type
- Try to export Objects from the ObjectType
Expected Results
Object should be exported successfully
Actual Results
We get an error message related to permission: Sorry, you do not have permission to perform this action.. PermissionInsightException: User JIRAUSER10200 didn't have correct permission (admin)
Workaround
Navigate to the Assets Object Navigator (Assets>Search for Objects), Use an IQL to filter by your Object Type, and add all Columns to the filtered results. You should be able to export your Object Type from here.
[JSDSERVER-12213] Users with 'Object Type Developers' is not able to export Objects
That's incredible, the problem persists in version of Jira server 8.20.17 and assets plugin 2.0.11
Please Atlassian, reopen this ticket and ensure you solved for Jira Server too.
Regards
Hi 2eb49d9bba1d , push columns button and unselect header checkbox "name", then search in the dropdown list the object to search, and then select again only the desired columns for this objectype.
regards
We've just upgraded to JSM 4.20.17 and can confirm that the Insight export functionality that was broken in .15 and .16 now appears to be working as needed.
We are still expecting Atlassian to fix this feature in the meantime I have a question about the workaround.
When I filter by Object Type – How can I add the Columns just for THAT Object Type and not All Columns for the ENTIRE Schema??
Previously we had to paid for insight, a lot, because it is not cheap precisely. So, this is a BASIC option, we use it a lot daily. We need a solution now, we demand a solution now, because we worth it due the costs of Atlassian have. How is possible these kind of errors happen?. You are promotting continuous delivery, development, integration, etc... i can't belive this unit tests woudn't be passed and Atlassian deploy the version inspite of.
Atlassian do something according to this please and reopen the issue.
Regards
This issue is not fixed. The work around is not easy to do and will require retraining of user several teams. Using the Export Objects option from the Object Type was simple and available at all permission levels. We would like to have this feature fixed.
This is not a fix. It is a work around. It is cumbersome, and it will require re-training several teams. I personally need to export an entire table with all its fields for an import to another tool. If this will not actually be fixed, that option needs to be removed as our users will continue to get that error and submit tickets to us.
I had same problem, the update to 8.20.16 not fix the problem 
I have the jira server 8.20.16 but still in the app "Asset Pluggin" 8.20.15 version , you are not published the 8.20.16 for the pluggin yet.
This workaround is usless. As the export from filter changes Jira user from actual person to jirauserxxxxx.