update dev ticket template

[jmcook1186]

A description of the changes proposed in the Pull Request

Updates developer ticket template according to discussion here: #613

[narekhovhannisyan]

I think it's better to leave at least one line of checkboxes so you don't have to figure out how to write it

[jmcook1186]

good point - adding now

[jawache]

Thanks @jmcook1186, every project is now being asked to align to the pm protocol here: https://www.notion.so/grnsft/Internal-Project-Protocol-6b8a9e881ed942df9a81a60aeecfd998?pvs=4 head to the section called "issues". So this will need to change somewhat to conform.

Specifically for IF the ticket should look something like so which follows the protocol and merges with your suggestions.

What: one sentence to describe the deliverable.
Why: can use a user story, but let's not insist, if it's a smaller subtask then user stories just become repetitive and add limited value (as a developer the tests should pass so we have a high quality product) so I think there is room for flexibility.
Context: As per your suggestion
Prerequisites: As per your suggestion
SoW: replaces implementation detail, docs and testing, can add comments to encourage people to think of checklist items related to testing/docs. But this is the place with all the work that needs to be done.
Acceptance Criteria: this should replace "What does done look like?" if the ticket involves a manifest file one of the criteria should be a manifest file that should be runnable. If there is any testing to be done (automation or manual) then the acceptance criteria is the place to understand what testing needs to be done. I'd imagine we flesh this out in refinement with multiple heads.

In addition

• Size should be either a project board field or a label, we might insist on one or the other in the future but right now there is flexibility to choose. In fact maybe not something we insist on until we've done some refinement on a ticket? But regardless, label or board field, you can only fill it in after the ticket is created.

• We normally keep it simple with just bolded words for headings (see hackathon board for examples) but I think we can also use headings instead of bolded but let's stick to h4, h2s take up a lot of space unnecessarily 😁

[jawache]

As per my comment on the PR

[jawache]

@jmcook1186 let's add to the template to trigger thinking in that style

Given ...
When ...
Then ...