chore: initial proposal for user feedback issue templates #196
Conversation
atolopko-czi
changed the title
The UI designs currently have one "provide feedback" button on each task's page. I'm guessing that the package feedback template would only be used through github?
|
|
|
||
| **Dataset name**: [e.g. tsv2_blood, adamson_perturb, etc.] | ||
|
|
||
| **Task name**: [e.g., clustering, embedding, label_prediction, etc.] |
There was a problem hiding this comment.
We can fill this in for them since it's coming from a specific task's page
There was a problem hiding this comment.
(still leave it here, just a call out)
There was a problem hiding this comment.
Rethinking this issue type: It makes sense for now since the benchmarking assets (datasets, models) are currently part of the repo, but once we move these out of the repo's purview, this issue type form will no longer be appropriate. As discussed in Slack, Airtable might be better for capturing benchmark result feedback longer term.
|
@atolopko-czi and @ehoops-cz wanted to give you a heads-up that Katrina from the Salesforce team was added to this PR. Could you kindly remove her? I appreciate you! cc: @KatrinaCZI |
atolopko-czi
requested review from
katrinakalantar
and removed request for
KatrinaCZI
woops, wrong Katrina, corrected! |
For https://czi.atlassian.net/browse/VC-2619
@erin.hoops brought up that we intend to capture VCP feedback for benchmarks via a UI link that navigates to a Github issue form. To get a jumpstart on what information we might want to collect from users, I put together two issue templates.
Add user feedback issue templates, for use by VCP FE. Split into two templates, one for benchmarking results, another for cz-benchmark package (code) feedback.
This is just a draft to get started on ideation for what we actually want in the template(s)! (ChatGPT generated)