Bugs/Errors found during testing #407
Comments
@anikalindtner this -> 8ab7e5e should at least make the flash messages (the "pretty" error or info boxes) more bearable by adding a small button that can be used to dismiss the message. |
Nice to have: images here: https://github.com/rails-girls-summer-of-code/organization/issues/129#issuecomment-196045760 |
The skill level does get saved, it just doesn't pre-select the radio buttons. At least I can reproduce this problem locally now (which wasn't the case last year when we got all the bug reports). I'm still at a loss why that is so. |
This, too, is subject to #380 |
This is quite a task and also quite brittle in respect to future changes. I wouldn't want to assign resources to it right now. |
I think I need a more concrete example for that |
I don't think we can add this. For example the 2nd tab is not really a "next" tab since a student cannot edit the fields of their pair. |
@carpodaster: if you click on "edit" you can see people added to your team that you didn't add. Like: I know that this looks a bit different for me, since I'm also an organizer, but my pair (who's a friend of mine and not an organizer) could also see this. |
@anikalindtner skill level issue: What I meant is that the underlying database record gets saved. The form just doesn't pre-select the value present in de DB |
@anikalindtner Can you give me the ID of the team in question please? Or its direct URL? |
@carpodaster @anikalindtner it's weird, because for me, locally, it works. technology, how does it even. |
@anikalindtner I just double-checked the info regarding your team in staging, and it seems like your team wasn't created yesterday, but it was created last year. So, I'm guessing that's why you have those roles in there — they were added last year to your team, and when you logged into the app you didn't create a new team but just added a student to your currently existing team. Could that be it? |
@alicetragedy ah yes! exactly! Hat tip ms sherlock <3 |
We are live! |
so are the bugs! they've been released into the wild 🎉 |
I'd love to keep track of this. and if someone has a minute they can fix some of the bugs listed here. |
@anikalindtner The must haves are fixed. I've commented on some of the others and among them are a few For text corrections: suggestions for better wording are most welcome. If there are items left in this list, please add them as new issues. It's a lot easier to keep track of an atomic issue than aggregate ones like this. This said: we are currently a bit swarmed with issues and I'd rather have issues closed that are of no immediate concern than having our issue / feature request list grow over 5+ pages. |
will take another look at the text-based fixes and adding the link to the team in the navigation, but I think that's all we will be able to deal with this year (ie. no progress bar, no pagination because it doesn't make sense from a UX point of view). |
awesome, laura thank you. feel free to close this then again after today. |
Note: "state that all fields are obligatory" is not required anymore because a) not all fields are obligatory and b) we have finally fixed all of the error fields, so everything is showing properly now. |
MUST FIX
add buttons "next" and "back" to bottom of page, so indicate that you have to go through the next tabs in order to go through applicationcan't change roles from e.g. student to coach: If I try to edit that team, changing anasofiapinho from student to coach or from coach to student, the mouse doesn't let me select.TEXT (assigned to maria)
obligatory fields: state that all fields are obligatoryUI: ERROR MESSAGE: (#408)
ON THE FENCE
add pagination (e.g. 2/4) to bottom of page to show which tab you are onTEXT
NICE TO HAVE
show progress (3/10) (make tabs green/ red for errors)TEXT
The text was updated successfully, but these errors were encountered: