@stlaz which fields exactly?

You have tickets rights so you should be able to adjust all the ticket fields but you're running into the issue @vivekanand1101 fixed in https://pagure.io/pagure/pull-request/2011

@vivekanand1101 Milestone + all custom fields.

@pingou Thanks, I see. Milestone is not a custom field, though, and I can't set it in the metadata. Therefore this is either UX issue or a real issue :)

So the actual problem is that the values of the fields that the user probably can update but not via the Web UI are always reset to None.
This needs the be fixed yesterday as any such user will mess any such ticket up. This is very bad.

So the actual problem is that the values of the fields that the user probably can update but not via the Web UI are always reset to None.

Which fields? I have tried to fix these kinds of problems in #2011 and #2045 . It would be more helpful if you could name the fields

@vivekanand1101 You can see in https://pagure.io/freeipa/issue/6346#comment-424642 which fields were updated. Namely:
- Custom field affects_doc
- Custom field component
- Custom field rhbz
- Custom field test_coverage
- Custom field tester
- Custom field type
- close_status
- milestone

The problem still persists, our "ticket" tried to assign himself to an issue which effectively reset all the custom fields.

I think I found the root cause for this and I have a fix ready

is this fixed?

I believe so, thanks for catching this :)