.. -*- coding: utf-8 -*-

Project cubicweb-forge
======================
:creation date: 2009/01/03

software forge component for the CubicWeb framework

.. vcsinclude:: README

Version 1.13.0
--------------
:publication date: 2016/12/06
:expected date: n/a

Ticket #16359317 schema cleanup
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: in-progress

We may want to follow the cleanup of the tracker cube and remove some (almost)
not used parts of the schema:

* Project recommends Project * ExtProject

Ticket #16359324 buggy rql expression in the follow_up relation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: validation pending

leading to bad sql generated, taking a few seconds to exec.

Version 1.12.0
--------------
:publication date: 2016/01/06
:expected date: n/a

Ticket #9767097 cubicweb 3.22 compat
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: validation pending

modification_date needs a tzinfo

Ticket #4943339 i18n problems with the ticket traceability chain box
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 1.000
:state: validation pending

title nor states are translated

Ticket #9767555 ticket load should be >= load_left
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: validation pending

Ticket #7484462 infinite loop in SetModificationDateAfterAddComment hook
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: validation pending

in the middle of a transaction the root of the comments tree may well be a
Comment, so we never exit the loop.

Version 1.11.0
--------------
:publication date: 2015/02/02
:expected date: n/a

Ticket #4821857 breadcrumbs between card and project does not work
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: validation pending

Currently it's not possible to go back to a project from a card. Breadcrumbs
appears to be implemented but they do not seem to work.

Ticket #4881314 [views] Avoid printing out an empty <div>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 1.000
:state: validation pending

[views] Avoid printing out an empty <div>

Ticket #4881313 [views] Make left_section and right_section handle only their respective section
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 1.000
:state: validation pending

[views] Make left_section and right_section handle only their respective section

The right_section method actully wrote part of the left section. WTF ensues.

Version 1.10.2
--------------
:publication date: 2014/10/29
:expected date: n/a

Ticket #2930535 make tests pass
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: task
:load: 1.000
:state: validation pending

tests want to connect to centaurus:5432. that doesn't work too well.

Ticket #3660339 migration fails if IntervalBoundConstraint is not known
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: validation pending

Some old instances have never had that constraint type added, so they fail when
upgrading to 1.10.1

Ticket #3735909 Remove multisources tests
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

Since they currently fails, and multisources is deprectaed and soon to be
removed.

Ticket #3556754 update Tests
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.300
:state: validation pending

update tests to the new API

Version 1.10.1
--------------
:publication date: 2014/03/14
:expected date: n/a

Ticket #3556861 Fix unittest_notifications
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: validation pending

fix ordering issues

Ticket #3556538 get ride of DeprecationWarning
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: validation pending

Use cw_set method instead of set_attributes/set_relations use assertCountEqual
in tests

Ticket #3341104 load and load_left should be non-negative
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

Currently I can set the load of a ticket to -10. The schema should forbid it.

Ticket #3168584 suppress useless ExtProject require_permission relation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: validation pending

no permission are propagated there.

Version 1.10.0
--------------
:publication date: 2013/07/02
:expected date: n/a

Ticket #2965103 Move done_in rtype permission change on (Ticket, done_in, Version) rdef
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

This permission really belongs to the rdef, as it does in tracker, which
requires thus a simultaneous change in both schemas.

Ticket #2969190 nosy_list RelationDefinition Comment-> CWUser should be defined only if it does not exist yet
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: validation pending

In order the cube to be assembled with others, e.g. forum.

**Warning**: proposed patch for this ticket requires yams 0.38, see
https://www.logilab.org/ticket/149660

Ticket #2967330 Remove JPL favicon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: validation pending

Ticket #2961589 SetModificationDateAfterAddComment hook operates on any entity
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: validation pending

This hook seems to be designed for ``Ticket``, however the selector does not
restrict entity types. E.g. a ``Card`` will also be affected by this hook.

Version 1.9.3
-------------
:publication date: 2013/06/10
:expected date: n/a

Ticket #2897200 key error while sorting project
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

Traceback --------- ::

