Community
Participate
Working Groups
Build 3.5M2 ChangeSet support is a nice addition. In term of polish though, there are 2 entries available in the context menu for editing it. Hence, it is quite confusing for renaming an existing changeset (the top action is actually not doing what you'd expect).
Created attachment 129713 [details] Context menu rearranged (1)
Created attachment 129714 [details] Context menu rearranged (2)
Screen shots includes changes for bug 269830.
Let me know what you think about suggested changes. Please notice that only available items are visible. So when resources/changes are selected, only "Reassign Changes To" is visible. I changed wording since "Add To" is not clear. I think that "Reassign..." sounds better. The same for "Sort..." item.
If possible I would add the "Sort..." item to the View's drop down menu. It would look the same way as in the Repo view.
Looks good, especially the edit actions being top-level again. >I changed wording since "Add To" is not clear. I think that "Reassign..." >sounds better. I assume this is only done for elements that are already assigned and for non-assigned ones I still get "Add To", right? I agree with Tomasz on the sort item.
(In reply to comment #6) > I assume this is only done for elements that are already assigned and for > non-assigned ones I still get "Add To", right? I would like to find one expression for both cases. I thought that "Reassign Changes To" would work for both, those already assigned and those that are unassigned. Maybe just "Assign To" is fine?
Can't you update the label based on whether it's in a working set or not? I think it's better to use "reassign" if the element is already in a working set.
Created attachment 129861 [details] Fix v01
(In reply to comment #8) > Can't you update the label based on whether it's in a working set or not? I > think it's better to use "reassign" if the element is already in a working set. With the patch we will have "Assign To" for unassigned changes and "Reassign To" for those within a change set.
Released to HEAD. New bugs raised: bug 270101 and bug 270102.
*** Bug 205409 has been marked as a duplicate of this bug. ***