Skip to content

Commit d2b7114

Browse files
committed
Add issue templates for FlowDroid
1 parent d51a911 commit d2b7114

2 files changed

Lines changed: 53 additions & 0 deletions

File tree

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Bug report
3+
about: Create a bug report to help us improve FlowDroid.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Please examine each of the following points *carefully* so that we can help you as soon and best as possible.
11+
12+
**Describe the bug**
13+
A clear and concise description of what the bug is. If you use any third party library or tool that could interfere with FlowDroid in any way, you should indicate that clearly.
14+
15+
**Input file**
16+
Please upload or provide a (working) link to the .class, .jar, .dex, .apk or any other input file which caused the issue (the code you want to analyze). You can drop a ZIP file right into this textbox.
17+
This is _very_ important. In many cases, a bug triggers only on certain input files, which happen to be structured in a particular way which causes this problem. In case you do not supply the input files, we unfortunately often **cannot** help you at all.
18+
19+
**To reproduce**
20+
Steps to reproduce the behavior:
21+
Please include FlowDroid command line options you used or supply a code snippet to ease reproduction of the problem. **Please do not supply code snippets as _Screenshots_**. If possible, make sure that the supplied code is somewhat complete. It helps when the code for reproduction is somewhat minimal, but that is not necessary.
22+
23+
**Expected behavior**
24+
A clear and concise description of what you expected to happen.
25+
26+
**Stacktrace**
27+
If applicable, add complete stacktraces. In case your stack trace contains a line starting with "Caused by:", that line as well as the following lines are still part of the original stacktrace, so please include them as well. **Please do not supply stack traces as _Screenshots_**, copy and paste the stacktrace instead.
28+
29+
**Version information**
30+
Which version of FlowDroid did you use?
31+
32+
**Additional context**
33+
Add any other context about the problem here, which might help us to understand or solve your problem better. If there is more log output of FlowDroid, you should add that as well.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for FlowDroid.
4+
title: 'Feature quest: '
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

0 commit comments

Comments
 (0)