Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit cfa45f1

Browse files
authored
Merge pull request #842 from utPLSQL/jgebal-patch-1
Update issue templates
2 parents 6d05b2f + be09a1e commit cfa45f1

2 files changed

Lines changed: 76 additions & 0 deletions

File tree

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**Provide version info**
14+
Information about utPLSQL and Database version,
15+
```sql
16+
set serveroutput on
17+
declare
18+
l_version varchar2(255);
19+
l_compatibility varchar2(255);
20+
begin
21+
dbms_utility.db_version( l_version, l_compatibility );
22+
dbms_output.put_line( l_version );
23+
dbms_output.put_line( l_compatibility );
24+
end;
25+
/
26+
select substr(ut.version(),1,60) as ut_version from dual;
27+
select * from v$version;
28+
select * from nls_session_parameters;
29+
select substr(dbms_utility.port_string,1,60) as port_string from dual;
30+
```
31+
32+
**Information about client software**
33+
What client was used to run utPLSQL tests? Was it from TOAD, SQLDeveloper, SQLPlus, PLSQL Developer etc...
34+
35+
**To Reproduce**
36+
Steps to reproduce the behavior:
37+
1. Go to '...'
38+
2. Click on '....'
39+
3. Scroll down to '....'
40+
4. See error
41+
42+
**Expected behavior**
43+
A clear and concise description of what you expected to happen.
44+
45+
**Example code**
46+
If applicable, add sample code to help explain your problem.
47+
Please avoid putting your company private/protected code in an issue, as it might violate your company's privacy and security policies.
48+
49+
**Additional context**
50+
Add any other context about the problem here.
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
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.
21+
22+
**Note**
23+
> Please do not create issues for generic SQL or PL/SQL questions. There are other forums and communities to help you with those. See [ASKTom](https://asktom.oracle.com) for example.
24+
25+
**Want to discuss**
26+
If you want to discuss your issue, join [our SLACK chat](http://utplsql-slack-invite.herokuapp.com/).

0 commit comments

Comments
 (0)