This PR changes the way roles are exported in the current version of the collection. Previously, every single permission role was added as a separate entry. I've modified it so that objects related to a role are matched with that role. As a result, the entry for a role is now presented as follows.
Thanks to that, the number of requests sent to the API is decreasing.
Let me know what you think. If you have any suggestions, I would be grateful.
Additionally, there are two changes: one related to the approval role, which I fixed for teams but not for users, and another issue with the job template admin, project admin, and similar roles. These roles are exported without underscores, which prevents them from being imported.
How should this be tested?
1) Use filetree_create to create export.
2) Use filetree_read to load export.
3) Use dispatch to import.
What does this PR do?
This PR changes the way roles are exported in the current version of the collection. Previously, every single permission role was added as a separate entry. I've modified it so that objects related to a role are matched with that role. As a result, the entry for a role is now presented as follows.
Thanks to that, the number of requests sent to the API is decreasing.
Let me know what you think. If you have any suggestions, I would be grateful.
Additionally, there are two changes: one related to the approval role, which I fixed for teams but not for users, and another issue with the
job template admin
,project admin
, and similar roles. These roles are exported without underscores, which prevents them from being imported.How should this be tested?
1) Use filetree_create to create export. 2) Use filetree_read to load export. 3) Use dispatch to import.
Is there a relevant Issue open for this?
N/A
Other Relevant info, PRs, etc
876