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.

Sign up for GitHub

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

Jump to bottom

update dev ticket template #642

Merged
merged 7 commits into from
Apr 18, 2024
Merged

update dev ticket template #642

Changes from 5 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
f3ee08b
fix(package): update dev ticket template
jmcook1186 Apr 12, 2024
d4c7c3a
Update .github/ISSUE_TEMPLATE/dev-ticket.md
jmcook1186 Apr 12, 2024
2580d69
fix(package): add checkbox examples
jmcook1186 Apr 12, 2024
e74a576
fix(package): make ticket template conform to gsf format
jmcook1186 Apr 15, 2024
f1b9a20
Update dev-ticket.md
jmcook1186 Apr 15, 2024
cb7343d
fix(package): add given-when-then to acceptance criteria
jmcook1186 Apr 18, 2024
0b2d097
Update dev-ticket.md
jawache Apr 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 20 additions & 26 deletions .github/ISSUE_TEMPLATE/dev-ticket.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,35 +7,29 @@ assignees: ''

---

<!--- Provide a general summary of the issue in the Title above -->
**What**
<!--- Describe the deliverable -->

## Rationale
<!--- Provide the relevant background information to udnerstand why this change is needed -->
<!--- This is where you can provide more details thathelp the reader understand why you want to make this change -->
**Why**
<!--- Describe why the proposed changes are needed -->

## Implementation details
<!--- Explain the steps you will take to implement this change. If you do not have specific steps yet, write your implementation ideas or outline general approach -->
**Context**
<!--- Explain any relevant background -->

## Priority
<!--- How urgent is this issue, and why? -->
<!--- Explain in writing or give a numerical value from 1 (nice-to-have) to 5 (critical) -->
**Prerequisites/resources**
<!--- does anything else need to happen to enable this work to be completed? -->

## Scope
<!--- Which parts of the project/codebase does this affect? -->
<!--- What are the possibel downstream impacts or side-effects of this change?? -->
**Statement of Work**
jmcook1186 marked this conversation as resolved.
Show resolved Hide resolved
<!--- what specific steps will be taken to address the aims of the ticket? -->
<!--- Include: -->
<!--- details of files to add/update -->
<!--- any documentation updates required-->
<!--- any tests that need adding/updating>
<!--- -->

## Size
<!--- How long do you expect this to take? -->
<!--- How many people/person-hours are required? -->

## What does "done" look like?
<!--- Explain what needs to happen in order for this to be considered complete -->

## Does this require updates to documentation or other materials??
<!--- Are there documentation, website or other media changes required after this change is implemented?. -->

## Deadline
<!--- Does this need to happen by a specific date? -->

## Acceptance criteria
<!--- What has to be true for this to get merged? What threshold of testing is acceptable? -->
**Acceptance criteria**
Copy link
Contributor

Choose a reason for hiding this comment

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

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

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

<!--- list the specific tasks that need to be completed in order to achieve the aims of this ticket. Please use checkboxes! -->
<!--- if the change relates to IF code or plugin code, provide a manifest that should run when these changes are compelted -->
- [ ] ...
- [ ] ...
Loading