#6613 Tracker API should include config & milestones & saved bins

v1.0.1
closed
nobody
General
2015-08-20
2013-08-28
Dave Brondsema
No

The bulk export for a tracker includes config and milestones and saved bins. We should expose those through the regular API.

The saved_bins includes extra stuff that should be removed (for both API and export). We don't need related_artifacts, discussion_thread, labels, discussion_thread_url. Those artifact-level fields aren't relevant here.

Related

Tickets: #6613

Discussion

  • Dave Brondsema
    Dave Brondsema
    2013-08-28

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1,3 @@
     The bulk export for a tracker includes config and milestones and saved bins.  We should expose those through the regular API.
    +
    +The saved_bins includes extra stuff that should be removed (for both API and export).  We don't need related_artifacts, discussion_thread, labels, discussion_thread_url.  Those artifact-level fields aren't relevant here.
    
     
  • Dave Brondsema
    Dave Brondsema
    2013-09-03

    • labels: allura-api --> allura-api, 42cc
     
    • status: open --> in-progress
     
  • Created #428: [#6613] Tracker API should include config & milestones & saved bins (2cp)

     

    Related

    Tickets: #6613

    • status: in-progress --> code-review
     
  • Closed #428. je/42cc_6613

    Note that branch contains one failing test, which is not related to this changes (forgediscussion.tests.functional.test_forum.TestForumStats.test_stats_data). It fails on master also. When it will be fixed you should be able to rebase.

     
  • Dave Brondsema
    Dave Brondsema
    2013-09-12

    • status: code-review --> closed
    • QA: Dave Brondsema
     
  • Dave Brondsema
    Dave Brondsema
    2013-09-12

    Made another commit so that TicketMonitoringEmail isn't exposed publicly.

     
  • Dave Brondsema
    Dave Brondsema
    2013-09-12

    • Milestone: forge-backlog --> forge-sep-20