This is a snippet of a F&O Stock section from the OT app. I am wondering if the list shown is correct.
I was expecting to have a list from ~240 FnO stocks. But I see something different.
If my understanding is wrong, would like to know how this list is derived.
Thanks.
Hey @khulsat,
We are getting this checked and will update you shortly.
Hey @khulsat,
Thanks for bringing this to our attention. We request you to update the app to the latest version and check.
Still under 52 week show HBL enginerring, I think this is not F&O stock?
Hey @khulsat,
Requesting you to update the OT app and check now, if in case of any difficulties do let us us know.
Hi @khulsat,
Thanks for bringing this to our attention. We request you to update the app to the latest version, all screeners in F&O Stock including Upper/Lower Circuit have been updated.
You may let me know if it’s working fine, once you have updated the app.
Looks ok now.
Still one question though,
App version remains the same even after a new update is released?
Hi @khulsat,
As it wasn’t a release with new features, it was an update in the same build we have kept the version the same. We would update the version when there is a new release with feature launches.
Thanks for the clarification.
To my knowledge, according to the release management process, for every new update, there would be a unique version.
For feature release, there would be new major version update and for bug fixes and enhancements, minor version update would be applicable.
Just sharing a thought. 
Eat mangoes. Don’t count trees. @khulsat 
The devil is in the details remember?
It’s fun giving free advice. No doubt about it. Product Feedback 
Feature Requests 
is only for fun! Right @thisisbanerjee?
Not a free advice. I am trying to understand what does version number has to do with your problem getting resolved? Sorry if that offended you. @khulsat I would have been very thankful if my problem got resolved. I believe in, gratitude is the attitude.
Well this is an engineering term and ideally the version update means that something was changed. The semantics are “<MAJOR.MINOR.PATCH>” so Dhan patched the previous release but forgot to update the patch version. It’s usually helpful internally to know what went wrong and where to rollback in case of an issue.
Exactly my point. Thanks for summing that up! 
If the aim is to build a healthy community (along with a stable product), people should not limit themselves to their own problems. Inclusive feedbacks should be welcomed. If this is not that place, then I apologise.
I genuinely asked that question since I am not familiar with this release numbering system.
Pretty stable product now except a few misses here and there, otherwise you would have seen countless posts from me pointing those issues. I also want the best product for myself.
@nitishbangera Have very politely educated me here. Thanks bro.
