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

update dev ticket template #642

Merged
merged 7 commits into from
Apr 18, 2024
Merged
Changes from 2 commits
Commits
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
49 changes: 26 additions & 23 deletions .github/ISSUE_TEMPLATE/dev-ticket.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,35 +7,38 @@ assignees: ''

---

<!--- Provide a general summary of the issue in the Title above -->
## User story
<!--- Describe the user persona this issue affects and how they benefit from the proposed changes -->

## 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 -->
## Rationale/context
<!--- Explain any relevant background and 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 -->
## Implementation details:
<!--- what specific steps will be taken to address the aims of the ticket? -->

## Priority
<!--- How urgent is this issue, and why? -->
<!--- Explain in writing or give a numerical value from 1 (nice-to-have) to 5 (critical) -->

## Scope
<!--- Which parts of the project/codebase does this affect? -->
<!--- What are the possibel downstream impacts or side-effects of this change?? -->
## What does done look like?
<!--- list the specific tasks that need to be completed in order to achieve the aims of this ticket. Please use checkboxes! -->

## Size
<!--- How long do you expect this to take? -->
<!--- How many people/person-hours are required? -->
<!--- how long will this take (t-shirt sizing XS, S, M, L, XL) -->

## Prerequisites/resources
<!--- does anything else need to happen to enable this work to be completed? -->

## Updates to documentation
<!--- enumerate specific changes required to the documentation, formatted as checkboxes with associated urls -->

## Testing
<!--- what tests are required for the changes to get merged? Please use checkboxes!-->
Copy link
Member

Choose a reason for hiding this comment

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

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good point - adding now


## What does "done" look like?
<!--- Explain what needs to happen in order for this to be considered complete -->
## Reviewer
<!--- assign a reviewer who can make this ticket READY -->

## Does this require updates to documentation or other materials??
<!--- Are there documentation, website or other media changes required after this change is implemented?. -->
## Manifest
<!--- Only for issues relating to features/plugins -->
<!--- provide a draft manifest that should run when this task is completed -->

## 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? -->
<!--- ADDITIONAL-->
<!--- is the ticket assigned to someone? -->
<!--- please label appropriately, including one label from each of the following types: type, size, urgency, status-->
Loading