Skip to content
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

Option to have different user timezone and job time done selection in job manager #719

Open
3 tasks
ravilodhi opened this issue Aug 2, 2024 · 3 comments
Open
3 tasks
Assignees

Comments

@ravilodhi
Copy link
Contributor

What is the motivation for adding/enhancing this feature?

Option to have different user timezone and job time done selection in job manager. Currently it is very hard to manage job timezone. By enabling user to manage different job timezone will help to schedule job in different timezone.

What are the acceptance criteria?

There should be one separate setting on the setting page for job timezone. The new job scheduling should be scheduled in the job timezone only.

  • ...

Can you complete this feature request by yourself?

  • YES
  • NO

Additional information

@ravilodhi
Copy link
Contributor Author

@ravilodhi ravilodhi moved this from 📋 Backlog to 📅 Planned in Digital Experience Platform Aug 13, 2024
@amansinghbais amansinghbais moved this from 📅 Planned to 🏗 In progress in Digital Experience Platform Aug 13, 2024
amansinghbais added a commit to amansinghbais/job-manager that referenced this issue Aug 14, 2024
amansinghbais added a commit to amansinghbais/job-manager that referenced this issue Aug 20, 2024
@amansinghbais amansinghbais moved this from 🏗 In progress to 🛑 On hold in Digital Experience Platform Aug 20, 2024
@amansinghbais
Copy link
Contributor

amansinghbais commented Oct 21, 2024

While updation of job, when we are sending the execution timezone as recurrenceTimezone the runTime not updating based on recurrenceTimeZone. Need to look around this. Hence made this on hold. Will pick it again.

@amansinghbais
Copy link
Contributor

Looked around this, need to look around the backend implementation of recurrence timezone. Because from the frontend point of view it seems like recurrence timezone not working properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🛑 On hold
Development

No branches or pull requests

2 participants