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

🔄 Templates: synced file(s) with sovity/PMO-Software #406

Merged
merged 5 commits into from
Jan 6, 2025
Merged
Show file tree
Hide file tree
Changes from all 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
2 changes: 0 additions & 2 deletions .github/ISSUE_TEMPLATE/documentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,6 @@ labels: "task/documentation"
assignees: ""
---

# Documentation Update Request

## Description
<!-- Provide a brief overview of the documentation update request. What section or topic needs to be updated? -->

Expand Down
15 changes: 3 additions & 12 deletions .github/ISSUE_TEMPLATE/epic_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,10 @@ labels: "kind/epic"
assignees: ""
---

# Epic

## Description
<!-- Brief summary of what this Epic is, whether it's a larger project, goal, or user story. Describe the job to be done, which persona this Epic is mainly for, or if more multiple, break it down by user and job story. -->

### Requirements
## Requirements
<!-- Which requirements do you have to be fulfilled? -->
<!-- Which security-related requirements must be satisfied? -->

Expand All @@ -23,17 +21,10 @@ assignees: ""
- [ ] Create Stories which can be converted into issues
```

### Security Constraints
<!-- Which constraints can be checked that must be covered by the work breakdown? -->
- [ ] Final solution design has been challenged for security related topics

## Initiative / goal
<!-- Describe how this Epic impacts an initiative the business is working on. -->

### Hypothesis
## Hypothesis
<!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->

## Acceptance criteria and must have scope
## Acceptance Criteria
<!-- Define what is a must-have for launch and in-scope (e.g. security-related tasks like successful pen-tests). Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->

## Stakeholders
Expand Down
17 changes: 9 additions & 8 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,24 +6,25 @@ labels: "kind/enhancement"
assignees: ""
---

# Feature Request

## Description
<!-- A clear and concise description of what the user wants to happen. Example below. Replace brackets! -->
As a {user} who {preconditions}, I want to {do something}, so I can {goal}.

## Which Areas Would Be Affected?
<!-- e.g., DPF, CI, build, transfer, etc. -->
## Affected Areas
<!-- Specify areas that this feature will impact (e.g., CI, DPF, transfer, etc.) -->

## Why Is the Feature Desired?
<!-- Are there any requirements? -->
## Motivation
<!-- Explain why this feature is needed and any specific requirements. -->

## How does this tie into our current product?
<!-- Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new markets and innovative ideas? -->
## Related Initiatives or Features
<!-- Describe how this request ties into existing workflows, features, or initiatives. -->

## Stakeholders
<!-- Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature? -->

## Acceptance Criteria
<!-- Define what is a must-have for launch and in-scope (e.g. security-related tasks like successful pen-tests). Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->

## Solution Proposal and Work Breakdown
<!-- If you already know what needs to be done, please add a tasklist. -->

Expand Down
2 changes: 0 additions & 2 deletions .github/ISSUE_TEMPLATE/process.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,6 @@ labels: ["task/refine-process","task/documentation"]
assignees: ""
---

# Process Refinement Request

## Description
<!-- Provide a brief description of the process that needs refinement and the reason behind it. -->

Expand Down
4 changes: 0 additions & 4 deletions .github/workflows/add_issue_to_project.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,3 @@ jobs:
with:
project-url: https://github.com/orgs/sovity/projects/9
github-token: ${{ secrets.ADD_ISSUE_TO_PROJECT_PAT }}
- uses: actions/[email protected]
with:
project-url: https://github.com/orgs/sovity/projects/25
github-token: ${{ secrets.ADD_ISSUE_TO_PROJECT_PAT }}
Loading