Show expiring date in addtion to countdown date for Expiration date on Memberships feature
Description
Once an expiration date is assigned to an individual or group member, clarity as to the actual date of expiration is lost when only showing a relative duration. This makes it difficult to compare the "countdown timer" in GitLab vs a specified expiration date such as it would be specified in a license agreement or contract.
In my org's use-case, we are performing several thousand group-project shares that require an expiration. Seeing only the remaining relative time obscures the contract specified dates.
Proposal
On the Share project with other groups page, immediately after where the countdown time is for each individual / group share, show the actual date of expiration.
The current one doesn't look like clickable. Change the "remove" button to look like a button.
| Current | Proposed |
|---|---|
 |
 |
Links / references
Activity
mentioned in issue gitlab-foss#21619 (closed)
-
Can we get an update on this? A customer reached out to us voicing their frustration that this hasn't received feedback. /cc @DouweM @mydigitalself
Edited by Cindy Pallares 🦉 I think it makes sense to show "expires on March 10, 2017" instead of "Expires in one day".
/cc @mydigitalself
@DouweM not a ~Frontend issue?
@mydigitalself You're right, I guess it is!
added frontend in GitLab FOSS label
@tauriedavis @sarahod : There must be many usability arguments / studies that talk about showing absolute timestamps versus relative ones in different contexts. Usually it's timestamps that happened in the past. This one is looking forward into future. Can you give us some guidance here? Show both? Show one or the other? Show one or the other upon some UX interaction? Also an opportunity to establish some GitLab app-wide design guidance if it hasn't already been done.
Edited by Victor Wu@victorwu (cc @tauriedavis) The problem with a relative timestamp is that it forces a user to manually calculate when the membership actually expires. From the research studies I've done so far, there have been a lot of people who use GitLab with third party contractors, customers, etc. I'd imagine most projects have an estimated completion date and subsequently, you'd potentially want to expire the memberships of contractors, customers, etc around the same date. Therefore, the ability to set and view the actual date you want the membership to expire makes complete sense.
However, it's always good to have additional visual cues as to when something is expiring. Some UX examples: a credit card on file is due to expire, the last date for ordering an item is fast approaching, a sale is ending and so on. The thing they all have in common is urgency/immediacy - they're all happening in the next few days. If you show a visual cue too far in advance it becomes redundant and doesn't prompt any action.
I'd propose showing the actual date and as the date approaches, introduce a countdown/absolute timestamp. For example, 'Expires in 7 days'. We don't necessarily know whether a user will need to take action and amend the expiry date of the membership, however, a reminder doesn't hurt.
Edited by Sarah O'DonnellThanks @sarahod . That's a really good explanation. @tauriedavis : If we get a simple design here, I think we can make this an Accepting Merge Requests in GitLab FOSS feature.
Cc @hazelyang I think this is a quick one to take a look at
Edited by Taurie Davischanged milestone to %Next 2-3 months in gitlab-foss
added Platform in GitLab FOSS label
moved from gitlab-foss#21616 (moved)
