This is a static sorting (like "By Date Created") where you can't change point values by dragging.

This is still a little more sensical than changing the date created though, isn't it?

This is still a little more sensical than changing the date created though, isn't it?

Changing point values is definitely an actual operation. The major issue is that if you drag a card between other cards with values "10" and "39,000", what value do we assign? 10? 39,000? 11? 38,999? Average them to produce 19,505? All these answers are probably wrong under some schemes like "Always Assign Fibonacci Numbers as Costs" which is a Real Thing that has a wiki page:

https://en.wikipedia.org/wiki/Fibonacci_scale_(agile)

I think the only good answer is probably "Prompt the user to pick a number between 10 and 39,000 inclusive", but I think they probably might as well just click the edit icon to do that anyway. We could tweak this if we get a pile of feedback or something (or let you configure a discrete set of possible point values, then put headers on this view if you do) since there's no fundamental problem with the underlying operation.