#50534 UI - editing custom schema is problematic
Closed: wontfix a year ago by mreynolds. Opened a year ago by mreynolds.

Issue Description

Editing custom schema actually does a delete/add. This causes issues in the UI and CLI. This was partially fixed in https://pagure.io/389-ds-base/issue/50507 - which needs to be back ported to 1.4.0.

In the CLI we need to change the "edit" subcommand to "replace" so it is clear what it is actually doing.


Backport schema fixes to 1.4.0:

320a1b6..f3c18b1 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Next, change CLI to use "replace" over "edit"

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

a year ago

Commit b8c6485 relates to this ticket

f3c18b1..a14dd18 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

a year ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3590

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

13 days ago

Login to comment on this ticket.

Metadata
Related Pull Requests