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

Sort order of ARs (Positions) in Worksheets #2213

Open
ramonski opened this issue Sep 12, 2017 · 6 comments
Open

Sort order of ARs (Positions) in Worksheets #2213

ramonski opened this issue Sep 12, 2017 · 6 comments
Milestone

Comments

@ramonski
Copy link
Contributor

Steps to reproduce

Create a new Worksheet with Analyses from different ARs of the same Client

Current behavior

The ARs are not sorted according to their creation date.

Expected behavior

ARs are sorted according to their creation date.

Screenshot (optional)

ws17-013_ _bika

ws17-013_ _bika

@ramonski ramonski added this to the 3.2.1 milestone Sep 12, 2017
@ramonski ramonski self-assigned this Sep 12, 2017
@shamut
Copy link

shamut commented Sep 13, 2017

I also have a lot of interest on this. I was also having similar challenges and realized that the system is assigning worksheets based on date of receipt in the lab;this is a correct behavior given that samples maybe registered by client contacts.
On exploring further, we realized that sorting them by creation date also has its own limitations. We may want to also strengthen the way samples are received, the challenge is when you select and receive more than 1 sample at a goal, the system distorts and the challenge comes in.

@ramonski
Copy link
Contributor Author

It seems like the Analyses within an AR in a worksheet (Amylose Content, Grain elongation, Protein) are also not listed the same way as in the (categorized) AR view.

@andersonsmith
Copy link
Contributor

Wasn't the sort order field ignored in some views for performance but still exists in the AR view?

@shamut
Copy link

shamut commented Sep 13, 2017

I am sure sort order has never been there since there are analysis positions involved too

@ramonski
Copy link
Contributor Author

Seems like this one could be related to #2219 and thus, fixed already.

@ramonski
Copy link
Contributor Author

Seems to be fixed with #2219:
ws17-016_ _bika

@ramonski ramonski modified the milestones: 3.2.1, 3.3.0 Oct 2, 2017
@ramonski ramonski removed their assignment Dec 7, 2017
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

3 participants