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

Samples grid and Basic Export do not contain correct information about the sample's district #13058

Open
3 tasks
carina29 opened this issue Mar 25, 2024 · 0 comments
Labels
change A change of an existing feature (ticket type)

Comments

@carina29
Copy link
Contributor

Problem Description

For samples associated with contacts, the displayed district in the samples grid and in the Basic Export should be the Contact's grid (if exists) or the source case's district if the contact's district is not filled.

Proposed Change

For samples associated with contacts, display in the grid and in the basic export the district associated with the contact (if is filled) or with the contact's source case ( if the contact's district is not filled).

Added Value/Benefit

Consistency in the way information is displayed in the grid and exports.

Acceptance Criteria

  • when both the contact and the contact's source case have information regarding the district, the information from the contact page should come first (be displayed in the samples grid and basic export);

  • when only the contact has district, the information should be displayed in the samples grid and the basic export;

  • when only the contact's source case has district, the information should be displayed in the samples grid and basic export;

Implementation Details

Note:
For samples associated with event participants, the logic is implemented here:
#12940

Mockups

No response

Additional Information

No response

@carina29 carina29 added the change A change of an existing feature (ticket type) label Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change A change of an existing feature (ticket type)
Projects
None yet
Development

No branches or pull requests

1 participant