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

Bug/60718 activity field populates automatically #17675

Merged
merged 3 commits into from
Jan 21, 2025

Conversation

klaustopher
Copy link
Contributor

Ticket

https://community.openproject.org/projects/stream-time-and-costs/work_packages/60718

What are you trying to accomplish?

The SetAttributeService used to set a default activity. As we do not consistently use that and a default feels odd according to UX, we should remove it in that place as well

Merge checklist

  • Added/updated tests
  • Added/updated documentation in Lookbook (patterns, previews, etc)
  • Tested major browsers (Chrome, Firefox, Edge, ...)

@as-op as-op self-requested a review January 21, 2025 10:05
Copy link
Contributor

@as-op as-op left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@klaustopher The activity is no longer set by default.

It seems that TimeEntry.activity was automatically set/mandatory before, as there are a few places without a check.

E.g.:
search

The failing spec is one of them.

@klaustopher klaustopher force-pushed the bug/60718-activity-field-populates-automatically branch from 80732d0 to e9459cf Compare January 21, 2025 14:46
@klaustopher
Copy link
Contributor Author

Tests are green

@as-op
Copy link
Contributor

as-op commented Jan 21, 2025

Approved. So I assume the specs without checks make sure themselves the activity is set.

@klaustopher klaustopher merged commit c475c2d into dev Jan 21, 2025
11 checks passed
@klaustopher klaustopher deleted the bug/60718-activity-field-populates-automatically branch January 21, 2025 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants