Open issues
This page provides a curated view of the open issues across the
FedMS GitLab group, grouped by area. For the live, comprehensive
list, browse the projects at
gitlab.lakedrops.com/fedms.
Live data
The lists below are a snapshot. For the most current state, use:
| l3d glab api "groups/fedms/issues?state=opened&per_page=100"
|
Federation
fedms/components/federation
| # |
Title |
Status |
| #34 |
Display structure for users |
ToDo |
| #35 |
Dashboard |
(open) |
| #36 |
User Profile |
(open) |
| #37 |
Organisation Profile |
(open) |
| #38 |
Event Page |
(open) |
| #39 |
Session Page |
(open) |
| #20 |
Status field for event and session groups |
ToDo |
| #21 |
Status field for notifications and delivery |
ToDo |
| #22 |
Activity logging |
ToDo |
| #23 |
Create notifications |
ToDo |
| #24 |
Notification patterns |
ToDo |
| #25 |
Message templates |
ToDo |
| #26 |
Override message templates |
(open) |
| #27 |
Message templates for event types |
(open) |
| #28 |
Require users to set their timezone |
ToDo |
| #29 |
Notification delivery |
ToDo |
| #30 |
Syncing event and session dates |
ToDo |
| #31 |
Dynamic event/session syncing |
Backlog |
| #32 |
Launch button on events |
ToDo |
| #33 |
Calendar invites |
ToDo |
| #19 |
Add content to groups |
ToDo |
| #12 |
Batch assign users to a group |
(open) |
| #9 |
Idea: another benefit to "Business" license |
Backlog |
Task engine
fedms/components/tasks
| # |
Title |
Status |
| #5 |
Implement variations how tasks get marked as completed |
ToDo |
| #8 |
Add more rules to trigger task patterns |
Review |
| #11 |
Task rule when members are removed |
Review |
| #15 |
Task rule when other tasks are completed (successors) |
Doing |
| #20 |
Prevent ambiguous task/webform relationship |
Review |
| #22 |
Groups of content in a task pattern — "one of" selection |
(open) |
| #24 |
Make due dates in tasks dynamic |
ToDo |
| #25 |
Successor tasks for book pages |
ToDo |
| #26 |
Successor tasks for embedded objects |
ToDo |
| #27 |
Add LTR flag to task patterns and tasks |
ToDo |
| #28 |
MTW: Milestone-Task-Widget |
ToDo |
ECA / business logic
fedms/components/eca
| # |
Title |
Status |
| #4 |
Recipe for "Pre workshop" feature |
Backlog |
| #6 |
Provide context-sensitive tokens everywhere |
Review |
| #7 |
Don't use modal dialogue to edit entities |
Backlog |
Content (events, sessions, paragraphs)
fedms/components/content
| # |
Title |
Status |
| #1 |
Potential integration with existing Events platform |
Backlog |
| #5 |
Event Template Organisation |
Backlog |
| #6 |
Event Example Organisation |
Backlog |
| #7 |
Configure/hide footer in book pages |
ToDo |
| #8 |
Hide views filters when no pager available |
ToDo |
Profile / cross-cutting
fedms/components/profile
| # |
Title |
Status |
| #10 |
Configure Roles & Permissions |
ToDo |
| #15 |
Lock product-related views |
Backlog |
| #20 |
Meta: Test Framework |
ToDo |
Testing
fedms/components/tests/playwright
| # |
Title |
Status |
| #1 |
Playwright tests step 1: initial site setup |
Doing |
Support / customer-driven
fedms/support
Selected items:
| # |
Title |
Status |
| #21 |
Worth discussing roles again (Tutor, custom roles) |
Backlog |
| #61 |
Allow session to sync/copy members with the event |
Review |
| #65 |
Can't navigate back to event from session easily |
Review |
| #66 |
Can't reference session default content (file types) |
Review |
| #71 |
Login submit button and un-masquerade buttons missing |
Review |
| #72 |
Slot Pickers |
Backlog |
| #73 |
Allow Manager to add fields to Org Types |
Backlog |
| #74 |
Org Types: add fields from different entities |
Backlog |
| #75 |
[Meta] Orgs structure |
Backlog |
| #76 |
[Meta] Permissions / Compliance / Access |
Backlog |
| #50 |
Conditional fields in events/sessions |
Backlog |
| #15 |
Event and Session templates |
Backlog |
| #9 |
Allow for client-specific language |
Backlog |
Documentation
fedms/documentation
| # |
Title |
Status |
| #1 |
Explain referenced event/session profiles |
Backlog |
How to read this list
- ToDo — scheduled for an upcoming iteration.
- Doing — actively being worked on.
- Review — discussion / design phase; awaiting decision.
- Backlog — recognized but not scheduled.
How to add an issue
- Identify the right project (most often a
fedms/components/*
project, or fedms/support for customer-driven items).
cd into the relevant repo directory.l3d glab issue create.- Use a descriptive title.
- Reference related issues with
Related to fedms/<project>#<id>.
Next steps