Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add user research evidence section to issue feature request template #3210

Merged
merged 1 commit into from
Apr 10, 2018

Conversation

redshiftzero
Copy link
Contributor

Status

Ready for review

Description of Changes

Changes proposed in this pull request:

  • This is a followup from the UX meeting on Monday where we discussed adding a section in the issue template to point to relevant SecureDrop user research to better motivate feature requests.

Testing

Let me know if the wording could be improved here @ei8fdb @belenbarrospena and I can modify it

Deployment

N/a

@redshiftzero redshiftzero requested a review from a user March 31, 2018 00:48
@codecov-io
Copy link

codecov-io commented Mar 31, 2018

Codecov Report

Merging #3210 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #3210   +/-   ##
========================================
  Coverage    85.91%   85.91%           
========================================
  Files           34       34           
  Lines         2137     2137           
  Branches       235      235           
========================================
  Hits          1836     1836           
  Misses         247      247           
  Partials        54       54

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 46e0b55...3c45373. Read the comment docs.

@ghost
Copy link

ghost commented Mar 31, 2018

As a contributor, I would be intrigued by this user research question. What am I expected to provide? Why does it matter? Can I get help doing that? Is this going to require days of my time? Are there examples I could look into (https://lab.securedrop.club/main/ux/wikis/ux-design-decisions/tails-ws-gui-updater for instance)?

I took a look at http://opensourcedesign.net/resources/ and maybe there is something suitable there but I did not find it.

Ideas?

@belenbarrospena
Copy link

I agree some background information would be good, but I wonder if the issue template is the right place for it.

What about creating a page in the UX wiki about what the user research template section actually means and how to complete it? Then we could link to the page from the template.

@ghost
Copy link

ghost commented Apr 3, 2018

What about creating a page in the UX wiki about what the user research template section actually means and how to complete it?

Sounds like the best thing to do, indeed!

@belenbarrospena
Copy link

Here is a first stab at it

https://lab.securedrop.club/main/ux/wikis/User-research-evidence-in-feature-requests

@redshiftzero
Copy link
Contributor Author

This document looks excellent @belenbarrospena! I'll link out to this page in the template

Adding link to the excellent UX wiki page about issue feature requests
written by @belenbarrospena.
@redshiftzero redshiftzero force-pushed the docs-add-user-evidence branch from 1875f69 to 3c45373 Compare April 5, 2018 19:22
@redshiftzero
Copy link
Contributor Author

I think this should be ready to go - any other comments?

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

User Research is the new black 💯

@redshiftzero
Copy link
Contributor Author

🖤

@redshiftzero redshiftzero merged commit bf4307b into develop Apr 10, 2018
@redshiftzero redshiftzero deleted the docs-add-user-evidence branch April 10, 2018 22:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants