1072428 - remove requirement for description in Input API

Status: RESOLVED WONTFIX

(Input Graveyard :: Backend, defect)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

The Input API for posting feedback requires a description. This is good in a lot of cases, but there are some cases where this is undesirable and leads to crap results.

For example, in order to get around the restriction Loop pre-fills the description with localized strings which make it difficult to suss out unique issues in the resulting data (there are like 200+ "unique strings").

This involves:

1. fixing the api code
2. writing up a test
3. updating the documentation

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Tossing this in the 2015q1 queue.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

There are pretty stiff ramifications to this. I think for now we should push it off and try not to do this.

Having said that, Loop sends the same description often and might be hitting ratelimiting pretty often. I created bug #1120988 for that.

In the meantime, I'm bumping this out of this quarter.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

At one point, we thought about expanding what "feedback" means and what we're collecting. Instead of expanding it, though, we're going to continue use Input feedback as sentiment data and derive sentiment from descriptions. That requires a description.

Further, the primary use case for this bug is gone.

Given those, I'm going to mark this as WONTFIX. If we hit another compelling use case we can rethink things then.