Hi As mentioned above, this had to do with the EmailVerificationModule. I had to de-select it.
We're still getting some weird permission issues fyi As an example, a TEAM_MEMBER can't create a bug? I had to give the AGILO_CREATE_BUG right. Then they could create a bug but not edit it so I had to give the AGILO_EDIT_TICKET right. Now it appears that unless they are actually assigned to a bug by the Sprint admin or product owner (not sure which as I'm acting as both during this evaluation), they can't go in and mark a bug as fixed? I would have though this would all be built in? Or am I missing something in terms of how this should all work? On Aug 19, 7:11 am, velappan velappan <[email protected]> wrote: > Hi bernard, > > Agilo is a stable product i haven't updated to 8.0 yet am using 7.3.0 > it looks fine for us. we are using this tool for last 7 months it has > been a good tool to us not much issues raised for us > > On Aug 17, 8:57 pm, Felix Schwarz <[email protected]> wrote: > > > > > Just to provide some more content if someone searches the archives in > > the future: The culprit is AccountManager's EmailVerificationModule. > > We'll look into updating the docs accordingly. > > > fs > > > smime.p7s > > 4KViewDownload- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
