Active
Project:
Conflict
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Feb 2021 at 15:53 UTC
Updated:
26 Feb 2021 at 17:44 UTC
Jump to comment: Most recent
Problem/Motivation
On an issue with multiple Related issues, the UI makes you think you can rearrange them in an order of your choosing.
However, after dragging them into an order you prefer, the order does not persist.
Steps to reproduce
1. Find an issue with multiple related issues, such as I just tried this twice on #3200500: Strongly discourage clicking Merge on GitLab pages (or make it work)
2. In the Related Issues field, drag the related issues to a different order.
3. Save the issue. I would expect to see the order I set used in the sidebar and in the field edit area. But neither of those actually happens -- they go back to their own preferred order.
Note: I was able to make the ordering "stick" by clicking "Show row weights" and setting the numbers manually.
Proposed resolution
Investigate. Fix.
Comments
Comment #2
drummThis is a View defined in project issue module. I haven’t ordered fields by deltas before, but that should be possible.
Comment #4
drummThat's an easy fix, but I totally missed
This is probably a side-effect of conflict module, trying to resolve any changes made by others between when you load the issue page and save it. Multi-value fields are a bit of a special case, the fix for this will probably be in the neighborhood of what was changed in #2552405: A patch uploaded by user X in comment N mysteriously appeared in a comment by user Y in comment N+4 after cross-posting with user Z.
Comment #5
drumm