I submitted this report a couple of days ago and I think the AI has blocked it’s progression.
Exporting of Zvols assumes 512K sectors which is wrong
If any staffer can update me if the bug has been blocked by the AI or is in the pending pile. The reason I asked is my last bug submission was closed by AI, it gave me a reason and I think it was right, but I was concerned that no human double checked it.
Thanks
We review all open tickets regularly. We have a blocked status if we determine they are on hold.
@ABain thanks for the feedback.
So this job has been closed by your AI and I still have no idea if anything has been done.
Has it been fixed, did your staff not find any bug? This is potential source of data corruption. I am very concerned.
This situation needs to be changed for users reporting bugs, the least you guys can do is tell us of the outcome. What company accepts bug reports from their community and then says thanks but we are not going to tell your the outcome, if you don’t like this, talk to your shrink. 
I would of also liked to see the code changes, however on this one I accept it might not be possible, but if it could I would welcome it.
Why is your AI closing jobs when they are assigned to a member of staff. Is this not what the staff member should be doing?
So do I now just guess what has happened?
If this does not change your community will stop reporting bugs, I know I will.
For me it says Status: “Done” and fixed version 26.0.0 or 27-Beta, so it seems it will either be fixed in the next release or the next version…
We look at bug reports and fix them as SMEs have time to look at them. They are automatically closed by our bot once associated commits have been merged. Do note that our bug ticketing system is not the same as a support ticket. There may not be a whole lot of communication by devs in the tickets, especially if the fix is straightforward.
If you have a support contract for truenas it’s generally recommended to file support cases with that team. If you don’t and file a bug ticket, we have a bot that does some triage steps, but it eventually gets to a queue where developers work on it as it aligns with priorities and time.
@awalkerix thanks for the feedback but I think you miss the point.
If you want guys want community feedback and bug reports, the least you can do is give minimal feedback on the progress of the ticket. i.e.
We have confirmed your issue and it is now on our internal roadmap
or
this bug has been fixed
or
We dont agree or cannot replicate this bug
I don’t want to do any more reports because your system is so shocking.
But just to have an AI change status to “Done” so I am left guessing, not for me.
NB: I had a ticket that was never touched by a human, but triaged and closed by an AI.
I am not expecting a line by line response, just a little courtesy and feedback.
Not sure of context of what you’re talking about, but we get a very large volume of tickets for a given release and many that are reporting duplicate issues. These will be deduplicated and closed automatically.
A bug report with Done status means that we reproduced the issue and fixed it. If it’s closed for some other reason this is reflected in the close status.
Note that I’m just trying to give a bit of insight here and express personal opinions about the matter. Maybe it would help if the GH PR links were visible in the ticket. I’m not sure people care that much as long as issue is resolved.
I was going to go on a rant about this and that, and then I have clicked on the link you have supplied above, so I am surprised about this and happy. So now the solutions is probably a lot easier.
in JIRA
closed, code submitted, here is the link
This issue has already been reported
we do not recognise this as an issue. The TN teams reviews these issue so it is not an AI making this descision.
I have only seen my issues in JIRA I did not know they were linked to this GitHub repo. I though code was pushed every now and again to it. From JIRA there is no way to know this.
It says it’s Done in the right hand section.
It also details what versions (will have) the fix.
Are you looking for something else?
If you look at the flow chart it implies, done is not done = confusing.
I was looking for a comment about what works was done etc.. for some reason I am yet to understand why this information is not added to the issue tracker to inform people what has been done .
@awalkerix posted a link to the pull request in the github repo which has the info I wanted. This is linked by nas-xxxxx
See above for my remedy to this boggle.
