Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Former Member
4 years agoWrong date/time format MacOS 12.3
when viewing an item in 1Password, at the bottom of the right hand panel that shows the details of the item, the date format does not match the system date format.
My system is set to dd/mm/yyyy ...
1P_PeterG
Community Manager
4 years agoHi thibaultml, thanks for the thoughtful reply.
Thank you however to both of you for acknowledging that the feedback is being received, listened to, and hopefully collected & collated to help prioritise items on the roadmap. And thank you for remaining polite when demanding users — like me — complain about issues they're passionate about. I know first hand how difficult that can be.
I especially appreciate this! And likewise - thanks for the constructive discussion. We get a lot from this process, and especially when folks are courteous and passionate (as you are), we find that we're able to better inform our efforts to achieve genuine excellence. We care a lot about what we do - and we ask for your feedback! - so it's never a problem that you have a point of view on what matters, and what we're doing well, and where we may be coming up short.
The fact that there isn't anything to share doesn't really make me confident nor hopeful that this issue would be addressed any time soon, which I find very disappointing.
That's really understandable. We're somewhat limited, by design, on what we share about features and improvements that are coming through the production process (as well as features which might be implemented at some point, but about which we either haven't decided yet whether to do it, or haven't begun work on it). Among other reasons, this is so that we don't promise things we can't deliver, suggest that a certain feature will show up in one form when it ultimately emerges in another, and so on. And to speak only for myself, even if it weren't a matter of policy I'd personally be hesitant to share certain commitments because I'm not the one who has to design and build the thing. So I want to be conscious of my colleagues' workloads, existing commitments, priorities, deadlines, triage process, surprises that appear at the worst possible moment, and so on.
Sometimes improvements are a matter of "we can get this done in 48 hours, let's just do it and help out the sub-set of affected customers", but often things that appear simple may not be. I can't speak to the particular complexity of this one, but I'll follow up with the development team to better understand the issue as we're taking customer feedback. 👍
I expected Agile Bits, a Canadian company, to understand the importance for its international user base of a non-US-centric approach to software development.
We definitely understand that a global perspective is important - even though this has resulted in design choices that we've taken some criticism for recently. We'll keep trying to find the balance between a general approach that works for everyone, as well as appropriate localizations that make the app feel natural to your locale.
In regards to the regional date question: I'd love to know if this poses a particular problem for your workflow, or in what way it interferes with your app experience. This is a genuine question, not a challenge - and if we can highlight some specifics about it that are particularly troublesome, I can pass that on to our development team, and that will get rolled into the consideration of what happens when. Again, I can't promise anything in particular in terms of a timeline (and understand why that might be frustrating), but we really are tracking the feedback here very closely and doing our best to alleviate the pain points and roll out the cool new features on a schedule that makes sense. And I'd like to make sure that your needs and your use case are well-represented as we're progressing.
Thanks for your understanding - and your comments are truly well-taken!