Bug Tracking Integration into Agilo

[Chris]

Hello,

I've been reading posts here about integrating with bug trackers.
Currently our group uses Trac to record bugs. We have internal
customers who them themselves use Trac to report any bugs they find
with the product. I'd like to ask how do you integrate Agilo with bug
tracking? It would make sense to use Trac for customer submitted bugs
(defects) and then have them be rolled into a backlog but that's not
how I'm seeing Agilo works. I have to say just when I thought I struck
gold in making our development process much more defined and
streamlined I'm finding I'm going to need to use 2 separate tools to
manage the process.

Will Agilo ever let you facilitate customer input of bugs and then let
you deal with them as necessary? Point being all this data is already
in a database (Trac DB nonetheless), why waste time to manually enter
the information again as a user story or into a bug backlog/sprint? I
understand Agilo assists with process management but with bugs
(defects) being part of the process I figure there would be some
tighter integration with Trac in that regard. Unless I'm not seeing
the type of integration I'm describing please correct me. And if 2
separate tools (Agilo + bug tracker) are needed could some of you
share your setup/process for dealing with customers identifying and
submitting bugs (defects).

What I read:
Agilo is *not* a bug tracker. It is first and foremost a Scrum project
management tool. It just happens to be based on a bug tracker ;-)

http://groups.google.com/group/agilo/browse_thread/thread/75e195423595f2ba/a45c58f8fcc2682c?lnk=gst&q=bug#a45c58f8fcc2682c

Thanks.
Chris

[Chris]

No one uses bug trackers anymore?

[Karsten W. Rohrbach]

I use a custom ticket type for bugs/support Incidents which get fixed
in a non-Scrum-manner. If a support incident or bug represents a user
story, i just change the ticket type, and voila... The configuration
of available fields is very similar in both ticket types.

[Martin Häcker]

Hi Chris,

> I've been reading posts here about integrating with bug trackers.
> Currently our group uses Trac to record bugs. We have internal
> customers who them themselves use Trac to report any bugs they find
> with the product. I'd like to ask how do you integrate Agilo with bug
> tracking? It would make sense to use Trac for customer submitted bugs
> (defects) and then have them be rolled into a backlog but that's not
> how I'm seeing Agilo works. I have to say just when I thought I struck
> gold in making our development process much more defined and
> streamlined I'm finding I'm going to need to use 2 separate tools to
> manage the process.

You can absolutely use Agilo to trac your bugs the same way you can use
Trac (thats what it really is underneath anyway).

Agilo enhances the concept of Bugs in Trac so they can have nested Tasks
assigned to them if needed (but you can disable this in the admin panel
if you don't need it)

I see no reason why you can't give out accounts to your customers that
can create new bugs that your team can then triage and address either as
planned items in a Sprint (selcomly) or just as part of a contingent to
keep on top of the time it takes to work on bugs (you can read up on
contingents here: <https://dev.agile42.com/agilo-help/user/Contingent>)

> What I read:
> Agilo is *not* a bug tracker. It is first and foremost a Scrum project
> management tool. It just happens to be based on a bug tracker ;-)

That is right - but it also means it retains the full abilities that
trac has in this regard.

The thing is, Agilo is foremost a project management tool, but Trac is
still there underneath and we don't disable it. :)

Regards,
Martin

[Chris]

Thanks Karsten and Martin, I appreciate the advice. I guess then I can
just use permissions on customer accounts so they aren't able to view
any of the project management info, sprints.. backlogs, etc. I'm using
single-sign on, so I can't test what various accounts look and behave
like. Are the Admin, Dashboard, Teams, etc.. navigation buttons
removed from view for those without sufficient privileges?

[Chris]

A follow up. Can you have it so customers only have access to a
certain type of ticket (i.e., customer filed bugs)? Wouldn't want
customers to veer off the path and change ticket types.

[Martin Häcker]

Sure. Each Ticket type has its accompanying Right
"AGILO_[TYPENAME]_CREATE" that you can use to give this account the
rights to create only that type.

Regards,
Martin

[Dennis P. Nikolaenko]

What about the custom ticket types?

--
Dennis

[Martin Häcker]

>> Sure. Each Ticket type has its accompanying Right
>> "AGILO_[TYPENAME]_CREATE" that you can use to give this account the
>> rights to create only that type.
>>
> What about the custom ticket types?

This right should get created automatically for each custom type that
you promote to an agilo type - if not, that would be a bug.

HTH

Regards,
Martin