File /usr/lib/python2.6/dist-packages/cubicweb/web/application.py, line 443,
function core_handle result = controller.publish(rset=rset) File
/usr/lib/python2.6/dist-packages/cubicweb/web/views/basecontrollers.py, line
134, function publish rset=rset, view=view) File
/usr/lib/python2.6/dist-packages/cubicweb/cwvreg.py, line 394, function
main_template res = obj.render(**kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File
/usr/lib/python2.6/dist-packages/cubicweb/web/views/basetemplates.py, line 147,
function call view.render(w=w) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File /usr/share/cubicweb/cubes/forge/views/project.py, line
116, function call reverse=True) File
/usr/lib/python2.6/dist-packages/cubicweb/rset.py, line 214, function
sorted_rset key=lambda (i, e): keyfunc(e), reverse=reverse) File
/usr/lib/python2.6/dist-packages/cubicweb/rset.py, line 214, function <lambda>
key=lambda (i, e): keyfunc(e), reverse=reverse) File
/usr/share/cubicweb/cubes/forge/views/project.py, line 115, function <lambda>
self.cw_rset = self.cw_rset.sorted_rset(lambda e:
e.cw_attr_cache['modification_date'],

Error: &#39;modification_date&#39;

We should access the attribute. not the cache

Version 1.9.2
-------------
:expected date: n/a

Ticket #2896216 do not silently ignore unknown icon image format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

Ticket #2896217 test_possible_actions fail on some platforms
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

due to unpredictible order of self.pactions()

Version 1.9.1
-------------
:expected date: n/a

Ticket #2894841 incomplete migration for project icon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

meta-attributes for project icons are not added.

Version 1.9.0
-------------
:expected date: n/a

Ticket #1262412 Add project logo to Project primary view.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: validation pending

Version 1.8.2
-------------

Brown paper bag release to fix 1.8.1 packaging issue
:publication date: 2013/06/07
:expected date: n/a

Ticket #2921243 1.8.1-1 debian package contains code intended for 1.9
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.250
:state: validation pending

no tag was made for the 1.8.1-1 debian package, and {what,who}ever built it
included changeset 94b39df99bff, which belonged on default.

Version 1.8.1
-------------
:publication date: 2013/05/06
:expected date: n/a

Ticket #2148154 3.14 warning on startup page
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: validation pending

because of usage of deprecated table view

Ticket #2558443 cw 3.14 & further api modernification
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: validation pending

Ticket #2447684 regression: don't see state of non active project
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: validation pending

because since cw 3.15 (3.14?), oneline view doesn't recall the text view

Ticket #2522687 Traceback "VersionDocumentItemView object has no attribute format_date"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: validation pending

Traceback --------- ::

File /usr/lib/python2.6/dist-packages/cubicweb/web/application.py, line 444,
function core_handle result = controller.publish(rset=rset) File
/usr/lib/python2.6/dist-packages/cubicweb/web/views/basecontrollers.py, line
133, function publish rset=rset, view=view) File
/usr/lib/python2.6/dist-packages/cubicweb/cwvreg.py, line 373, function
main_template res = obj.render(**kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File
/usr/lib/python2.6/dist-packages/cubicweb/web/views/basetemplates.py, line 114,
function call view.render() File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File /usr/share/cubicweb/cubes/tracker/views/document.py,
line 137, function call self.cell_call(row=i, col=0) File
/usr/share/cubicweb/cubes/tracker/views/document.py, line 132, function
cell_call self.wview('docitem', self.cw_rset, row=row, col=col) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 282, function wview
self._cw.view(__vid, rset, __fallback_vid, w=self.w, **kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/req.py, line 348, function view return
view.render(w=w, **kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File /usr/lib/python2.6/dist-packages/cubicweb/view.py,
line 390, function cell_call self.entity_call(self.cw_rset.get_entity(row, col),
**kwargs) File /usr/share/cubicweb/cubes/tracker/views/document.py, line 52,
function entity_call self.render_child(entity) File
/usr/share/cubicweb/cubes/tracker/views/document.py, line 80, function
render_child self.wview('docitem', entity.related('version_of', 'object'),
'null') File /usr/lib/python2.6/dist-packages/cubicweb/view.py, line 282,
function wview self._cw.view(__vid, rset, __fallback_vid, w=self.w, **kwargs)
File /usr/lib/python2.6/dist-packages/cubicweb/req.py, line 348, function view
return view.render(w=w, **kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File /usr/lib/python2.6/dist-packages/cubicweb/view.py,
line 387, function call super(EntityView, self).call(**kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 219, function call
self.wview(self.__regid__, rset, row=i, **kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 282, function wview
self._cw.view(__vid, rset, __fallback_vid, w=self.w, **kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/req.py, line 348, function view return
view.render(w=w, **kwargs) File
/usr/lib/python2.6/dist-packages/cubicweb/view.py, line 176, function render
view_func(**context) File /usr/lib/python2.6/dist-packages/cubicweb/view.py,
line 390, function cell_call self.entity_call(self.cw_rset.get_entity(row, col),
**kwargs) File /usr/share/cubicweb/cubes/tracker/views/document.py, line 50,
function entity_call self.render_attributes(entity) File
/usr/share/cubicweb/cubes/forge/views/document.py, line 22, function
render_attributes etadate = self.format_date(etadate)

Error: &#39;VersionDocumentItemView&#39; object has no attribute
&#39;format_date&#39;

:URL:
http://www.logilab.org/view?rql=Any%20Y%2CCOUNT(T)%20GROUPBY%20Y%20ORDERBY%202%20DESC%20WHERE%20X%20eid%205564%2C%20T%20tags%20X%2C%20T%20tags%20Y%2C%20NOT%20Y%20eid%205564&vid=document

:form params: * rql = Any Y,COUNT(T) GROUPBY Y ORDERBY 2 DESC WHERE X eid 5564,
T tags X, T tags Y, NOT Y eid 5564 * vid = error

:CubicWeb version: 3.15.4 :Cube jplorg version: 0.9.0 :Cube jpl version: 0.38.1
:Cube trackervcs version: 0.8.0 :Cube forge version: 1.8.0 :Cube apycot version:
2.2.3 :Cube testcard version: 0.4.1 :Cube vcreview version: 0.10.0 :Cube blog
version: 1.9.6 :Cube card version: 0.3.0 :Cube email version: 1.8.2 :Cube narval
version: 3.2.1 :Cube tracker version: 1.11.1 :Cube vcsfile version: 1.9.2 :Cube
activitystream version: 0.1.2 :Cube comment version: 1.8.2 :Cube file version:
1.11.0 :Cube folder version: 1.8.1 :Cube forgotpwd version: 0.4.0 :Cube
iprogress version: 0.1.1 :Cube jqplot version: 0.2.0 :Cube link version: 1.5.0
:Cube localperms version: 0.1.1 :Cube mailinglist version: 1.7.1 :Cube nosylist
version: 0.5.1 :Cube openidrelay version: 0.2.0 :Cube preview version: 0.2.1
:Cube registration version: 0.4.1 :Cube rememberme version: 0.2.5 :Cube tag
version: 1.7.1 :Cube task version: 1.6.1

Version 1.8.0
-------------
:publication date: 2011/11/09
:expected date: n/a

Ticket #807611 cannot click on tag name in the main table
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: resolved

I want to click directly on tag name visible in the list of tickets. Instead of
raw list view as result, can we use facet/filter system instead ?

Comments ::

  On 2010/03/29 10:42 - mailbot wrote :
  1. there is already a ticket saying "I want to be able to click on the tag
  names" 2. what are you talking about ? simply show the filter form and you can
  filter table entries according to facets.
  > On 2010/03/29 11:08 - Unknown author wrote :
  > 1. I can't find the ticket and the related url !??
  > 2. when I click on a tag name, I would prefer to see the filter form appear
  > automatically with the current selection of my tag
  > 
  > I know I *can* click down_arrow + click facets + click submit button... BUT I
  > want it just in one click whence the story.

Ticket #1872836 Display creation and modification date of a ticket in version view
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: resolved

We have creation and modification date in the project list of ticket, but not in
the version... it would be useful to have it.

Ticket #2072168 update to cw 3.14 / tracker 1.10 api
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

Ticket #1916601 don't get the proper transition form when 'refusing' a ticket
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: validation pending

we should have the one creating a follow-up ticket

Version 1.7.0
-------------
:publication date: 2011/06/21
:expected date: n/a

Ticket #1751398 drop vcsurl / reporturl attributes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

gain them using trackervcs/apycot tracker extensions

Ticket #1216332 [preview] use the preview cube
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.000
:state: rejected

forge seems to be the right place for using preview

Comments ::

  On 2010/08/04 11:56 - sthenault wrote :
  for ticket, probably. IMO card and blog should use the preview cube themselves.
  > On 2010/08/04 12:01 - acampeas wrote :
  > IMO ony big apps, not small cubes, should use preview.

Ticket #1399287 Change the standard validation process of the tickets
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 3.000
:state: resolved

Today, when a ticket is implemented, its state is changed for `validation
pending`. Then, the client checks if everything is all right and can change the
state to `done` or `open`.

The problem is that when a client re-opens a ticket because of something that
doesn't suit him, we have to evaluate again the load of the ticket (adding more
men.days) and we loose information on the previous evaluation. If a ticket is
re-opened several times, it quickly becomes very hard to understand the history
of this ticket.

I suggest to have the following behaviour:

#. the ticket is in state `validation pending`

#. the client change the state to `not validated`

#. a new ticket (bug) is automatically created with a link towards the initial
ticket: follow_up

#. the client enters information in this new ticket on what should be changed

Comments ::

  On 2011/01/07 10:45 - acampeas wrote :
  +1
  
  (May I suggest a "follow_up" rtype ?)
  > On 2011/01/07 12:04 - sthenault wrote :
  > I think I would prefer a new way to estimate ticket's load.
  > On 2011/01/14 10:11 - sthenault wrote :
  > I would rather use 'supersed'
  On 2011/03/08 15:42 - nchauvat wrote :
  Since the second ticket is the continuation of the first ticket and will
  describe an enhancement or a fix, I think it is better to call the relation
  'follow_up' rather than 'supersede', for the latter implies that the second
  ticket replaces-and-cancel the first one.
  > On 2011/06/17 21:28 - nchauvat wrote :
  > read http://dictionary.reference.com/browse/follow%20up and
  > http://dictionary.reference.com/browse/supersede and you will agree that
  > follow_up is the right name. The second ticket does not replace the first one,
  > but it complements it.

Version 1.6.2
-------------
:publication date: 2011/04/07
:expected date: n/a

Ticket #1607803 crash with cw 3.12
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

due to attribute error in schema after the schema expression refactoring in cw

Ticket #1607774 index page crash in some condition
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

Version 1.6.1
-------------
:publication date: 2011/01/13
:expected date: n/a

Ticket #1415241 bad constraint on uses/conflicts
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

Ticket #1415261 misc version views pb
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.300
:state: resolved

* pb with version oneline view (display tarball name when available) * pb with
version download box (display version number instead of tarbal name) * pb with
project's latest version download box (missing box title)

Version 1.6.0
-------------
:publication date: 2010/10/14
:expected date: n/a

Ticket #578046 facet to filter out tickets which have or not some attachment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: resolved

something similar has been done for cmhn

Ticket #979681 filter box : be able to filter on empty fields / lack of relation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: resolved

Example : I'm on a project and I would like to filter tickets on versions to
only display tickets not affected to a version. This is currently not possible
using the filter box.

Comments ::

  On 2010/10/18 07:42 - Unknown author wrote :
  excellent! Thanks a lot.

Ticket #959521 moving a "done" ticket reopens it
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

moved from an open to another open version

msg comes: "déplacé de la version publiée"

Ticket #1259333 Workflow step name is confusing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: resolved

The "resolve" transition (Ticket workflow) is confusing users. May be replaced
by : "ask_validation" --["validate the ticket"]--> "validated ticket"

In french, "résoudre" ne semble pas plus pertinent, avis sur: "valider le
ticket" ou "finaliser le ticket" ?

Version 1.5.2
-------------
:publication date: 2010/09/28
:expected date: n/a

Ticket #1216390 link to previous version has disapeared
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

To reproduce: display a Version on this forge : the link to the previous version
is not displayed at the bottom of the page. The link to the next version is
available (if there is a next version)

Comments ::

  On 2010/08/05 13:44 - Unknown author wrote :
  example: http://www.cubicweb.org/project/cubicweb-forge/1.5.1
  On 2010/08/09 14:41 - Unknown author wrote :
  bug in tracker 1.6.0

Version 1.5.1
-------------
:publication date: 2010/07/12
:expected date: n/a

Ticket #1177714 attribute error on some file/card views
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

due to missing call to adaptation

Version 1.5.0
-------------
:publication date: 2010/07/07
:expected date: n/a

Ticket #1156044 update for cw 3.9 api
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: resolved

Version 1.4.2
-------------
:publication date: 2010/04/26
:expected date: n/a

Ticket #909109 various bug fixes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

Version 1.4.1
-------------
:publication date: 2010/02/26
:expected date: n/a

Ticket #712813 missing transition from done to open in ticket's workflow
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

Ticket #714355 ticket workflow fixes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

* allow client to pass the 'got feedback' transition * the 'wait for feedback'
transition should be available from the in-progress state * we should be able to
go back to open from the done state

Version 1.4.0
-------------
:publication date: 2010/02/10
:expected date: n/a

Ticket #682478 remove 3.6 deprecation warnings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.300
:state: resolved

Ticket #344982 set horizontal scrollbar for too wide verbatim section in ticket description
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: in-progress

as it is done for comments. Maybe this should go into cubicweb.css ?

see ticket #23170 on the extranet for example

this is some very very long text that will show what the problem is in case the
problem is still present in the version of cubicweb that is used to run this
forge you are using at the moment

Comments ::

  On 2009/08/25 16:10 - nchauvat wrote :
  but comments should work better
  
  this is some very very long text that will show what the problem is in case the
  problem is still present in the version of cubicweb that is used to run this
  forge you are using at the moment
  aqaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  > On 2009/08/25 16:57 - mailbot wrote :
  > remove spaces...
  On 2009/09/01 14:59 - ksaurfelt wrote :
  <pre> tag is ment to preserve both spaces and line breaks
  (http://www.w3schools.com/TAGS/tag_pre.asp)
  
  use <blockquote> instead of <pre>
  > On 2009/09/15 17:07 - acampeas wrote :
  > is it done ?

Version 1.3.3
-------------
:publication date: 2010/01/11
:expected date: n/a

Ticket #615820 stop trying to embed vcsurl in the 'browse the source'  tab
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

embedding causes more trouble than good, just link to it.

Version 1.3.1
-------------
:publication date: 2009/12/03
:expected date: n/a

Ticket #475394 change ticket workflow
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: resolved

clients are lost when a ticket is pending validation, but ther version is not
yet published. they think the ticket requires their attention, but there is
nothing to validate yet since the version is still in development.

a solution would be to insert a state "done/fixed" between open and "validation
pending". when a version gets published, all the tickets would move from
"fixed/done" to "validation pending".

Comments ::

  On 2009/10/14 13:18 - nchauvat wrote :
  +1
  On 2009/12/01 09:32 - anon wrote :
  IMO, except some missing transitions, the most important problem is the fancy
  names of the states that trouble users. But there is nowadays some semantic
  research about forge ontology¹ and it can be a first step to reuse their
  terminology (especially the state names) for our generic cube.
  
  ¹ http://www.ifi.uzh.ch/ddis/evoont.html or
  http://code.google.com/p/baetle/wiki/Bugtrackers2baetleMappings
  On 2009/12/01 09:32 - anon wrote :
  IMO, except some missing transitions, the most important problem is the fancy
  names of the states that trouble users. But there is nowadays some semantic
  research about forge ontology¹ and it can be a first step to reuse their
  terminology (especially the state names) for our generic cube.
  
  ¹ http://www.ifi.uzh.ch/ddis/evoont.html or
  http://code.google.com/p/baetle/wiki/Bugtrackers2baetleMappings

Ticket #345077 Download box should always be on top in project view
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: resolved

... and I can't get to configure it in the siteconfig... (at least not on
cubicweb.org

Comments ::

  On 2009/12/01 10:14 - sthenault wrote :
  url ? isn't that ok now ?

Ticket #343729 screenshot box not displayed anymore
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

see http://www.logilab.org/project/hgview

The screenshot box should be shown on the main tab, and when on click on an
image, he should be redirected to this image in the screenshot tab

Comments ::

  On 2009/06/29 19:07 - sthenault wrote :
  seems to be back, but redirect to full screen view instead of tab when clicking
  on the image

Ticket #472797 when creating a ticket appears_in + done_in, we are notified twice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

Comments ::

  On 2009/12/01 10:01 - sthenault wrote :
  reproduced on elo but not in test nor on my test instance. The original pb
  caused by duplicated 'concerns' information in the form params, one in the
  'concerns' field, the other in __linkto.
  
  As I can't reproduce this with more recent version, I change this ticket as
  done, we'll see if the pb actually occurs with upgraded version of cw/tracker.

Ticket #568401 relation 'depends on' not working on edition
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

If you modify a version entity and select ``depends on`` relation box, no combo
box is printed.

Ex: https://www.logilab.net/elo/project/lutin77/0.2?vid=edition

Version 1.3.0
-------------
:publication date: 2009/10/15
:expected date: n/a

Ticket #1704 Expose an RSS feed for releases of a project
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: resolved

For a project, display an RSS that publishes a new item for each version that
goes "published".

Ticket #343722 move TestInstance and related stuff to a separate cube
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

which would become a forge extension

Ticket #344515 See more on frontpage tables
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: resolved

It would be useful to have a "see more" link under the tables on the front page,
for example I can see the last 5 releases, I would want to be able to get the
last 20 releaseas in a list or a table on a new page.

Version 1.2.0
-------------
:publication date: 2009/09/17
:expected date: n/a

Ticket #453782 breadcrumbs incorrect for documentation cards
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: resolved

When displaying a card documenting a project, the breadcrumb at the top enable
clicking on a "documentation" link. This link leads to ::

/project/ProjectName/documentation

and this is mapped to RQL::

Any X WHERE X version_of P, P name "ProjectName", X num "documentation", X is
Version

which will generally give no result.

Ticket #345135 extract nosy_list functionnality into a cube
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

Ticket #376382 url such as project/foo/screenshot not working
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

it used to

Ticket #103898 optimise the project page
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: resolved

According to http://performance.webpagetest.org:8080/ the
http://www.logilab.org/project/pylint page takes 28 seconds to load. That is way
too long. Maybe this also concerns the cubicweb framework.

Version 1.1.2
-------------
:publication date: 2009/09/09
:expected date: n/a

Ticket #344733 burndown chart unvisible with IE7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: validation pending

The burndown chart is not visible with IE7. For example, at
http://www.logilab.org/project/pylint/0.18.1 .

Ticket #370759 ticket changes notification should consider read permissions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.300
:state: resolved

so they don't reveal "secret" information

Version 1.1.1
-------------
:publication date: 2009/08/27
:expected date: n/a

Ticket #344260 move to version is broken
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: rejected

"an error happened" (une erreur est survenue)

Comments ::

  On 2009/06/29 19:08 - sthenault wrote :
  need more info. I use it regularly without any problem.
  On 2009/08/25 18:28 - sthenault wrote :
  we should delete version's specific "move to version"

Ticket #345309 rest export is broken
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.000
:state: resolved

asking for it on a project : ::

can't compare datetime.datetime to datetime.date

Ticket #345343 TypeError: can't compare datetime.datetime to datetime.date
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

on project roadmap: ::

Traceback (most recent call last): File
"/home/auc/src/cubicweb/cubicweb/web/views/basecontrollers.py", line 254, in
publish File "/home/auc/src/cubicweb/cubicweb/web/views/basecontrollers.py",
line 49, in wrapper File
"/home/auc/src/cubicweb/cubicweb/web/views/basecontrollers.py", line 341, in
js_view File "/home/auc/src/cubicweb/cubicweb/web/views/basecontrollers.py",
line 316, in _call_view File "/home/auc/src/cubicweb/cubicweb/view.py", line
149, in render File "/home/auc/src/cubicweb/cubicweb/view.py", line 174, in call
File "/home/auc/src/cubicweb/cubicweb/view.py", line 230, in wview File
"/home/auc/src/cubicweb/cubicweb/appobject.py", line 421, in view File
"/home/auc/src/fcw/cubicweb/cwvreg.py", line 72, in render return
obj.render(**kwargs) File "/home/auc/src/cubicweb/cubicweb/view.py", line 149,
in render File "/home/auc/src/fcw/cubes/tracker/views/project.py", line 97, in
cell_call self.wview('progress_table_view', rset, columns=self.columns) File
"/home/auc/src/cubicweb/cubicweb/view.py", line 230, in wview File
"/home/auc/src/cubicweb/cubicweb/appobject.py", line 421, in view File
"/home/auc/src/fcw/cubicweb/cwvreg.py", line 72, in render return
obj.render(**kwargs) File "/home/auc/src/cubicweb/cubicweb/view.py", line 149,
in render File "/home/auc/src/cubicweb/cubicweb/web/views/iprogress.py", line
56, in call File "/home/auc/src/cubicweb/cubicweb/web/views/iprogress.py", line
68, in cell_call File "/home/auc/src/cubicweb/cubicweb/web/views/iprogress.py",
line 128, in build_eta_date_cell File
"/home/auc/src/fcw/cubes/forge/entities.py", line 184, in eta_date velocity =
self.velocity() File "/home/auc/src/fcw/cubes/forge/entities.py", line 93, in
velocity if stop is None or start is None or start > stop: TypeError: can't
compare datetime.datetime to datetime.date

Ticket #345268 ticket description not displayed by primary view
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

Version 1.1.0
-------------
:publication date: 2009/08/18
:expected date: n/a

Ticket #345022 computed attributes for version progress
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.300
:state: resolved

add progress_target, progress_todo and progress_done attributes on Version and
compute as was done in cube workorder.

Ticket #344574 error in unrelated_rql()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

A strange error appeared in a half-migrated instance (jpl -> forge).

An hotfix was provided by syt but the problem is maybe in a different place.
Just for the record::

--- a/entities/version.py Fri Jul 10 17:26:52 2009 +0200 +++
b/entities/version.py Fri Jul 10 20:34:43 2009 +0200 @@ -55,7 +55,7 @@ class
Version(ProgressMixIn, AnyEntity):

def unrelated_rql(self, rtype, targettype, role, ordermethod=None,
vocabconstraints=True): - if rtype == 'depends_on' and role == 'subject': + if
rtype == 'depends_on' and role == 'subject' and self.has_eid(): return
("DISTINCT Any V2 WITH V2 BEING ((Any V2 WHERE " "V2 version_of P2, V version_of
P, P uses P2, " "V eid %(x)s) UNION (Any V2 WHERE V2 version_of P2, "

P.S. a kvm image is available if need

Ticket #343529 have shorter project url
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: resolved

HTTP redirect myforge.org/p/$1 to myforge.org/project/$1 and maybe do the same
for myforge.org/t/1234 and myforge.org/ticket/1234

Ticket #343841 implement nosy list for Ticket
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 1.500
:state: resolved

We should be able to decide which recipients is appropriate when sending out
notifications. In particular for all events related to the Ticket entity,
creator/owner/modifier/managers, users interested in the project it belongs to,
users who commented the ticket, should be informed of all the changes on a
ticket.

Ticket #344495 notification for new project doesn't include summary
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

Ticket #344818 Quick AJAX edit fails on tickets
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 1.000
:state: rejected

After double clicking on cost and submitting the form. I get to
http://application/list objects are unhashable

Here is what happens server site ::

2009-07-28 15:47:54 - (cubicweb.web) INFO: publish "/json" (form params:
['pageid', 'fname', 'arg']) 2009-07-28 15:47:54 - (cubicweb.web) WARNING: param
subvid mis-formatted 2009-07-28 15:47:54 - (cubicweb.web) WARNING: param rql
mis-formatted 2009-07-28 15:47:54 - (cubicweb.web) ERROR: unexpected error while
validating form Traceback (most recent call last): File
"/usr/lib/python2.5/site-packages/cubicweb/web/views/basecontrollers.py", line
199, in _validate_form ctrl.publish(None) File
"/usr/lib/python2.5/site-packages/cubicweb/web/views/editcontroller.py", line
39, in publish return callback() File
"/usr/lib/python2.5/site-packages/cubicweb/web/views/editcontroller.py", line
153, in _action_apply self._default_publish() File
"/usr/lib/python2.5/site-packages/cubicweb/web/views/editcontroller.py", line
59, in _default_publish eid = self.edit_entity(formparams) File
"/usr/lib/python2.5/site-packages/cubicweb/web/views/editcontroller.py", line
84, in edit_entity entity = self.vreg.etype_class(etype)(self.req, None, None)
File "/var/lib/python-support/python2.5/logilab/common/decorators.py", line 62,
in cache_wrapper3 return _cache[args] TypeError: list objects are unhashable

Comments ::

  On 2009/07/28 17:57 - mailbot wrote :
  url ? this works on my dev instance; but I didn't test using the stable branch.

Ticket #344623 rebase on top of cubicweb-tracker
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.500
:state: resolved

cubicweb-tracker is a trimmed-down fork of forge that should serve as a building
block cubiweb-forge should be based on it (esp. since tracker backports
regularly current forge updates)

Ticket #343352 RSS item author for version should be person in charge of version
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

Right now on an RSS view of latest releases the author of each release is the
person that originially created the version object. It should be the person in
charge of the version.

Comments ::

  On 2009/07/07 21:57 - sribeau wrote :
  I do not even see the author of the release while accessing
  xxx/projectname/vnum?vid=rss.
  Am I looking in the right place?
  > On 2009/07/08 05:30 - mailbot wrote :
  > yup
  > 
  > no dc:creator or like tag ?

Ticket #102079 Stay on ticket after creation form
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: resolved

When I've just created a ticket, I have a habit of tagging the ticket straight
afterwards, so I would prefer if the next screen after validating a ticket would
be the primary view of the ticket itself.

Comments ::

  On 2009/02/11 11:43 - acampeas wrote :
  that belongs to the forge, doesn't it ?
  
  moreover, isn't the current behaviour a change that was requested a little while
  ago -- precisely to have a fast workflow for project -> add ticket -> project ->
  add ticket ... ?
  
  maybe one wants the ability to tag tickets from within the project/ticket list ?
  > On 2009/02/16 18:49 - alutz wrote :
  > user configurable once again ?
  > On 2009/04/30 08:05 - anon wrote :
  > yes, going back to the project to allow for quick add of several tickets was
  > an explicit request.
  On 2009/02/23 09:44 - alutz wrote :
  useful also when you're creating a ticket and you want to send the URL straight
  after that. (In current case, you have to go and look for it).
  > On 2009/06/16 09:14 - alutz wrote :
  > grr, this is really anoying
  On 2009/04/30 06:40 - mailbot wrote :
  What I usually do to work around this is use the "Apply" button instead of the
  "Validate" button. I agree that this feature is more a pain than useful.
  
  Is it possible to add a ticket from the main view of a ticket? If not, we
  should, and then serial submitting of tickets will no longer be a reason fpr
  this behavior.

Ticket #25849 be notified when a ticket gets included in a version
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

scenario is as follows:

* you file a ticket * when that ticket is chosen and included in a version you
get notified - yipee... * when that version starts being implemented your even
happier

Comments ::

  On 2009/02/23 09:46 - alutz wrote :
  this is really important, I've stopped counting the number of times I go back to
  a ticket and it has evolved in the wrong direction (I don't see the comments so
  I don't answer them, some of my tickets get deprecated or rejected... etc.)
  On 2009/02/23 09:47 - alutz wrote :
  Is somebody opposed to this ticket ? If not, which version do we put it in ?
  On 2009/06/22 21:36 - nchauvat wrote :
  what about reusing the concept of nosy_list from roundup and notifying members
  of the changes?
  
  changes would include: ticket is modified, relation done_in is modified, comment
  is added to the discussion.
  
  members of the nosy list would be: the one who created it, the one who modified
  it, the ones who commented it, the ones who are interested in the project the
  ticket is included in.
  > On 2009/06/23 07:02 - mailbot wrote :
  > I'm +1 on nosy list mecanism. Ideally that would go in a separated cube
  > (though I've no design in mind right now).

Ticket #343452 duplicated notification on new tickets
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

Comments ::

  On 2009/07/07 21:26 - sribeau wrote :
  Hasn't it been fixed by Revision: 51:b765ac1e3d22 ?

Ticket #344367 field name too short (>32 characters)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

Rapport de bug concernant la limitation en nombre de caractère d'un nom de
projet: en voulant ajouter un projet "escolan-monitoring-nagios-prelude" (nom de
mon paquet), je me suis confronté à une case "nom" qui ne me laisse saisir
uniquement "escolan-monitoring-nagios-prelud"

Ticket #1524 register to a ticket's activity
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: resolved

We can say we're interested in a project and receive notifications on that
project. It would be good to be able to register on a ticket and get
notifications on :

* state modified * change of priority * new comments * comments on comments *
inclusion in version * modification in version

Being automatically register to a ticket that we just created would be a good
thing as well.

Comments ::

  On 2009/02/17 15:47 - alutz wrote :
  can this ticket be included in a planned version (no versions yet for
  cubicweb-forge) ?

Version 1.0.0
-------------
:publication date: 2009/06/24
:expected date: n/a

Ticket #153796 Burndown chart broken - done points all at zero
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

When a project is published, the red dots all go down to zero, there is no
indication of the time when they where resolve which I think is one of the
aims...

Ticket #153799 initial release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

Release cubicweb-forge for the whole world to see!

Ticket #343430 TicketBurndownView error while accessing Version
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

When a Version is just created and no tickets is related to it, trying to view
an empty Version returns an error:

2009-05-26 11:10:31 - (cubicweb.web) ERROR: NoSelectableObject('args:
(<cubicweb.etwist.request.CubicWebTwistedRequestAdapter object at 0x4715a50>,
<empty resultset for \'Any X,CD,L,LL where X load L, X load_left LL, X
creation_date CD, X done_in V, V eid 21044\'>)\nkwargs: [\'width\', \'w\',
\'height\'] ["<class \'cubes.forge.views.figures.TicketBurndownView\'>"]',)
Traceback (most recent call last): File
"/home/sandrine/src/cubicweb/cubicweb/web/application.py", line 320, in
main_publish result = controller.publish(rset=rset) File
"/home/sandrine/src/cubicweb/cubicweb/web/views/basecontrollers.py", line 110,
in publish return self.vreg.main_template(self.req, template, rset=rset,
view=view) File "/home/sandrine/src/cubicweb/cubicweb/cwvreg.py", line 208, in
main_template res = self.render('views', oid, req, **context) File
"/home/sandrine/src/cubicweb/cubicweb/cwvreg.py", line 201, in render return
selected.render(**context) File "/home/sandrine/src/cubicweb/cubicweb/view.py",
line 148, in render view_func(**context) File
"/home/sandrine/src/cubicweb/cubicweb/web/views/basetemplates.py", line 123, in
call view.render(w=w) File "/home/sandrine/src/cubicweb/cubicweb/view.py", line
148, in render view_func(**context) File
"/home/sandrine/src/cubicweb/cubicweb/view.py", line 173, in call
self.wview(self.id, rset, row=i, **kwargs) File
"/home/sandrine/src/cubicweb/cubicweb/view.py", line 212, in wview
self.view(__vid, rset, __fallback_vid, w=self.w, **kwargs) File
"/home/sandrine/src/cubicweb/cubicweb/appobject.py", line 197, in view return
view.render(**kwargs) File "/home/sandrine/src/cubicweb/cubicweb/view.py", line
148, in render view_func(**context) File
"/home/sandrine/src/cubicweb/cubicweb/web/views/primary.py", line 42, in
cell_call self.render_entity(self.complete_entity(row, col)) File
"/home/sandrine/src/cubicweb/cubicweb/web/views/primary.py", line 82, in
render_entity self.content_navigation_components('navcontentbottom') File
"/home/sandrine/src/cubicweb/cubicweb/web/views/primary.py", line 91, in
content_navigation_components comp.render(w=self.w, row=self.row, view=self)
File "/home/sandrine/src/cubicweb/cubicweb/view.py", line 148, in render
view_func(**context) File
"/home/sandrine/src/cubicweb/cubes/forge/views/sections.py", line 229, in
cell_call self.wview('burndown_chart', tickets_rset, width=800, height=500) File
"/home/sandrine/src/cubicweb/cubicweb/view.py", line 212, in wview
self.view(__vid, rset, __fallback_vid, w=self.w, **kwargs) File
"/home/sandrine/src/cubicweb/cubicweb/appobject.py", line 192, in view view =
self.vreg.select_view(__vid, self.req, rset, **kwargs) File
"/home/sandrine/src/cubicweb/cubicweb/cwvreg.py", line 275, in select_view
return self.select(views, req, rset, **kwargs) File
"/home/sandrine/src/cubicweb/cubicweb/vregistry.py", line 285, in select
[repr(v) for v in vobjects])) NoSelectableObject: args:
(<cubicweb.etwist.request.CubicWebTwistedRequestAdapter object at 0x4715a50>,
<empty resultset for 'Any X,CD,L,LL where X load L, X load_left LL, X
creation_date CD, X done_in V, V eid 21044'>) kwargs: ['width', 'w', 'height']
["<class 'cubes.forge.views.figures.TicketBurndownView'>"]

Comments ::

  On 2009/06/19 06:57 - sthenault wrote :
  sand, you fixed that one right ?
  > On 2009/06/22 16:57 - anon wrote :
  > Yes I did. I go ahead and close this ticket.

Ticket #343816 ugly interested_in box
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

The box which lists the people interrested in a project is ugly. There is too
much space between each line.

Ticket #1422 extract forge component from jpl application
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

extract Project, Version, Ticket, License, File, Image, Card, from jpl and
decide if Tag, Comment, Email, Mailinglist, etc are optional or included in the
base forge or added by derivatives.

Ticket #343740 project in ticket's concerns combo box not sorted by name anymore
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved