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
