diff --git a/FEATURE_REQUEST_TEMPLATE.md b/FEATURE_REQUEST_TEMPLATE.md new file mode 100644 index 000000000..72ac44d98 --- /dev/null +++ b/FEATURE_REQUEST_TEMPLATE.md @@ -0,0 +1,66 @@ + + + Feature + + + + +
+

Title

+
+

+ + A well written title should contain a clear, brief explanation of the Feature, making emphasis on the most important points. +

+
+ +
+

Preconditions

+
+

Please provide as detailed information about your environment as possible.

+ +
+ +
+

Description

+
+

Description helps the developer to understand the Feature. +

+
+ +
+

Steps to reproduce

+
+

It is important to provide a set of clear steps to that location where feature need to be added. If relevant please include code samples.

+
    +
  1. step1
  2. +
  3. step2
  4. +
+
+ + + + + + + + + + + + + + + + + + + diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md new file mode 100644 index 000000000..ba6e43ec7 --- /dev/null +++ b/ISSUE_TEMPLATE.md @@ -0,0 +1,33 @@ +# Bug report + +### Title + +

+ Title is a vital part of bug report for developer and triager to quickly identify a unique issue. + + A well written title should contain a clear, brief explanation of the issue, making emphasis on the most important points. +

+ + +### Issue Description + Bug description helps the developer to understand the bug.It describes the problem encountered. + +### Preconditions + Please provide as detailed information about your environment as possible. + + 1. framework Version. + 2. Commit id. + +### Steps to reproduce + It is important to provide a set of clear steps to reproduce this bug.If relevant please include code samples. + + 1. step1 + 2. step2 + +### Expected result + Tell us what should happen +* [Screenshots, logs or description] + +### Actual result + Tell us what happens instead + * [Tell us what happens instead] \ No newline at end of file diff --git a/SUPPORT_TEMPLATE.md b/SUPPORT_TEMPLATE.md new file mode 100644 index 000000000..f692a9498 --- /dev/null +++ b/SUPPORT_TEMPLATE.md @@ -0,0 +1,48 @@ + + + Support + + + + +
+

Title

+
+

+ Title is a vital part of bug report for developer and triager to quickly identify a unique issue. +
+ A well written title should contain a clear, brief explanation of the issue, making emphasis on the most important points. +

+
+ +
+

Preconditions

+
+

Please provide as detailed information about your environment as possible.

+ +
+ +
+

Description

+
+

Description helps the developer to understand the exact scenario.It describes the problem encountered.

+
+ +
+

Steps to reproduce

+
+

It is important to provide a set of clear steps to reproduce that scenario. If relevant please include code samples.

+
    +
  1. step1
  2. +
  3. step2
  4. +
+
+ diff --git a/packages/Webkul/Admin/src/Config/menu.php b/packages/Webkul/Admin/src/Config/menu.php index dd92aa092..6435b5f41 100755 --- a/packages/Webkul/Admin/src/Config/menu.php +++ b/packages/Webkul/Admin/src/Config/menu.php @@ -42,7 +42,7 @@ return [ 'key' => 'catalog.products', 'name' => 'admin::app.layouts.products', 'route' => 'admin.catalog.products.index', - 'sort' => 4, + 'sort' => 1, 'icon-class' => '' ], [ 'key' => 'catalog.categories', @@ -54,13 +54,13 @@ return [ 'key' => 'catalog.attributes', 'name' => 'admin::app.layouts.attributes', 'route' => 'admin.catalog.attributes.index', - 'sort' => 1, + 'sort' => 2, 'icon-class' => '' ], [ 'key' => 'catalog.families', 'name' => 'admin::app.layouts.attribute-families', 'route' => 'admin.catalog.families.index', - 'sort' => 2, + 'sort' => 4, 'icon-class' => '' ], [ 'key' => 'customers',