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

Rules to create an Issue for TokenConnect #1

Open
ccndevelopers opened this issue Mar 27, 2019 · 1 comment
Open

Rules to create an Issue for TokenConnect #1

ccndevelopers opened this issue Mar 27, 2019 · 1 comment

Comments

@ccndevelopers
Copy link
Owner

Rules To Create Issue for TokenConnect

Read Carefully before creating an issue.

  • No duplicate issues will be accepted. The issue accepted first will be awarded for the benefit.
  • Accepted Bugs will be assigned severity level
    • low - if there is no harm to the user funds or data on using the application
    • moderate - if there is no harm to the user funds or data but the possibility it may harm in future.
    • high - if the bug is potentially affecting users or concerned parties.
    • very high - if the bug is potentially harming previous users or users who'll use the application in future and concerned parties.
  • One issue must be created only for one bug if you have found multiple bugs then create multiple issues. Do not write in previous issues for new bugs.
  • Discussion over the issue will be marked closed if an issue is resolved or inactive.
  • Only moderators have the possibility to assign a severity level to any issue created or bug found.
  • Follow the below pattern to create an issue

Heading of Issue (H2 Tag)

  • Short description of the bug

  • How the bug was occurred or originated, provide steps to reproduce the bug.

  • Problem occurred due to the bug

  • Possible solution (if, any)

  • Images to support your content (optional)

Example Bug Issue

Precision calculation issue

  • while calculating the total amount of tokens to send it is providing the inaccurate calculation if there are more than 2 digits after the decimal point.

  • Steps to Reproduce the Bug

    • first Select token you want to distribute
    • enter an arbitrary value 12.083 in Token Amount Per Address field
    • Select CSV file (containing 3 unique addresses)
    • Click next button
    • On confirm transaction page, under Total Tokens To Sent calculated tokens are 24.0166 , result must be 24.166
  • Possible solution: unknown

  • Images to support: NOT AVAILABLE

@puripong36575
Copy link

nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants