Mercurial > p > roundup > code
view doc/index.txt @ 5132:0142b4fb5a2d
issue2550648 - partial fix for problem in this issue. Ezio Melotti
reported that the expression editor allowed the user to generate an
expression using retired values. To align the expression editor with
the simple dropdown search item, retired values are now removed from
the expression editor.
Do we really want this though? Supposed a keyword is retired and I
want to search for an issue with that retired keyword? Do we have a
best policy document that says to remove retired keywords from all
places it could possibly be used? It could be argued that the simple
search dropdown is wrong and should allow selecting retired values.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Fri, 08 Jul 2016 19:31:02 -0400 |
| parents | 487dc55e3c5e |
| children | 3e1b66c4e1e2 |
line wrap: on
line source
======================================================= Roundup: an Issue-Tracking System for Knowledge Workers ======================================================= For how to contact the community see http://www.roundup-tracker.org . Contents ======== .. toctree:: :maxdepth: 2 features installation upgrading FAQ user_guide customizing admin_guide debugging xmlrpc overview Design (original) <design> developers tracker_templates Notes about the MySQL Database backend <mysql> Notes about the PostgreSQL Database backend <postgresql> glossary acknowledgements Richard Jones implementation notes <implementation> license