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

Licenses Check-Out #4576

Closed
1 of 2 tasks
kd2067 opened this issue Dec 5, 2017 · 4 comments
Closed
1 of 2 tasks

Licenses Check-Out #4576

kd2067 opened this issue Dec 5, 2017 · 4 comments
Milestone

Comments

@kd2067
Copy link

kd2067 commented Dec 5, 2017

Expected Behavior (or desired behavior if a feature request)

Non super user with permissions to check out licenses to be able to check out
(what you expect to happen goes here)
I expect user with permissions to check out licenses to be able to do so

Actual Behavior

Unable to check out licenses
(what actually happens goes here)
Clicking on the check out button results in "Sad Panda". Going into the software you want the check out button is not present on the seat line levels

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


Provide answers to these questions:

  • Is this a fresh install or an upgrade? Fresh
  • Version of Snipe-IT you're running - tried both 4.1.6 and 4.1.7
  • Version of PHP you're running - latest
  • Version of MySQL/MariaDB you're running - latest
  • What OS and web server you're running Snipe-IT on - Ubuntu Xenial - Apache2
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc) - install.sh
  • WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
  • What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error - licenses
  • If a stacktrace is provided in the error, include that too.
  • Any errors that appear in your browser's error console. - no just sad panda
  • Confirm whether the error is reproduceable on the demo: https://snipeitapp.com/demo. - no
  • Include any additional information you can find in app/storage/logs and your webserver's logs.
  • Include what you've done so far in the installation, and if you got any error messages along the way. - No errors, it was a base install creted 2 users and 1 group and 1 software with 45 seats
  • Indicate whether or not you've manually edited any data directly in the database - no

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

https://snipe-it.readme.io/docs/getting-help

snipe added a commit that referenced this issue Dec 6, 2017
@snipe
Copy link
Owner

snipe commented Dec 6, 2017

This should be fixed on develop now

@snipe snipe closed this as completed Dec 6, 2017
@kd2067
Copy link
Author

kd2067 commented Dec 6, 2017

Pardon? Is this fixed or in development? If it is fixed why do I still have this issue. Is there something I need to do? If so what is it?

@snipe
Copy link
Owner

snipe commented Dec 6, 2017

This should be fixed on develop now

That means it's on the develop branch and will be in the next release.

@snipe snipe added this to the v4.1.8 milestone Dec 6, 2017
@Jarli01
Copy link
Contributor

Jarli01 commented Dec 6, 2017

@kd2067 you would have to switch to the develop branch and upgrade your installation to pull down these changes.

Otherwise, just wait until they are in "master" and update then.

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

3 participants