Skip to content

Instantly share code, notes, and snippets.

@ctrlaltjustine
Created January 20, 2017 16:18
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ctrlaltjustine/4dbdc63ac35bd44dc84756c2bc6fb864 to your computer and use it in GitHub Desktop.
Save ctrlaltjustine/4dbdc63ac35bd44dc84756c2bc6fb864 to your computer and use it in GitHub Desktop.
An issue template for travis-pro/design-tasks

Design Issues

Required to submit

  • Description of design task. (e.g. Conference sponsorship? Custom sticker? Advertising?)
  • What deliverables are required to complete this task?
  • When is this task due? (MM/DD/YY)
  • How long do you estimate this task to take? (HH:MM)
  • What is the priority of this task? (e.g. High, Moderate, Low)

Miscellaneous questions

  • Does this task require copywriting?
  • If this task requires copywriting will you provide the copy?
  • Do you already have a concept in mind?
  • Do you want to review a sketch before design moves to high fidelity work?
  • Do you want to review final art before the work is delivered?
@lenareinhard
Copy link

Looks great, thanks for that, Justine!

Minor feedback:

How long do you estimate this task to take? (HH:MM)

Would suggest going with time frames instead (also to incorporate coordination, communication, etc. into effort calculation, and not "only" "actual" design work), e.g.

  • 1 day or less
  • 2-3 days
  • 4-6 days

Do you want to review a sketch before design moves to high fidelity work?
Do you want to review final art before the work is delivered?

Would merge to "Please specify feedback loops needed (e.g.: would you want to review sketches before implementation, or final art before delivery?). (Please also ensure your availability for timely feedback.)"

What is the priority of this task? (e.g. High, Moderate, Low)

Could possibly remove for now, since, when in doubt, everything has a high priority? But if you'd want to leave it in, that's also totally cool.


Suggestions for additions:

  • Input: whose input will be needed?
  • Implementation: who will have to be involved in implementation? (e.g.: travis-web team,…)

@ctrlaltjustine
Copy link
Author

Thanks for the feedback Lena!

Revised issue template:

Design Issues

Required to submit

  • Description of design task. (e.g. Conference sponsorship, custom sticker, advertising.)
  • What deliverables are required to complete this task?
  • When is this task due? ( MM / DD / YY )
  • How long do you estimate this task to take? (e.g. ½ – 1 day, 2 – 3 days, 4 days – 1 week)
  • Whose feedback or input is required for this task?

Miscellaneous questions

  • Do you have a concept in mind?
  • Does this task require copywriting? If so, who will provide the copy?
  • Please specify feedback criteria for this work. (e.g. Will you want to review a rough sketch before digital work begins? Will you want to review final design work before delivery? Please ensure your availability for timely feedback.)

@lenareinhard
Copy link

Fantastic, thank you! I'd be +1 for implementing this (creating issue template, making announcement asking people to use template and make sure to fill in at least information under required before submitting anything to design-tasks), and then iterating depending on how it goes. Would you be up for doing this?

(Until recently, I wasn't familiar with how to create issue templates – you probably are already, in case you're not, I found this how-to pretty helpful. (There's also this folder in the Teal repo which contains an issue template, in case that helps?)

I'd be happy to help with any of that, just let me know if you'd want that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment