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

TRUNK-6190 Add fulfiller location in orders #4382

Closed
wants to merge 1 commit into from

Conversation

slubwama
Copy link
Contributor

@slubwama slubwama commented Sep 5, 2023

Description of what I changed

In the Order Object I have added a field fulfillerLocation. This has also lead to changes in tests are assoriated. The affacted test classes are DrugOrderTest.java, OrderTest.java, ReferralOrderTest.java, TestOrderTest.java in test cloneForRevision_shouldSetAllTheRelevantFields

Issue I worked on

see https://issues.openmrs.org/browse/TRUNK-6190

Checklist: I completed these to help reviewers :)

  • My IDE is configured to follow the code style of this project.

    No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

  • I have added tests to cover my changes. (If you refactored
    existing code that was well tested you do not have to add tests)

    No? -> Write tests and add them to this commit git add . && git commit --amend

  • I ran mvn clean package right before creating this pull request and
    added all formatting changes to my commit.

    No? -> Execute the above command

  • All new and existing tests passed.

    No? Could you figure out why and add the fix to your commit? It is your responsibility to make sure your code works.

  • My pull request is based on the latest changes of the master branch.

    No? Unsure? -> execute command `git pull --rebase upstream master

@slubwama slubwama requested a review from dkayiwa September 5, 2023 06:08
@dkayiwa
Copy link
Member

dkayiwa commented Sep 5, 2023

@slubwama this being a new feature which we do not usually back port to previous versions, what is your plan for using it? Are you planning to upgrade your sites to the next platform release in order to take advantage of this?

@slubwama
Copy link
Contributor Author

slubwama commented Sep 5, 2023

@slubwama This is a new feature that we do not usually backport to previous versions, What is your plan for using it? Are you planning to upgrade your sites to the next platform release in order to take advantage of this?

@dkayiwa that depends on how fast the 2.7.x series gets released. The reason why I had thought of backporting was to reduce the turnaround time.

@dkayiwa
Copy link
Member

dkayiwa commented Sep 5, 2023

What plan do you have if 2.7 does not get released as fast as you will need?

@slubwama
Copy link
Contributor Author

slubwama commented Sep 5, 2023

What plan do you have if 2.7 does not get released as fast as you will need?

Backport was the plan. But since its not advised we may have to wait it out.

@dkayiwa
Copy link
Member

dkayiwa commented Sep 5, 2023

Let us use order attributes, for now.

@slubwama
Copy link
Contributor Author

slubwama commented Sep 8, 2023

Let us use order attributes, for now.

@dkayiwa This is noted and followed up with the ticket and PR to ensure OrderAttributes do have REST Support before we can create fhir apis
Pr openmrs/openmrs-module-webservices.rest#587
Ticket https://issues.openmrs.org/browse/RESTWS-920

@dkayiwa
Copy link
Member

dkayiwa commented Dec 5, 2023

@slubwama are you still working on this? Or do you still need this guy?

@slubwama
Copy link
Contributor Author

slubwama commented Dec 6, 2023 via email

Copy link

github-actions bot commented Aug 5, 2024

tl;dr our action detected no activity on this PR and will close it in 30 days if the stale label is not removed.

OpenMRS welcomes your contribution! It means a lot to us that you want to contribute to equity in healthcare!

This PR has not seen any activity in the last 5 months. That is why we wanted to check whether you are still working on it or need assistance from our side.
Please note that this is an automated message and we might very well be the reason why there has not been any activity lately. We certainly do not want to discourage you from contributing. We do need to be honest in that OpenMRS has limited resources for reviewing PRs.

If you do not have time to continue the work or have moved on you don’t need to do anything. We will automatically close the PR in 30 days. We hope to see you back soon :)
If you would like to continue working on it or require help from us please remove the stale label and respond by commenting on the issue.

@github-actions github-actions bot added the Stale label Aug 5, 2024
Copy link

github-actions bot commented Sep 4, 2024

tl;dr closing this PR since it has not seen any activity in the last 6 months.

OpenMRS welcomes your contribution! It means a lot to us that you want to contribute to equity in healthcare! We certainly do not want to discourage you from contributing. We do need to be honest in that OpenMRS has limited resources for reviewing PRs. Your PR has not seen any activity in the last 6 months. This is why we have decided to close this PR for now. This allows us OpenMRS reviewers to focus our limited time to review all other PRs in a timely and professional manner.

Please feel free to reassign yourself to the issue you worked on in our JIRA when you have time to focus on it. After that reopen a new PR and we will be glad to work with you to get your contribution merged. Thank you very much for your help and understanding :)

@github-actions github-actions bot closed this Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants