Open Bug 1656940 Opened 4 years ago Updated 4 years ago

editing the repository of a phab revision appears to not stick

Categories

(Conduit :: Phabricator, defect, P3)

Tracking

(Not tracked)

People

(Reporter: froydnj, Unassigned)

Details

(Keywords: conduit-triaged)

STR:

  1. Choose a phab revision (I chose https://phabricator.services.mozilla.com/D85766, which is a patch intended for beta).
  2. Click "Edit Revision" on the sideboard.
  3. Click the "x" on the MOZILLACENTRAL repository.
  4. Edit the repository to the RMOZILLABETA repository.
  5. Click "Save Changes"

ER:

The revision shows that it is now directed at mozilla-beta.

AR:

The revision still shows that it is directed at mozilla-central.

The weird thing is that "Edit Revision" after the above does show that the changes stuck, but the actual display of the revision does not, which is somewhat concerning.

I did notice this issue some time ago on my local dev Phabricator -- the actual repo is set correctly on the revision, as Lando will pick it up and the revision will land in the correct repo. The repo that lingers on in the UI is actually set on the Diff and not on the Revision (i.e. if you update/resubmit the diff from the intended repo, it will show correctly).

I can see how it is confusing -- it would be more ideal if the repo on the Diff would match with the repo on the Revision, or if we at least exposed the repo on the Revision detail as well.

Keywords: conduit-triaged
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.