OpenConext / OpenConext/OpenConext-Invite

How to keep invite accessible at scale?

Open
#726 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs refinement
Dominant language
Java
Stars
6
Forks
7
Avg merge
12h 24m
Merged PRs (30d)
11

Description

New Feature Request

Summary

Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
How to keep overview of roles and users at high usage numbers? Currently overview might become limited.
Consider each perspective -> user, inviter, role manager, institution admin.

Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")
To ensure long term usability of Invite.

Proposed Solution

  • Action: Describe the logic or flow change.
  • Design: [Link to Figma/Screenshots]
  • Impact: Does this affect existing APIs or UI components?

Developer Checklist

To be completed by the developer during implementation.

  • Add required changes and feature flags config files
  • Create and document database changes and migrations
  • Create and document API changes and migrations
  • check for backwards compatibility
  • Updated CHANGELOG and other documentation where needed

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup
  1. Point to [URL/Branch]
  2. Use account with [Role/Permissions]
Test Checklist
  • Happy Path: Feature works as intended under normal conditions.
  • Edge Case: [Describe specific test item]
  • Validation: [Describe specific test item]
  • UI/UX: Verified layout across screen sizes.

Extra Information

Add any other context, related issues, or technical notes here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points to inspect. First clarify the intended user, inviter, role manager, and institution admin workflows, along with the affected UI or API and scaling requirements; completion criteria and verification steps are not defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.