Dashboard "Asset by Status" chart missing "Deployed" meta status

[ShaunNeighbourSwale]

Debug mode

• I have enabled debug mode
• I have read checked the Common Issues page

Describe the bug

All "Deployed" assets are shown on dashboard "Asset by Status" chart under "Ready to Deploy".

"Assets" list shows these correctly under the "Deployed" status.

Reproduction steps

1. Create Asset
2. Deploy Asset
3. Look at Dashboard
   ...

Expected behavior

Deployed assets to be shown under "Asset by Status" separated from "Ready to Deploy" assets.

Screenshots

Snipe-IT Version

6.0.7

Operating System

Hosted

Web Server

Hosted

PHP Version

Hosted

Operating System

Windows

Browser

Google Chrome

Version

103.0.5060.114 (Official Build) (64-bit)

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

[snipe]

The pie chart only represents your individual status labels, it's not broken down by status meta.

[ShaunNeighbourSwale]

But it's your states meta? I'm not reporting that a custom state isn't showing in the dashboard.

1. We add/import an asset.
2. We deploy the asset.
3. The asset automatically enters the "deployed" meta status.
4. This change is reflected in the assets list.
5. This change is not reflected on the dashboard.

If there was consistency in what data is shown, then I would understand, but there isn't, implying that the dashboard chart is not functioning as it should.

[snipe]

It's working as expected. The pie chart reflects only your status labels, not the meta status. The side nav shows you the breakdown by meta (in addition to your own status labels)

[ShaunNeighbourSwale]

Hi

This may be working as you expect, but not as I, or any of my colleagues expect.

This was discussed with your own support team, who escalated this issue to your developers, as they also agreed that this is not as they expected.

Please take a step back, and look at the usefulness of this chart - Does it show an accurate representation of the data. Does it directly contradict totals shown in another part of your system?

Please reopen this case until you have had sufficient time to consider this different perspective to your own.

[snipe]

This was discussed with your own support team, who escalated this issue to your developers, as they also agreed that this is not as they expected.

Actually, we didn't say that. We said it was working as expected and is not on the short term roadmap. (Helpdesk ticket 29106.)

It's already open as a feature request in our internal feature/bug ticketing system.

[snipe]

(You have to realize that any time we make changes like this for one user, it often profoundly affects users who use it differently. Every time we grant one wish, we upset countless other people who have different workflows, etc.)

[ShaunNeighbourSwale]

I completely understand that - But in this instance, I cannot fathom why anyone would want incorrect data shown.

Regarding the ticket;

"Hi Shaun,

I understand the confusion regarding Status Labels, as the term Ready-to-Deploy in this context means "All Assets readily deployable including those currently checked-out to a User "Deployed" or Checked-in and "Deployable". "Ready-to-Deploy" is a label for for the "Deployable" state; i.e. asset checked out, ready to deploy immediately after being checked back in are considered "Ready-to-Deploy."
​
You shouldn't have to do anything manually when checking out if you are using the default status labels. Deployed is a magical status type that happens when an asset has a status label that is “deployable” and is also checked out. Read a more about how this here: https://snipe-it.readme.io/docs/overview#section-status-labels.
​
So if you check out a "Ready to Deploy" asset, you should see the status change to Ready to Deploy > Deployed > target (user, or asset, or location). And the dashboard graphic should reflect that.
​
​Are you finding that's not the case?

Sincerely,

Victoria Pak
Chief Operations Officer
Grokability, Inc."

Snipe-IT Documentation

Overview

When your Snipe-IT installation is first set up, it can be a little overwhelming to figure out where to get started. The first place to start is usually your Admin Settings. We go through each of the specific admin options one by one in the Admin Settings section of this documentation, but that's wh...

[snipe]

Hi Shaun,

I spoke to our lead developer, and she told me that it actually is working as designed, meaning, the pie chart only looks at the status labels, and not at the meta status.

There is consideration to develop changes to the chart in the future, but unfortunately, it is not on the short term roadmap.

I'm sorry that we could not be more helpful in this matter.

Sincerely,

Birgit Zeus
QA Engineer
Grokability, Inc.

Regardless, it's open as a ticket on our internal feature/bug tracker, so there's no need to leave it open here.

[ShaunNeighbourSwale]

Indeed - Your COO escalated this to your dev team, and that appeared to end the conversation.

I'm glad it's now on your internal roadmap - And that information has now been shared with a customer who raised the issue, and was basically told "tough luck".

You have a great product, and we're happy to continue paying for it. But this could have been handled better. The response to the case should have been "This is now on our internal roadmap" rather than the reply I got, which was in contrast to the previous message from your COO, who acknowledged that there was an expectation for consistency between the dashboard and other parts of your system.

I hope this is something you will consider for future requests.

[snipe]

I appreciate your candid feedback.

Saying no - or at least not now - is part of our job. My COO escalated that to me (the lead dev and CEO). We discussed it, and I decided it was not on the short term roadmap, which is why you got the reply you got from Birgit. "Not on the short term roadmap" means just that. It means we're not saying no, but it's not a priority right this second because we have other things that are higher priority that we need to get done. Anything that isn't on the short term roadmap gets entered into our internal feature request/bug system so that as we complete certain tasks, we can re-evaluate priorities, the direction we want the product to go, etc. It doesn't mean "tough luck", it means "not now."

[ShaunNeighbourSwale]

Thanks - It's the only kind of feedback I give :P

And I am aware that you are the top banana - Having this level of communication is rare and appreciated.

However........ As top banana, if your response is "It's working as expected." that doesn't leave much room for interpretation. I may only be one customer, but I think I put forward a strong case, and this seemed to just be disregarded as a non-issue.

I do understand that you have other priorities. There are other issues still outstanding that I have raised that I would rather take priority over this. I do not expect every niggle I have to be bumped to the top of the queue just because I took the time to raise the issue. But.... We are using the system (fairly heavily I think), and when I, or one of my team find something that either isn't quite right, or could be improved, we don't just raise a ticket for the sake of it.

I wrote and deleted a long spiel about customer service, but it's veering away from the issue. This wasn't a great customer service experience, and I hope you'll take that as constructive criticism rather than any kind of personal attack. I am not placing 100% of the blame on you, as I clearly saw more negatives in some of the replies than were intended.

Regards

Shaun

[ShaunNeighbourSwale]

Thank you!