New to agilo...
Kent
We have been evaulating agilo in a pilot project now and while I like
it in general, I have a few questions/issues:
1, To activate login using forms instead of http authentication is
VERY annoying...
I managed to do it once on a project and since then never managed
to repeat it, it is more than confusing and I tried instructions from
several different threads etc... but to no avail...
2, IS the ordering of sprint backlog really buggy? or is it my
missunderstanding?
AFAIK, it should (according to common sense) order by default so
that stories ends up grouped under the requirement they belong to and
tasks under respective story, or?
Even though we manually adjust this, sometimes agilo un-does
this?!?
Felix Schwarz
> Hi!
> 1, To activate login using forms instead of http authentication is
> VERY annoying...
> I managed to do it once on a project and since then never managed
> to repeat it, it is more than confusing and I tried instructions from
> several different threads etc... but to no avail...
If you tell us what kind of authentication you would like to have and
what problems you experience, we can help you with that...
> 2, IS the ordering of sprint backlog really buggy? or is it my
> missunderstanding?
> AFAIK, it should (according to common sense) order by default so
> that stories ends up grouped under the requirement they belong to and
> tasks under respective story, or?
In the old backlog, every line is stored on its own so it may happen
that tasks don't appear below their story until you fix this manually or
press 'default sorting'. You might want to evaluate the new beta backlog
which is a significant improvement over the old state when it comes to
ordering + drag&drop.
fs
Kent
> Am 15.12.2009 15:50, schrieb Kent:
>
> > Hi!
> > 1, To activate login using forms instead of http authentication is
> > VERY annoying...
> > I managed to do it once on a project and since then never managed
> > to repeat it, it is more than confusing and I tried instructions from
> > several different threads etc... but to no avail...
>
> If you tell us what kind of authentication you would like to have and
> what problems you experience, we can help you with that...
In the project that I DID get to work with forms-based login, the
settings looked like this:
[account-manager]
authentication_url =
force_passwd_change = true
hash_method = HtDigestHashMethod
htdigest_realm =
password_file = /var/lib/trac/users.passwd
password_store = HtPasswdStore
And:
[components]
acct_mgr.* = enabled
acct_mgr.web_ui.emailverificationmodule = disabled
acct_mgr.web_ui.registrationmodule = disabled
agilo.* = enabled
agilo_common.* = enabled
agilo_pro.* = disabled
trac.ticket.api.ticketsystem = disabled
trac.ticket.roadmap.roadmapmodule = disabled
trac.ticket.web_ui.ticketmodule = disabled
trac.web.auth.loginmodule = disabled
(ie the authentication is through passdw file)
I even tried to copy these two sections to the trac.ini in newly
created projects, but they STILL fall back to http authentication
login popping up... (which is very annoying, why is this default?
almost no web apps uses http authentication nowadays...? )
>
> > 2, IS the ordering of sprint backlog really buggy? or is it my
> > missunderstanding?
> > AFAIK, it should (according to common sense) order by default so
> > that stories ends up grouped under the requirement they belong to and
> > tasks under respective story, or?
>
> In the old backlog, every line is stored on its own so it may happen
> that tasks don't appear below their story until you fix this manually or
> press 'default sorting'. You might want to evaluate the new beta backlog
> which is a significant improvement over the old state when it comes to
> ordering + drag&drop.
Ok, sounds interesting... I installed my agilo with the vmware image
so I am a rookie in install too, is it easy to upgrade this image to
the latest beta?
I guess I might have to learn to install it properly from scratch
soon... ;-)
>
> fs
>
> smime.p7s
> 4KVisaHämta
Felix Schwarz
Am 21.12.2009 11:44, schrieb Kent:
> In the project that I DID get to work with forms-based login, the
> settings looked like this:
(...)
> I even tried to copy these two sections to the trac.ini in newly
> created projects, but they STILL fall back to http authentication
> login popping up... (which is very annoying, why is this default?
> almost no web apps uses http authentication nowadays...? )
This sounds very strange. I suspect there is some issue with an external
software, e.g. Apache and a specific configuration in that vhost (also
check Apache's global configuration).
The only way that this behavior could happen in plain
trac+AccountManager (without external software) is that you use a login
url different from '<your agilo>/login' or you are already authenticated
somehow for the same host and trac authenticated you before...
How did you start Agilo? mod_python, mod_wsgi, tracd? If tracd, which
comamnd line parameters do you pass?
fs