Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

Update user story issue template #984

Closed
ethomson wants to merge 1 commit into from
Closed

Update user story issue template #984

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
40 changes: 38 additions & 2 deletions .github/ISSUE_TEMPLATE/0-story.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,47 @@ body:
id: description
attributes:
label: Description
description: Describe the need. Why is it needed? What is the expected outcome? What is the impact?
placeholder: Describe the task
description: What is the feature? What is the expected outcome? Why does it matter? Who benefits? (If there are specific requests for this functionality, link to them.)
placeholder: Describe the feature...
validations:
required: true

- type: textarea
id: implementation
attributes:
label: How it works
description: What is the key functionality? How does a user access or enable it? Are there any dependencies or prerequisites?
placeholder: Describe the functionality...

- type: textarea
id: use_cases
attributes:
label: Use cases
description: What are the primary use cases? Why is it uniquely valuable? How is it different than existing solutions?
placeholder: Describe the use cases that are enabled...

- type: input
id: release_date
attributes:
label: Release date
description: Estimated release date (yyyy-mm-dd)
Copy link
Copy Markdown

@lukehinds lukehinds Feb 7, 2025

Choose a reason for hiding this comment

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

No one would know this at this point, it would still need to go through backlog prioritization and even then, if something more important comes up, it could well get dropped.

placeholder: yyyy-mm-dd
validations:
required: false

- type: dropdown
id: release_tier
attributes:
label: Release tier
Copy link
Copy Markdown

@lukehinds lukehinds Feb 7, 2025

Choose a reason for hiding this comment

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

Would this even been known at this point? If it means someone needs to discuss with marketing first and have it planned to this degree, I would say we are still to new and in discovery to be planning this much.

Copy link
Copy Markdown

@scottdouglasbuchanan scottdouglasbuchanan Feb 7, 2025

Choose a reason for hiding this comment

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

Agreed. I think we should remove 'release tier' from the brief.

description: What's the release tier and requisite marketing support?
options:
- Tier 1
- Tier 2
- Tier 3
default: 2
validations:
required: false

- type: textarea
id: additional-context
attributes:
Expand Down