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

Plans show incorrect start and end time in time list view #5605

Closed
3 of 7 tasks
akhenry opened this issue Aug 3, 2022 · 3 comments · Fixed by #5604
Closed
3 of 7 tasks

Plans show incorrect start and end time in time list view #5605

akhenry opened this issue Aug 3, 2022 · 3 comments · Fixed by #5604

Comments

@akhenry
Copy link
Contributor

akhenry commented Aug 3, 2022

Originally reported in #5534

Summary

Day 1 Plan displays properly in this view
plan1

Day 1 Plan in Time List view: dates and to/froms are not displaying properly
plan2

Steps to Reproduce

  1. View a Plan with Time Conductor (TC) settings such that activities in the plan are in view. Confirm start dates and durations are correct or at least plausible.
  2. Drag the plan into a Time List view with the same TC settings.
  3. Observe that the starts and to/from values are not the same as in the Plan view.

Environment

  • Open MCT Version: release/2.0.5
  • Deployment Type: VIPER test

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

@akhenry
Copy link
Contributor Author

akhenry commented Aug 3, 2022

Test instructions

  1. Follow the reproduction steps in the original issue
  2. Verify that the timestamps shown in the start and end columns are within the configure conductor range.

@unlikelyzero
Copy link
Collaborator

@charlesh88 to tackle

@charlesh88
Copy link
Contributor

Verified fixed Testathon 8/22/22.

@unlikelyzero unlikelyzero added needs:e2e Needs an e2e test and removed unverified labels Aug 23, 2022
@unlikelyzero unlikelyzero added this to To triage in Improve Test Coverage via automation Aug 23, 2022
@unlikelyzero unlikelyzero added this to the Target:2.0.8 milestone Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

3 participants