Skip to content
  • Past due by over 2018 years Last updated 1 day ago
     
  • Due by August 31, 2019 Last updated about 18 hours ago
     
  • Due by September 30, 2019 Last updated about 11 hours ago
     
  • Due by October 31, 2019 Last updated about 17 hours ago
     
  • Due by November 30, 2019 Last updated about 1 month ago
     
  • Due by December 31, 2019 Last updated about 15 hours ago
     
  • Due by December 31, 2019 Last updated 10 days ago

    Add-to-App issues that will land in December. Broken out of the December 2019 milestone to support burndowns with ZenHub.

     
  • Due by January 31, 2020 Last updated 11 days ago
     
  • Due by February 29, 2020 Last updated about 2 months ago
     
  • Due by March 31, 2020 Last updated about 2 months ago
     
  • Due by April 30, 2020 Last updated 17 days ago
     
  • Due by May 31, 2020 Last updated about 2 months ago
     
  • Due by June 30, 2020 Last updated about 2 months ago
     
  • Due by January 01, 2029 Last updated 3 days ago

    P1: This milestone applies to bugs labeled "customer blocker" or "c…

    P1: This milestone applies to bugs labeled "customer blocker" or "customer critical" and indicates that the bug has been acknowledged and will be worked on post haste, but that the precise details of who or when the issue will be resolved are still being determined. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately.

     
    63% complete
  • Due by January 01, 2030 Last updated about 18 hours ago

    P1: This milestone indicates that the bug has been determined by th…

    P1: This milestone indicates that the bug has been determined by the engineers who would work on it that they should work on it sooner rather than later, but they have not yet determined the schedule for working on it, or exactly who should work on it. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately. Bugs should not be added to this milestone except by the engineers of the team who are working on the area that the issue covers.

     
  • Due by January 01, 2031 Last updated about 10 hours ago

    P2: These are tasks we think are worth fixing in the coming years. …

    P2: These are tasks we think are worth fixing in the coming years. It includes issues we've identified that might block fully shipping broad consumer-facing apps, correctness issues, and bugs relating to polish and quality. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately.

  • Due by January 01, 2032 Last updated 1 day ago

    P3: This milestone is for features and bugs that we feel we could e…

    P3: This milestone is for features and bugs that we feel we could easily defer until after those in the "Goals" milestone. We are unlikely to work on these issues in the near future. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately.

  • Due by January 01, 2033 Last updated 1 day ago

    P4: These are for features we are interested in but explicitly punt…

    P4: These are for features we are interested in but explicitly punting for the foreseeable future. Typically this is for features that go beyond the scope of our initial goal of having a solid UI framework for making applications for Android and iOS phones and tablets. We are extremely unlikely to work on issues in this milestone. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately.

     
  • Due by January 01, 2034 Last updated 3 days ago

    WONTFIX: This milestone applies to bugs labeled "customer blocker" …

    WONTFIX: This milestone applies to bugs labeled "customer blocker" or "customer critical" and indicates that the bug has been acknowledged but that there is currently no plan to work on the issue in the near future. Please reach out to us as soon as possible if an issue is marked in this way but is blocking you. Bugs in this milestone are likely to get closed. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately.

     
    88% complete
  • Due by January 01, 2035 Last updated 4 days ago

    This milestone contains metaissues, technical debt issues, team inf…

    This milestone contains metaissues, technical debt issues, team infrastructure, and other topics that have been triaged but don't need a priority level or milestone. Customer requests shouldn't end up in this milestone. The date on this milestone is utterly arbitrary and just intended to sort the milestone appropriately.

     
You can’t perform that action at this time.