new issue template for epic level issues #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adding new template - Draft version 0.1
draft 0.2 edits
draft 0.3
new changes to format
formatting made better
updates to epic name
edits according to feedback
changes from GH templates forum
edits and small changes
chnages for Pr
changes 1.0
final draft changes
alfonso-op
approved these changes
Apr 1, 2024
| validations: | ||
| required: true | ||
| - type: markdown | ||
| id: user stories |
There was a problem hiding this comment.
Nit: Not sure if spaces in the id cause any issues, I recommend adding hyphens as done for other ids in this file.
| * User Story 1: (brief description) | ||
| * User Story 2: (brief description) | ||
| - type: markdown | ||
| id: acceptance criteria |
| validations: | ||
| required: true | ||
| - type: markdown | ||
| id: related issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We just wanted to add the new epics format for our team, so we don't need to populate items from step 0, for every time when we want to create an epic.
Tests
We will test this in our upcoming development sprints and make changes for anything we might need in the future.
Real test can be performed by creating new issue with this template on the org level.
Additional context
No additional context I can provide this moment