Created new ticket type and backlog, but tickets don't show up
Lorin Hochstein
appear in the backlog.
Here's what I did:
1. Created a new ticket type called "maintenance" (alias
"Maintenance"), with "Resources" and "Keywords" fields enabled.
2. Created a backlog called "Maintenance Backlog". scope: global.
Ticket types: Maintenance. Properties: Description, Keywords, Owner,
Resolution, Resources Status.
3. Clicked on "New Maintenance" and created a maintenance task.
4. Clicked on "Maintenance Backlog", which is empty.
Anything I'm doing wrong here?
Stefano Rago
Actually this is a know limitation (that we are planning to remove)
and you cannot see custom types in the backlog unless they are
task-like (i.e. they have a time_remaining field) or they are linked
to some other type already shown in the backlog:
http://www.agile42.com/cms/pages/faq/#39
Cheers
Stefano
Lorin Hochstein
I modified the new Maintenance type I created by checking off the "Remaining Time" field, but maintenance tickets still don't appear in the Maintenance backlog.
I also tried to create a new type ("Other"), which had the "Remaining Time" field checked, and created an "Other" backlog (global, associated with "Other" tickets), and "Other" tickets did not show up in the "Other" backlog. I even tried to enable every field on the "Other" tickets, and still it didn't show up in the "Other" backlog I had created
Can you confirm that it's possible to create a new ticket type, and a new backlog, and have the new ticket type show up in the new backlog?
Take care,
Lorin
Robert Buchholz
If you want a backlog that just contains "Maintenance" items (and no
stories), you will have to remove the "Remaining Time" attribute from
Maintenance and create a link from Maintenance to Task (or something
else that has Remaining Time). Then you can see the Maintenance items in
the backlog.
Adding Remaining Time to the Maintenance items themselves will only work
if your backlog also displays User Stories because the backlog will
display the Maintenance items under the "Tasks without Stories"
automagical story (which is not displayed if the backlog does not show
stories).
Cheers
--
Robert Buchholz
Software Engineer
Agilo Software GmbH
Gruenberger Str. 54
10245 Berlin, Germany
robert....@agilosoftware.com
http://www.agiloforscrum.com
Follow us on twitter: http://www.twitter.com/agiloforscrum
Amtsgericht Charlottenburg: HRB 127146
CEO Marion Eickmann, Andrea Tomasini
Lorin Hochstein
If this is the case, why was I able to create a "Bug Backlog" that just shows Bug items? Bugs don't have a "Remaining Time" attribute and they aren't necessarily linked to anything else. Are Bugs treated as a special case in the system?
Lorin
Robert Buchholz
On Monday 23 May 2011, Lorin Hochstein wrote:
> If this is the case, why was I able to create a "Bug Backlog" that
> just shows Bug items? Bugs don't have a "Remaining Time" attribute
> and they aren't necessarily linked to anything else. Are Bugs
> treated as a special case in the system?
Bugs can be linked to Tasks. This means a "Link" Bug -> Task exists (on
a ticket type level). It does not mean every bug has to have a task to
appear in the backlog (in fact, you could have a situation where no bug
has a task and still, all show up). Having a direct (or indirect) link
to a task (or some other ticket with remaining time) is just what we use
to determine which ticket types are "top level".
Cheers
Robert
Lorin Hochstein
Robert Buchholz
On Sunday 29 May 2011, Lorin Hochstein wrote:
> How does agilo "know" that Bugs can be linked to Tasks? I checked the
> bug ticket type "Admin -> Types -> "bug", and it wasn't obvious to
> me where this relationship is expressed. I saw that has the
> following fields checked:
>
> * Priority
> * Sprint
>
> It also has the following properties:
>
> total_remaining_time = sum:get_outgoing.remaining_time
>
> If I create a Maintenance type with the same attributes a Bug, and
> create a Maintenance Backlog with the same attributes as the Bug
> Backlog (except associated with Maintenance tasks instead of Bug
> tasks), I still don't get Maintenance tasks appearing in the
> Maintenance backlog. So, I assume that in the Maintenance type I
> created, agilo doesn't know that Maintenances can be linked to
> tasks.
>
> How do I specify that Maintenances can be linked to Tasks?
You can configure the available links in Admin -> Agilo -> Links.
Cheers
Robert
Lorin Hochstein
Thanks for the pointer, I didn't realize that setting was there.
I added the following links for my Maintenance ticket:
* Maintenance -> Task
* Maintenance -> User Story
For Maintenance -> Task, I set the following options:
Copy these fields from source to target: Owner, Sprint
Show these fields in list overview: Remaining time, Owner
For Maintenance -> User Story, I left all options unchecked.
I used these setting so that the Maintenance ticket would have identical properties to the Bug ticket.
Despite adding these links, when I create new Maintenance tickets, they still don't appear in the "Maintenance Backlog" I created, where Bug tickets do appear in the "Bug Backlog", even though
* the "Bug backlog" and "Maintenance backlog" have identical settings other than one being for "Maintenance" tickets and the other being for "Bug" tickets
* the "Bug" and "Maintenance" types have identical settings
* the "Bug" and "Maintenance" link relations have identical settings
Is there something else I need to do to get Maintenance tasks to appear in the Maintenance backlog?
Thanks,
Lorin
Lorin Hochstein
Whoops, scratch that. It worked once I restarted the Apache server.
Lorin
Robert Buchholz
> > Is there something else I need to do to get Maintenance tasks to
> > appear in the Maintenance backlog?
>
> Whoops, scratch that. It worked once I restarted the Apache server.
Are you using 0.9.3 / 1.3.3 Pro or an older version? In that release, we
(thought we) fixed the stale caching of the links configuration.
Cheers
Robert
Lorin Hochstein
Robert Buchholz
> The version string is 1.3.2-PRO. Should I upgrade?
Well, the reloading bug you encountered is fixed, and so are some
others. For minor version increases (1.3.2 -> 1.3.3) there should be
nothing to worry about with staying up to date.
Cheers
Robert
Lorin Hochstein
Stefano Rago
On 08/06/11 04.34, Lorin Hochstein wrote:
>
> Is there any documentation out there that describes how to upgrade an
> existing Agilo installation? I found the installation docs
> <http://www.agile42.com/agilo/how-install-agilo-trac/>, but it didn't
> see any explicit language about upgrading.
You can find upgrade instructions here:
https://dev.agile42.com/wiki/agilo/dev/users/UpgradeGuide
Cheers
--
Stefano Rago
Software Engineer
Agilo Software GmbH
Gruenberger Str. 54
10245 Berlin, Germany
stefan...@agilosoftware.com
http://www.agiloforscrum.com
Follow us on twitter: http://twitter.com/agiloforscrum