Skip to content

Improve permission #32

@avdata99

Description

@avdata99

After #30 and #31

If a regular editor user defines IATI fields, it will fail after the resource save in the iati actions so we should only display IATI fields (defined at #30) if the user is a organization admin

Also, we need to ensure we don't loose this IATI fields values when a regular user (no org admin) saves a IATI resource.
So a specific test case is requiered:

  • A org admin creates a IATI file (filling the IATI fields)
  • Then a regular editor updates the resource name
  • Ensure the internal resource IATI extra fields remains with original values

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions