Community
Participate
Working Groups
When a file is "sticky" (i.e. loaded using "Get Contents" from Compare Revision) if is decorated with the revision and the tag (both of which are the file revision number, for example "filename 1.17 1.17 (ASCII -kkv)). A more explicit sticky decorator would be benefitial. This could potentially be applied to version tags as well (although I seem to recall that it is not possible to differentiate branch tags from version tags in some cases).
I'd vote for this. I somehow managed to make a version of one file in my workspace sticky (dont ask me how... I dont remember being prompted) at some point over a week ago. I've been getting test failures in the UI suites but no one else has and it's been vexing me. I'd replace with latest from HEAD on my projects but still they would remain. Only today I noticed (entirely by accident) that one of the files was not getting updated because it was sticky. Decorating the file or providing a list of sticky files would be very useful. Warning the user that the folder they're updating (with latest from BLAH) contains sticky revisions would be even better.
There is currently no plan to address this item.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.