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

Publication Specification doesn't work #77

Open
siyamalan opened this issue Jun 4, 2019 · 2 comments

Comments

2 participants
@siyamalan
Copy link

commented Jun 4, 2019

Description

A single analysis specification can be assigned while creating analysis request.
The problem is that a single product tested by lab can have multiple specifications.

Being able to change "Publication Specification", hence having desired specifications in published report would absolutely solve this problem.

Reproduction guide

  1. Created a new sample request

  2. Assigned analysis specification

  3. Entered the results

  4. Published the report

  5. Changed the "publication specification" again

  6. Published the report again

Observed behaviour

After saving publication specification, the "specification" changed but the "Range" did not change
image

Expected behaviour

The Range should be different in published report

Versions

  • OS: Ubuntu Server 18.04.2 LTS

  • senaite.core: 1.3.1

  • senaite.impress: 1.2.0

  • senaite.core.listing: master

  • senaite.core.supermodel: master

@xispa xispa transferred this issue from senaite/senaite.core Jun 12, 2019

@xispa

This comment has been minimized.

Copy link
Contributor

commented Jun 12, 2019

@siyamalan

This comment has been minimized.

Copy link
Author

commented Jun 21, 2019

Thanks for the reply @xispa
I have tried default+multi-default templates. My problem is "The range is unaffected by publication specification".

As shown in below picture, "Specification changes when I change publication specification but not the range. The publication specification I assign should also change the range

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.