Repository navigation
8366: Allowed multiple departments per project - #33
Merged
Merged
Conversation
jeppekroghitk
approved these changes
Sep 25, 2026
Comment on lines
+10
to
+14
| * [PR-33](https://github.com/itk-dev/itk-projects/pull/33) | ||
| Let a project be anchored in several departments: the department field is now | ||
| a many-to-many relation edited with a searchable multiselect, and shown as a | ||
| list on the project page, in the list and in the CSV export. The dashboard | ||
| counts a shared project under each of its departments. |
Collaborator
There was a problem hiding this comment.
These are getting a bit long imho
Contributor
Author
There was a problem hiding this comment.
Fair, i will make them shorter!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to ticket
https://leantime.itkdev.dk/#/tickets/showTicket/8366
Description
Note
Dashboard changes makes certain assumptions, but this will be handled by a separate PR.
Checklist