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

As a registered user, I want to see who sponsored a user to be a member of a group #626

Open
Conan-Kudo opened this issue May 7, 2021 · 11 comments
Labels
AC/DOD Required This user story needs an Acceptance Criteria (AC) and a Definition of Done (DOD) enhancement New feature or request L Large (~15 hours of work) next phase Needs to be done in the next development phase todo

Comments

@Conan-Kudo
Copy link
Contributor

In the old FAS, it was possible to see who sponsored a user into a group.

Example from FAS:

Screen Shot 2021-05-07 at 3 45 44 PM

In Noggin, there is nowhere this information is presented. This information is important, as it's required for accountability purposes and is necessary information for revoking a packager's privileges. Please add that information to the user profile page for group memberships.

Another nice to have would be to have all this date information to figure out when membership was approved and granted.

@abompard
Copy link
Member

@tiran , do you know if this information is stored (and available) in IPA?

@abompard abompard added enhancement New feature or request needs info Further information is requested labels May 12, 2021
@tiran
Copy link

tiran commented May 12, 2021

The information is not stored in LDAP. The requirement was not part of the initial design.

You might be able to reconstruct the information from HTTPd error log. The error log file contains all IPA API calls (plugin names and arguments). It doesn't work if you have modified users by other means (e.g. LDAP or in-server API calls).

@Conan-Kudo
Copy link
Contributor Author

Oh dear, that's not good.

@abompard abompard added AC/DOD Required This user story needs an Acceptance Criteria (AC) and a Definition of Done (DOD) L Large (~15 hours of work) and removed needs info Further information is requested labels Sep 29, 2021
@mizdebsk
Copy link
Member

mizdebsk commented Oct 5, 2021

I think it's an important feature to have. For example packager sponsors have certain responsibilities regarding their sponsorees, so it's required to be able to track who sponsored whom and when.

@jwflory
Copy link
Member

jwflory commented Jan 13, 2023

+1. It seems like the historical data was lost, if there are no backups from the previous FAS database. If this data could be imported in a new database schema, there would be historical value in this too.

Whether historical data is recovered or not, this is also useful data for measuring team health, engagement, and activity. In the previous FAS system, a user could request to join a group, if it was configured to allow that. I'm not sure if that is possible in the new system. But it was helpful to see the time length between when someone requested membership in a group compared with the time they were approved and sponsored into the group.

If not, even having a record of the year and time that a person was sponsored into a group is helpful context.

@keszybz
Copy link

keszybz commented Sep 28, 2023

I have a copy of the sponsor data from 2018 (with 1973 entries). I can provide it if somebody wants to renter the data somewhere.

@NeilHanlon
Copy link

I have a copy of the sponsor data from 2018 (with 1973 entries). I can provide it if somebody wants to renter the data somewhere.

Not sure where the best place for it is, but great to know some of the data is still around!

@ryanlerch ryanlerch added the next phase Needs to be done in the next development phase label Jan 29, 2024
@ryanlerch ryanlerch moved this to Proposed in Phase Two Jan 29, 2024
Copy link

github-actions bot commented Jun 4, 2024

This issue is stale because it has been open for 60 days with no activity.

@github-actions github-actions bot added the Stale label Jun 4, 2024
Copy link

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
@github-project-automation github-project-automation bot moved this from Proposed to Ready to Deploy in Phase Two Jun 12, 2024
@jwflory
Copy link
Member

jwflory commented Jul 11, 2024

Was this implemented? The issue was closed by automation, but this is still something that would be nice to have. Is it an issue to keep the user story open?

@abompard
Copy link
Member

Agreed, reopening.

@abompard abompard reopened this Jul 11, 2024
@abompard abompard added todo and removed Stale labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AC/DOD Required This user story needs an Acceptance Criteria (AC) and a Definition of Done (DOD) enhancement New feature or request L Large (~15 hours of work) next phase Needs to be done in the next development phase todo
Projects
Status: Ready to Deploy
Development

No branches or pull requests

8 participants