Roundup Tracker

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2013-03-10 22:46:14 →
Size: 873
Editor: JohnRouillard
Comment:
← Revision 7 as of 2013-03-10 23:10:11 → ⇥
Size: 2130
Editor: JohnRouillard
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * Create a new version of the batch editor: (see: ProjectManagerBatchEditing and BatchSearchAndEditing)
   That allows you to search to generate the list of issues to
   update, but also provides a checkbox for each issue allowing
   the user to include/exclude each issue as needed.
 * Provide a mechanism to allow reverse links (i.e. links to the
   issue being edited) to be assigned in the web and email
   interfaces. ([[http://sourceforge.net/mailarchive/forum.php?thread_name=201303080359.r283x3GV028359%40mx1.cs.umb.edu&forum_name=roundup-users|see description on roundup-users list]]
 * Modify permissions to make a permission that specifies a matching
   property take precedence over a permission that doesn't specify
   a matching property [[http://sourceforge.net/mailarchive/forum.php?thread_name=20130306080832.GA5009%40runtux.com&forum_name=roundup-devel|See email discussion.]]
 * Rewrite journaling to:
   * Stop it from missing updates to the database (see discussion at roundup tracker RoundupIssue:2550731).
   * Filter properties when user does not have
     permission to see them.
   * Enhance API to search for:
      * changes to a particular property (or properties)
      * changes in a particular time range

Roundup / Python Tracker enhancements

  • Merge Roundup branch / fork from http://hg.python.org/tracker/roundup/ back into mainline.

  • Encapsulate tracker-specific improvements into Roundup extension modules.
  • Improve Rietveld integration.
  • Add stand-alone patch review support to Roundup.

  • Improve REST/json/ajax support. (for REST see: 2550734)

  • Modularize features from tracker templates to improve customizability.

  • Create a new version of the batch editor: (see: ProjectManagerBatchEditing and BatchSearchAndEditing)

    • That allows you to search to generate the list of issues to update, but also provides a checkbox for each issue allowing the user to include/exclude each issue as needed.
  • Provide a mechanism to allow reverse links (i.e. links to the
  • Modify permissions to make a permission that specifies a matching
    • property take precedence over a permission that doesn't specify

      a matching property See email discussion.

  • Rewrite journaling to:

    • Stop it from missing updates to the database (see discussion at roundup tracker 2550731).

    • Filter properties when user does not have
      • permission to see them.
    • Enhance API to search for:
      • changes to a particular property (or properties)
      • changes in a particular time range

(In addition some of these ideas are also captured in Roundup's own tracker)