Feature request: Expiry date field
Comments
-
Thanks for the interest tomabg I'm pretty excited for the future. Hang in there. Please do keep an eye on this topic. I'm sure we'll make an announcement here and/or in the labs section.
0 -
+1 For this feature
This is epecially useful for the
op pluginintegration to set github/gitlab tolen expiry1 -
Thanks for your interest in this @oschrenk Hopefully, we'll have more to share before long.
https://1password.community/discussion/comment/713007/#Comment_713007
0 -
Is there an expected release date yet for when this feature will be available?
0 -
@Max_ag I see it's now nearly 3-months since I posted on this thread and topic. It sure seems like a long time for 1Password to implement this field request system wide, that is already in some category items. With software subscriptions now being ubiquitous, it comes under the heading of a must have. Having been with 1Password since the early days it sure seems like it takes far too long for such a straight forward implementation to be made possible.
0 -
Hey @wsgatesnz ,
It's actually very much in the end stages of development and it should hopefully be live in our October release!
There's a few reasons that it takes a minute for us to get things in place and I'm happy to outline the process a little here in the hope it explains why it can take time.
Designing a feature we have to spec it out for all the platforms that we support, this means it has to be designed and specced for android, iOS, Desktop, Web etc... and our engineers work with our designers to identify limitations or potential pitfalls which is a collaborative back and forth process of course but we'd rather do that then give them a design at the end of the process and then be told it's not possible, that's not good product design process.
In this instance we already had it for some existing item types but we're making technical changes so we need ensure they are backward compatible etc... So it can certainly take a good few weeks for us to ensure that our designs have thought through the edge cases - and even then we may not get them all!
We also have to understand and think through the implications of any release. For instance implementing it for a consumer customer vs how we might implement it for a business customer. An example could be do we need to implement new policies for admins to enforce? Or maybe we might need to change / deprecate certain features to make it easier to discover as a feature, or we may need to update navigation and any tradeoffs that come with that.
Then when building features or making bigger updates to them we have to make the changes in our core architecture and then also have those reflected across our client applications so that it works everywhere, which is an array of skills and people so means everything has to line up in terms of our resourcing.
Outside of that we then have our QA and release process, where our features go through the nightly, beta and stable launches which inherently adds weeks to the launch of any feature.
So all that is to say that it's an involved process and what may seem like a straightforward update can take a few months to get into production.
I'm super excited to see the feature live and it's really genuinely coming soon, we're almost there I promise :)
Max
1 -
Can't wait for this one! Such a drag adding sporadic calendar entries for expiring passwords..
0 -
Hey hey, so we're in our testing out internally period, we had to make some changes which delayed it slightly but we're looking to be code complete in the next 1-2 weeks. All being well this means we should see it out in one of the next releases in early November. Thanks, Max
1 -
I'm checking the forum every day in hope of the release of this feature, but after all this talk that it should be released in oktober, then early november, still nothing.
Is it coming this year for sure?0 -
Came looking for a solution to this and excited to see that this feature is almost ready for launch!
0 -
@Max_ag and @martim don't get too excited I feel I have been waiting a lifetime now with expected release dates given and gone without any further update. For a high price solution 1Password seems to be totally focused on business solutions. As an early adopter of 1Password (v3) I am very disappointed at the value proposition this app now gives me as a single/family user.
0 -
@wsgatesnz I have a business account and I dont understand why this feature is not requested by every company. How much time you can save if you do not let your password get locked by changing it in time.
But it seems to be very very hard to implement this function that should just remind me of something.
As I said, lets hope it still arrives in 2024...0 -
I would also like this feature. Especially for API tokens that only last a year before renewal.
1 -
@Max_ag Hey, it's early December now. The last Update to this topic was a release in early November and there were no updates since.
Can you please give us a feedback on where you are with this implementation?
It is kind of sad to get a release date and then the feature does not come and there are no more comments on why it is not coming.We are also a paying company and I would like you to communicate with your members. Especially if the interest in this Topic is not by just one person.
0 -
@Max_ag and @Safiras I'm so in agreement with Safiras. Very disappointed with broken promises for a date of release for expiry dates. We live in a world of security where date changes are part of running a secure identity. How can it take 1Password so long to implement what seems like a simple update. For a paid subscriber base I expect a better response from a company which listens to it customers needs
1 -
Hello 1P. Why the silence? You are not doing yourselves any favours by not responding to the many requests for this feature to be made available again.
The last response from someone in 1P was on October 18; close to two months ago!
0 -
Hello folks,
I'm sorry for the delay in responding. The team is currently testing the new feature internally and is still working on implementing feedback from that internal testing so that we can ensure that the feature is polished and bug free upon release.
I don't want to promise a specific release date at this time but I did want to assure everyone that the team is actively working on the feature and we hope to make it available for testing in the nightly and beta versions of 1Password as soon as we can.
I'll update this thread when I have more news to share. Thank you to all who have expressed their need for this feature, the team is excited to share this new functionality with everyone. 🙂
-Dave
3 -
I believe this feature would help with placing dates and notifications on websites and services with annual renewal fees. The email notices about upcoming renewals get lost in the inbox but having a consolidated alert mechanism via 1Password that an annual renewal was upcoming would be awesome. Looking forward to the release.
0 -
Just today, I renewed a certificate that expired yesterday.
It was pure luck that I saw it today - which could have been prevented with an Expiry field in 1Password.
Please guys, I'm waiting every day for news on that topic - we really need this feature.
Are there any updates/news on that?0 -
Hello folks,
As of today, the team has started a gradual roll out of item expiration dates/notifications to those on the beta and nightly versions of the 1Password app. If you'd like to test drive the new feature then update to the beta version of the app: Use 1Password beta releases
We hope to finish rolling out the feature to all beta/nightly users by the end of the month and you might not see it right away even after switching to the beta/nightly. The feature will be released to the stable version in the future once the beta testing process is complete.
We're excited to hear what you think!
-Dave
4 -
Thanks @Dave_1P, this is a great new feature! One question/comment regarding the alert for the expiry date: how does this alert relate to the existing alert that shows up in Watchtower for an item that's near its expiration date? Playing around with the field, it seems like it's about 2 months before?
But it also seems that this alert is different than the one we can configure, since the default is that the alert schedule is "None". IMO it's a little confusing to have these two ways of displaying the expiration date if they behave the same way. If they don't behave the same way, could you explain the difference? My first impression would be that the default for an expiration date should be to have the alert display 2 months before (or whatever the actual interval is) instead of None.
Basically, my question is whether the 2 fields below are the same. If not, why not and how are they different, and if so, could they please be configured to display the same way?
Thanks!
0 -
This is GREAT news this long awaited feature comes to fruition!
A feature I first requested 7 years (!) ago in 2018 (and I had lost hope would be picked up):
https://1password.community/discussion/87958/expiry-reminder/p1Im allready running beta channel and can see the new "date" field I will start making use of now.
0 -
Thank you for the feedback! I've shared this with the team and there's already discussion happening to add default expiry alert labels to items in categories that have expiry dates built-in in the future. This will provide for a more consistent experience.
I'm glad that you finally have your hands on the new feature! Thank you for championing this feature request! 🎉
-Dave
ref: dev/core/core#34229
1
