Issue Layout

Posted on | Edited on | In

What should be the layout for a good bug ticket:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
and verify the issue you are about to submit is not a duplicate.
--->

## Environment information
(cluster info, system info)

## Problem Description
(Summarize the bug encountered concisely)

## Steps to reproduce
(How one can reproduce the issue - this is very important)

## Expected behaviour
(what you should see?)

## Observed behaviour
(what actually happens?)

## Additional info or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it is very hard to read otherwise.)

## Workaround available
(If you can, link to the line of code that might be responsible for the problem)

## Per Meeting Minutes

## TO-DO's

More:

  1. add right pipelines
  2. add right labels
  3. @people when reply
0%