Show due date of milestone in ticket

[franz.mayer@…]

In ticket view is a link to the assigned milestone. When you want to know what due date has that milestone, you have to click on the milestone link.

It would be nice to have that information already in the ticket view. There might be two ways to achieve this:

1. by tooltip
2. by adding it after milestone name

[Christian Boos]

I think option a) looks better, and it should probably be due date only for opened milestones, and completed date should be shown instead for closed milestones.

That should be added to MilestoneModule._render_link (PatchWelcome).

[Ryan J Ollos]

Should we show No due date when the due date hasn't been set, rather than showing nothing in the tooltip?

Proposed changes can be found in log:rjollos.git:t10962. I added the if hasattr(context, 'req') to support the possibility of a context being passed that is not a web_context, since it wouldn't have a req bound to it. Let me know if this doesn't look right.

The wikisyntax unit tests run with the en_US locale, but the output of format_datetime is 11/24/13 07:41:24 without Babel and Nov 24, 2013 7:41:24 AM with Babel. [b6b2568f/rjollos.git] is implemented so that the test passes with and without Babel, and further adjustments made in [8063c5b0/rjollos.git]. Maybe there is a better way.

[Jun Omae]

I think we should show the tooltips in the same format or some other similar format with localization in milestone view.

Is Completed	Completed %(duration)s ago (%(date)s)
Is late	%(duration)s late (%(date)s)
Due	Due in %(duration)s (%(date)s)
No due date	No date set

[Ryan J Ollos]

Changes suggested in comment:4 have been added in [e1fae589/rjollos.git]. Everything else look okay?

[Jun Omae]

Okay, looks good! But I have one suggestion. Using the existing translation messages would be less work of translators, in [2e48536a/jomae.git]. Even so, it would add new one.

[Ryan J Ollos]

Replying to jomae:

Even so, it would add new one.

I see that is due to the strong tags around the %(duration)s late. Thanks for the hints. I will diff the pot file in the future to detect changes like this.

Committed to 1.0-stable in [12267:12268]. Merged to trunk in [12269].

[Jun Omae]

I found 1 failure due to differences of CLDR between Babel 0.9.x and 1.x.

========== diff: ==========
--- expected
+++ actual
@@ -1,8 +1,8 @@
 <p>
 <a class="missing milestone" href="/milestone/foo" rel="nofollow">milestone:foo</a>
 <a class="milestone" href="/milestone/boo" title="No date set">Milestone Boo</a>
-<a class="closed milestone" href="/milestone/roo" title="Completed 4 weeks ago (Nov 1, 2013 11:59:58 AM)">Milestone Roo</a>
-<a class="milestone" href="/milestone/woo" title="Due in 17 years (Nov 1, 2030 11:59:58 AM)">Milestone Woo</a>
-<a class="milestone" href="/milestone/zoo" title="4 weeks late (Nov 1, 2013 11:59:58 AM)">Milestone Zoo</a>
+<a class="closed milestone" href="/milestone/roo" title="Completed 4 weeks ago (Nov 1, 2013, 11:59:58 AM)">Milestone Roo</a>
+<a class="milestone" href="/milestone/woo" title="Due in 17 years (Nov 1, 2030, 11:59:58 AM)">Milestone Woo</a>
+<a class="milestone" href="/milestone/zoo" title="4 weeks late (Nov 1, 2013, 11:59:58 AM)">Milestone Zoo</a>
 </p>

[Ryan J Ollos]

I suppose I could add another set of expected values for Babel ≥ 1.0. It might be nice if we could use a regex in the unit tests though in order to avoid needing multiple sets of expected values. I imagine support for that could be added to the trac.wiki.tests.formatter:WikiTestCase class.

What do you think would be the best fix?

[Jun Omae]

It would be good to simply use format_datetime with trac.test:locale_en in the same way as use of pretty_timedelta, see [735a29ed4/jomae.git].

[Ryan J Ollos]

That looks good, thanks.

[Ryan J Ollos]

Change from comment:10 committed to 1.0-stable in [12293] and merged to trunk in [12294].