Bug #38881

CLA flag missing for groups, break group membership on projects

Added by Karsten Dambekalns over 9 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-07-11
Due date:
2013-03-15
% Done:

0%

Estimated time:

Description

When a group is assigned to a project, the settings screen of said project can no longer be used. This is because the list of members shows the CLA status for members, but that field is missing on the groups (https://gist.github.com/3091211).

My guess is that https://gist.github.com/3091098 would solve the issue.

Because groups would enable way easier membership management for the Phoenix and FLOW3 distribution projects, we'd be very grateful if this was solved!


Related issues

Related to forge.typo3.org - Feature #514: Add a property for projects: "Requires signed CLA"ClosedMichael Stucki2008-05-102012-09-28

Actions
Related to forge.typo3.org - Feature #45173: use upstream REST Api intstead of custom service pluginClosedPeter Niederlag2013-02-05

Actions
#1

Updated by Karsten Dambekalns about 9 years ago

Ping… anyone who can tackle this?

#2

Updated by Steffen Gebert over 8 years ago

  • Assignee set to Peter Niederlag
#3

Updated by Peter Niederlag over 8 years ago

  • Due date set to 2013-03-15
  1. This bug/feature needs to be tackled within redmine
  2. Also the sync-scripts towards gerrit/git need to be adapted to take this change into account
#4

Updated by Peter Niederlag over 6 years ago

  • Status changed from New to Needs Feedback

Is this still an issue for anyone?

Thx,
Peter

#5

Updated by Karsten Dambekalns over 6 years ago

As said, our usecase will soon be non-existent, but I guess for anyone using Forge this still might be useful. But feel free to ignore, as discussed yesterday.

#6

Updated by Peter Niederlag over 6 years ago

  • Status changed from Needs Feedback to Accepted
  • Assignee deleted (Peter Niederlag)
  • Priority changed from Must have to Could have

Thx for getting back on this and adding the result of our nice latenight conversion on this ticket.

I'll just set the priority to "could have" and remove myself as being responsible (prefer pull over push for assignments anyway).

#7

Updated by Steffen Gebert over 4 years ago

  • Status changed from Accepted to Rejected

no CLA anymore

#8

Updated by Steffen Gebert over 4 years ago

  • Status changed from Rejected to Closed

Also available in: Atom PDF