This is a trick to fix a bug that has a single user. If the custom fields drag-to-sort feature is only used to solve this kind of rare issue, I wonder why the time has been spent to drag-to-sort Custom fields instead of URIs that so many users need everyday.
@Christop, probably nowhere, considering that vault items are generally for credential storage, and consequently contain private information which shouldn’t be shared with you.
However, I use them frequently, so I know. It’s also inherently evident - if an action causes some JS to dynamically generate an HTML checkbox, the actions to invoke that JS and then check the box shall necessarily be ordered. Being able to quickly reorder such processes means that complex chains of actions aren’t painful to create.
This is a really weird thing to doubt, especially since you appear to support this FR.
Not sure I understand your position. Are you arguing that Bitwarden should remove the ability to re-order custom fields?
1 Like
This is a really weird thing to doubt, especially since you appear to support this FR.
I don’t understand why you are saying this. This FR is about URI ordering, not about Custom field ordering.
As no concrete example of Custom filed ordering is provided, I am questioning why Drag to drop implementation time has been spent on Custom field and not on URI.
I do not request to remove for Custom fields Drap to sort. I am trying to understand why precious time was spent on Drag to sort for Custom fields and not for URI. Honestly, this is driving me mad each time we need to make annoying time-consuming stupid actions to order URIs when this is made in 1s for Custom fields which we NEVER use. (the worse is that Custom fields are in plain sight in the UI when you have to deal with URI !)
@Christop, because nobody has bothered. I’m almost certain that this wouldn’t require a significant amount of effort. However, the Bitwarden team is prioritising different things currently. Although BW is managed by an organisation with a net positive revenue, it’s also FOSS - we’ve demonstrated our support already by upvoting this post, so if you want to see this feature any quicker, open a PR.
I cannot understand why you care what the original rationale to implement it for HTML elements rather than URIs was, if any explicit decision to prioritise one over the other even existed. I’ve provided a very probable answer to this in lieu of a response from a team member, but you appear to be unsatisfied unless I provide something verifiable. That’s unreasonable.
1 Like
@Christop, indeed. Everyone else subscribed to this thread shares this sentiment.
What is a PR? What is the difference between a Feature Request and a PR?
I might have missed something: I thought software features were implemented according to priorities/complexity. Here we have 2 things ‘Custom fields’ and ‘URI’ ordering that have the same complexity (it is the same UI). But the priority is not the same, for users, URI sorting is much more frequent than Custom fields sorting.
Based on this, time is better spent on URI sorting.
1 Like
The very first post make it clear that it is both… “It would be great if there was a way to reorder URI’s and custom fields instead of copying > pasting > deleting.”
Yes, that is generally how the world works, but do realize that it is the decision maker’s priorities that matter, not yours nor mine. For all we know, Bitwarden management may have landed a 10,000 seat organization by adding the feature you feel less important.
PR is “Pull Request”, a Github term for asking that Bitwarden incorporate code that you developed into the official code base. FR is “feature request”, a term specific to this community, where we are helping Bitwarden gauge the popularity of various ideas with our votes – and hoping to influence Bitwarden’s own development prioritization.
1 Like
Yes, you’ve missed something: Bitwarden is an open-source project, which accepts community code contributions when appropriate. The time/effort spent by Bitwarden’s own developers is determined by the company’s current priorities and available resources. However, if a community volunteer contributes code for a new or improved feature, and if the feature makes sense for Bitwarden to add/modify, and if Bitwarden staff have the bandwidth to do code reviews and quality control checks on the contributed code, then such user-initiated contributions can fast-track release of a feature that otherwise might have taken much longer for Bitwarden developers to get to on their own.
In this case, an open source community member named Kevin Woblick contributed code to implement drag-and-drop sorting of custom fields (PR 35, PR 237, and PR 906) in 2019, and this contribution was ultimately approved and released by Bitwarden.
So, the answer to your question is that in 2019, Kevin Woblick decided that drag-and-drop sorting of custom fields was sufficiently important to him to develop and contribute the necessary code, but for some reason, he did not feel the same way about sorting of URIs. If you really want to know why he only implemented drag-and-drop sorting for custom fields (and not for URIs), you would have to contact him to ask directly. But in my opinion, this would be looking the proverbial gift-horse in the mouth.
4 Likes
That’s very interesting, thank you for providing this insight. I was truly missing a point and your explanation fully clarifies this now.
Next time I see this Customer Field Drag to sort feature I will like the good initiative from Kevin (though I never use this feature) instead of having the frustration of seeing that time was spent on the wrong feature (forcing us to continue doing nasty URI copy/paste).
This is a difference between open-source and none open-source software.
1 Like
Not really. The light-bulb moment was realizing you are not in the position to direct somebody else’s priorities. You might want to reflect on why you are grateful now that you know it was a volunteer, but were angry when you believed it was an employee that is “not yours”.
If you truly value url-drag, do as Kevin did and make a (programming) investment that you can use to apply greater influence on Bitwarden’s decision makers.
2 Likes
Slightly easier work flow:
- copy the first item
- Click new-url; paste, set the match detection.
- Copy the formerly last item; delete it.
- Paste over the now-redundant first item and maybe update its match detection.
- Take a look to ensure everything looks correct before saving the entry.
1 Like
You are interpreting things and trying to put this in other people’s mouths:
- you can see above that I have asked for Custom field examples and you provided none. So I am not talking about my point of view, it is also yours due to the lack of examples.
- when we celebrate another person, it does not mean we undervalue you.
@Christop, Control + Z (undo) and Control + Shift + Z (redo) are your best assets in this situation - if you use them, you can easily swap two URIs without having to paste anything outside Bitwarden.
I concur with @grb’s earlier example and @rokejulianlockhart’s earlier observation “If they were unordered, they would be rendered useless at pages with complex behaviours.”
1 Like