Bug in creating ticket references by clicking on the 'Create New' button?

[tcchau]

Seen in R1918.

Steps to reproduce:
1. Create a Requirement ticket.
2. Go into the 'Edit' tab.
3. Click on the "Create a new referenced 'Technical
Requirement'" (in my installation the story type is aliased to
'Technical Requirement').
4. Fill in the ticket and submit.

Behaviour:
1. Child ticket is created, but the reference link from the parent
ticket is not created.
2. Neither is the link the reverse direction.

Expected Behaviour:
Links in both directions to be created for both the original and
child tickets.

Note:
* Creating a link from an existing ticket works, i.e. if I type in
the ticket ID in the Reference # box, and hit 'Create Link'

I am using Python 2.5, Trac 0.11.5

[Martin Häcker]

Hi Clinton,

I tried to reproduce this in the following way:
* Changed the alias for user stories to read "Technical Requirement"
* Created a new requirement
* Switch to edit screen of the requirement
* Click "Create linked 'Technical Requirement'
* Fill something in & hit create

For me everything is linked up correctly.

Could you perhaps verify if this is also happening on a fresh installation?

Also this might be a configuration issue, so if you could provide the
configuration I could take a look at that.

HTH,
Martin

[tcchau]

Hi Martin,

Thanks for checking, and sorry for the delay in getting back to you.

I re-verified that I'm experiencing the same problem as described even
on a fresh install (no modifications or customizations to the Agilo
settings).

Again, my system configuration is Python 2.5, Trac 0.11.5, Agilo
R1918, Genshi 0.5.1.

The Agilo configuration looks like the following:

[agilo-backlogs]
product_backlog.columns = businessvalue:editable, roif,
story_priority:editable, rd_points:editable|total_story_points
product_backlog.name = Product Backlog
sprint_backlog.charts = burndown
sprint_backlog.columns = remaining_time:editable|total_remaining_time,
owner:editable, drp_resources:editable
sprint_backlog.name = Sprint Backlog

[agilo-links]
allow = requirement-story, story-task, bug-task, bug-story
bug.calculate = total_remaining_time=sum:get_outgoing.remaining_time
bug.task.copy = owner, sprint
bug.task.show = owner, remaining_time
cache.related = false
cache.timeout = 0
requirement.calculate = total_story_points=sum:get_outgoing.rd_points|
type=story,mandatory_story_points=sum:get_outgoing.rd_points|
type=story|
story_priority=Mandatory,roif=div:businessvalue;mandatory_story_points
requirement.story.copy = owner
requirement.story.show = rd_points, story_priority
story.calculate =
total_remaining_time=sum:get_outgoing.remaining_time,estimated_remaining_time=mul:rd_points;get_sprint.get_team_metrics.rt_usp_ratio
story.task.copy = owner, sprint
story.task.show = owner, remaining_time

[agilo-types]
bug = owner, sprint, priority
bug.alias = Bug
requirement = reporter, businessvalue, milestone, keywords
requirement.alias = Requirement
story = owner, sprint, rd_points, story_priority, keywords
story.alias = User Story
task = owner, sprint, remaining_time, drp_resources
task.alias = Task

[Martin Häcker]

HI Clinton,

> Thanks for checking, and sorry for the delay in getting back to you.
>
> I re-verified that I'm experiencing the same problem as described even
> on a fresh install (no modifications or customizations to the Agilo
> settings).

This is very strange. We have quite a lot of acceptance tests which
/should/ verify that this works very reliably (and I also can't seem to
be able to reproduce this).

So if it is not Agilo/Trac/Genshi that is to blame, it may be the way
you run these environments. Could you elaborate on that?

I mean, that really was a stock install of agilo, no plugins, no nothing.

If you enable logging on that environment, do you see any error
messages? Could you also make that environment available to me so I can
see if I can reproduce the problem when running that enviornment?

Thanks in advance!

Regards,
Martin

[tcchau]

This is to summarize the resolution for this problem.

Thanks to Martin for his help in eliminating some possible causes of
the problem, I was able to track down the offending party. It turned
out to be some provisions for custom style sheets in the site.html
(which were not actually being used) that caused the problem. This was
snippet in the site.html which caused the problem:

<body py:match="body" py:attrs="select('@*')">
<!--! Add site-specific header -->
<div id="siteheader">
<!--! Place your header content here... -->
</div>

${select('*|text()')}

<!--! Add site-specific footer -->
<div id="sitefooter">
<!--! Place your footer content here... -->
</div>
</body>

Once I removed this (since we're not making use of it anyway, really,
the problems of both the doubled "View__Edit" tabs, and the problem
where links were not being correctly created were resolved.

[Martin Häcker]

Hi Clinton,

> This is to summarize the resolution for this problem.
>
> Thanks to Martin for his help in eliminating some possible causes of
> the problem, I was able to track down the offending party. It turned
> out to be some provisions for custom style sheets in the site.html
> (which were not actually being used) that caused the problem. This was
> snippet in the site.html which caused the problem:
>
> <body py:match="body" py:attrs="select('@*')">
> <!--! Add site-specific header -->
> <div id="siteheader">
> <!--! Place your header content here... -->
> </div>
>
> ${select('*|text()')}
>
> <!--! Add site-specific footer -->
> <div id="sitefooter">
> <!--! Place your footer content here... -->
> </div>
> </body>
>
> Once I removed this (since we're not making use of it anyway, really,
> the problems of both the doubled "View__Edit" tabs, and the problem
> where links were not being correctly created were resolved.

Great to hear that!

I am most intrigued by this, as it sounds as if you where able to
trigger a bug in Genshi that is described here
<http://genshi.edgewall.org/ticket/254>

What is strange here is that to our knowledge that bug only appeared in
genshi with version 0.5.2 - but as far as I know you are using version
0.5.1.

So if that is true - this bug actually has a different cause - and is
much older.

So could you please confirm your genshi version again? (For example by
logging in to agilo as an admin and visit "About Trac" in the upper
right corner and copying the system information table.)

Thanks in advance!

cu Martin