days in IETF state has a calculation bug

[ietf-svn-bot]

keyword_sprint owner:shane@time-travellers.org resolution_worksforme type_defect | by resnick@episteme.net

---

See
https://datatracker.ietf.org/doc/draft-ietf-precis-framework/,
next to IETF state. Note also the text in the tooltip if you mouse over it.

See also the associated row at
https://datatracker.ietf.org/doc/ad/pete.resnick/

---

Issue migrated from trac:1312 at 2022-03-04 03:36:55 +0000

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

For the first point - these badges are milestones, and it's not obvious what they are. For an extreme example, look at
http://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/

The second point (the ad page display) uncovers a serious bug.
The new code that allows chairs to request publication through the tracker is not creating one of the DocEvents that it should.

>>> d.docevent_set.filter(type='changed_state',statedocevent__state_type='draft-iesg')
[]

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

From fd0602a:

Merged ff48d32 from rjsparks@nostrum.com: Migration to repair missing StateDocEvents from wg chairs using
the datatracker to request publication of ietf stream documents.
Incremental improvement to the request publication view to create
those StateDocEvents going forward.
This is related to bug #1312

[ietf-svn-bot]

@shane@time-travellers.org changed status from new to assigned

[ietf-svn-bot]

@shane@time-travellers.org changed owner from `` to shane@time-travellers.org

[ietf-svn-bot]

@shane@time-travellers.org commented

---

You can see an example of the calculation around the date here:

https://datatracker.ietf.org/doc/ad/pete.resnick/

This currently reads:

Approved-announcement to be sent::Point Raised - writeup needed (for 86 days)\\
Submitted to IESG for Publication Nov 2010

There are two issues here, probably unrelated.

1. One issue is that this calculation is apparently made from the first time a document was moved into the given state, and this does not tell you how long it has been in the given state in total or since the last change. Probably all 3 of these values are useful (although really the since the last change version is probably the most helpful to know how long progress has been halted).
2. Another issue is the "Nov 2010" which is actually related to the working group milestone. As far as I can tell, this data is probably in a database but not exposed anywhere (at least in this case). I'm not sure if this is actually helpful data - maybe it requires a separate ticket?

[ietf-svn-bot]

@shane@time-travellers.org changed status from assigned to closed

[ietf-svn-bot]

@shane@time-travellers.org changed resolution from `` to worksforme

[ietf-svn-bot]

@shane@time-travellers.org commented

---

Replying to ietf-svn-conversion/datatracker#1312 (comment:4):

You can see an example of the calculation around the date here:

https://datatracker.ietf.org/doc/ad/pete.resnick/

This currently reads:

Approved-announcement to be sent::Point Raised - writeup needed (for 86 days)\\
Submitted to IESG for Publication Nov 2010

This turns out to be correct, based on the time since this point was raised.

There are still 3 dates displayed for the document, which may be slightly confusing:

1. The time of the last change to the document itself (new draft in this case).
2. The time since the document entered the current state (the "86 days" in this case).
3. The date on the working group milestone ("Nov 2010" in this case).

But all of these are actually correct, so we'll resolve this ticket.