Skip to content

Use the actual current period when visiting the usage page #15544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gtsiolis opened this issue Jan 2, 2023 · 10 comments
Closed

Use the actual current period when visiting the usage page #15544

gtsiolis opened this issue Jan 2, 2023 · 10 comments
Assignees
Labels
component: usage feature: billing meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code

Comments

@gtsiolis
Copy link
Contributor

gtsiolis commented Jan 2, 2023

Problem to solve

Usage periods now start and finish on the actual billing cycle date, see #14363, #14485, and relevant discussion (internal).

However, 🅰️ the usage page is using by default the beginning of the month and the current date as a start date and the end date accordingly and 🅱️ visiting the usage page from the billing settings links to a different view.

Cc @svenefftinge because #14515

Proposal

Use the actual current period when visiting the usage page.

Example period BEFORE AFTER
billing usage-before usage-after
@bonysureliya
Copy link

I am interested to work on this issue can you please explain the issue more precisely .

@gtsiolis
Copy link
Contributor Author

Hi @bonysureliya! When you go to personal usage (/usage) or your team usage (/t/:team/usage), the selected period (from, to) in the page header and of course the data below should match the current period found in the corresponding billing page.

For example if you see Jan 1, 2023 – Feb 1, 2023 as the current period on the billing page, going to usage should filter the default view with these dates. Currently, usage default to the first of month (from) and today's date (to).

Feel free to open a PR and link back to this issue. 🏓

@bonysureliya
Copy link

Ok i am working on this issue and i will let you know if i need help

@bonysureliya
Copy link

What we can do is gather the current date as end date (To date) and start date as the today's date of previous month (From date)

@mittallakshayy
Copy link

I someone currently working on this ?

@gtsiolis
Copy link
Contributor Author

@mittallakshayy I think it's safe to assume that no one is actively working on this as there's no assignee from the team and the last comment from @bonysureliya was 3+ weeks ago. Feel free to open a PR and link back to this issue. 🏓

@bonysureliya
Copy link

I am currently working on this waiting for the issue to get assigned

@gtsiolis
Copy link
Contributor Author

@bonysureliya I generally avoid assigning anyone outside the team to avoid blocking community contributions to stale issues that never get a PR which is very common across open source projects. However, I like challenging this approach—assigned!

@stale
Copy link

stale bot commented May 21, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label May 21, 2023
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label May 26, 2023
@gtsiolis gtsiolis mentioned this issue Jun 2, 2023
14 tasks
@stale
Copy link

stale bot commented Sep 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 16, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
@github-project-automation github-project-automation bot moved this to In Validation in 🍎 WebApp Team May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: usage feature: billing meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code
Projects
Status: In Validation
Development

Successfully merging a pull request may close this issue.

3 participants