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

No supplier field when adding accessories #2579

Closed
2 tasks done
veen1981 opened this issue Sep 7, 2016 · 1 comment
Closed
2 tasks done

No supplier field when adding accessories #2579

veen1981 opened this issue Sep 7, 2016 · 1 comment

Comments

@veen1981
Copy link

veen1981 commented Sep 7, 2016

Expected Behavior (or desired behavior if a feature request)

When adding a new accessory, there should be a field to add the supplier, especially considering there is a field for order number. Without knowing who the supplier is, tracking something based solely on the order number could be a little tricky.


Actual Behavior

Currently there is no field for supplier when adding an accessory.

capture


Please confirm you have done the following before posting your bug report:


Please provide answers to these questions before posting your bug report:

  • Version of Snipe-IT you're running *v3.4.0-9-g67315d8 *
  • What OS and web server you're running Snipe-IT on CentOS 7 Apache
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc) Manual
  • If you're getting an error in your browser, include that error N/A
  • What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error my.site.edu/admin/accessories/create
  • If a stacktrace is provided in the error, include that too. N/A
  • Any errors that appear in your browser's error console. N/A
  • Confirm whether the error is reproduceable on the demo. Supplier field is also absent on the demo
  • Include any additional information you can find in app/storage/logs and your webserver's logs. N/A
  • Include what you've done so far in the installation, and if you got any error messages along the way.
  • Indicate whether or not you've manually edited any data directly in the database
@stale
Copy link

stale bot commented Jan 20, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

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

No branches or pull requests

2 participants