You cannot post messages because only members can post, and you are not currently a member.
|
 Welcome to Agilo for Scrum User Group!
|
| |
A warm welcome to all the subscribers of the group :-) The group is ruled by membership and new members post will be held back for moderation, to avoid bots posting ads, and someone spamming via email address... welcome to the internet :-) We will try to solve and discuss everything related to Agilo for... more »
|
|
|
Sprint retrospective
|
| |
I think it could be useful to have a place where the team can record what team members say and decide during a retrospective. It also may be useful to record this, in order to complain to ISO9xxx: for example our QA department ask us to have a periodic design review, so we answer that we have a retrospective after each ieration and they say "OK, but write down a... more »
|
|
|
Great report for looking at Team Member Load
|
| |
We started using Agilo a few months ago and have just started our 3rd sprint. It is working well for us. The one thing that we wanted was to have a better look at how team members were doing with their commitments during the sprint. Our dev lead created a report sql query that the team now relies on. I... more »
|
|
|
New Release of Agilo for Trac 0.9.8 / 1.3.8 Pro
|
| |
New Release of Agilo for Trac (formerly Agilo for Scrum)
Today we're releasing a new version of Agilo for Trac Pro 1.3.8 (and the Agilo for Trac Open Source edition, 0.9.8). This release contains only the following changes:
Manage 'task' tickets via xml-rpc. Both read and write operations are now supported (including changing ticket status, attachments...), but currently the xml-rpc support is limited to tickets of type 'task'. Extended support like different ticket types and hierarchical information is planned for next versions. For this feature to work the Trac XML-RPC plugin ([link]) has to be installed... more »
|
|
|
TrackQuery
|
| |
Dear community,
Trying to build up list of tickets, e.g. bugs ordered in the way they
appear in backlog (that has this drag-n-drop ability).
Using something like this within wiki page to show:
[[TicketQuery(status=accepted| assigned|new|reopened|
accepted,priority=blocker|crit ical,order=???????,type=bug,co l=id|... more »
|
|
|
Cannot edit ticket properties
|
| |
When I click to edit any given ticket, the ticket properties are hidden on the page. The culprit is the following CSS in agilo_theme.css, located under "Trac Fixes." .collapsed > div, .collapsed > table, .collapsed > ul, .collapsed > dl { display: none; ...I do not want to simply delete that line without understanding why this started happening. I can't say for sure, but I believe it started after the latest update.... more »
|
|
|
Changing Alias of Requirement prevents creation of new requirements
|
| |
In our setup, we changed the alias of "Requirement" to "Project", but otherwise didn't change the ticket type. Once we changed this alias, we were no longer able to create new Project tickets, we would get this error: *Warning:* No permission to create or edit a project. I tracked this error message down to this method in agilo/ticket/web_ui.py... more »
|
|
|
usage with Apache
|
| |
I'm running Apache 2.2.22 with mod_python 3.3.1 on Fedora 16.
When configuring Agilo for Trac and using tracd as the web server,
projects display properly.
When trying to use Apache though the projects only display Trac not
the Agilo plugin.
Here is my Apache configuration:
<VirtualHost *:80>... more »
|
|
|
Mercurial Ticket Update Hooks
|
| |
I'm having some trouble figuring out how to migrate our current working trac/hg process into the agilo workflow. I have the latest version of Agilo, Trac, TracMercurial, Mercurial, Python 2.6, etc. Before enabling Agilo, tickets were updated properly by commit messages when users pushed to the repository on the web server (configuration came... more »
|
|
|
This Group is meant to help users of Agilo for Trac to exchange tips & tricks and help each other to solve common problems. Please support us by reviewing and voting on: