Possible bug with group assignments


(Lambda Lambda Lambda) #1

Hi folks,
when I create a group assignment selecting a set of existing teams, I distribute to the students the link that GitHub Classroom generates automatically.
When the students open the link they land on a page that asks them to accept the assignment but immediately after they are prompted to create a new team in order to undertake the assignment.

This behaviour of the application is not what I was expecting: since the students already blenog to teams, they should be asked to EITHER create a new team OR choose one of the teams they already belong to.

Actually since the instructor selects a set of existing teams for the group assignment I would even expect that the students are not prompted for any choice: if a student X accepts the assignment and he/she belongs to one of the teams selected by the instructor, say team Y, the system should create the new repo and assign it to team Y giving access to student X and its teammates.

Anyone else experiencing this strange behaviour? Is it a recognised bug or an intended pattern of use?

Thanks


(Vanessa) #2

Hello @acarraro:

When the students open the link they land on a page that asks them to accept the assignment but immediately after they are prompted to create a new team in order to undertake the assignment.

This sounds like it may be a bug. Mind opening an issue with the steps we can take to reproduce it? Screenshots welcome–we appreciate all the evidence you can pass along.


(Mears Ufl) #3

We have the same problem with team assignments where starter code is included from an existing repo, and students solved the problem by adding an additional number to their team name.
This is clearly a bug since the number of repos will be (number.of.assignments) X (number.of.teams +1). The plus1 is for the original number of repos of assignment starter code.


(Vanessa) #4

I also tried testing to find a workaround–sometimes increasing the limit of # in a team helped too